I am getting an error installing during the data deployment phase. I have triple checked SQL server instance , username  and password etc . Where can i find a log file to get a little more info on why it is throwing up?

Paul

Hi Paul.

The log file should be at "C:\Program Files (x86)\Common Files\MicroFour\StrataFrame".

I would like to see what the log shows. There is clearly some exception being thrown during the SQL deployment which will be shown in the log file, that will give us the starting point to work through this.

• 8/27/2010 4:13:09 PM -> Deploying meta-data for database 'StrataFrame'
• 8/27/2010 4:13:09 PM -> Ensuring Filegroups exist on database 'StrataFrame'
X 8/27/2010 4:13:09 PM -> An error occurred while deploying the meta-data to the server.UnknownPropertyException
  Cannot read property IsFileStream.This property is not available on SQL Server 2005.

Source     : Microsoft.SqlServer.Smo

Stack Trace:
   at Microsoft.SqlServer.Management.Smo.SqlPropertyMetadataProvider.PropertyNameToIDLookupWithException(String propertyName, PropertyAccessPurpose pap)
   at Microsoft.SqlServer.Management.Smo.PropertyCollection.GetValueWithNullReplacement(String propertyName, Boolean throwOnNullValue, Boolean useDefaultOnMissingValue)
   at Microsoft.SqlServer.Management.Smo.PropertyCollection.GetValueWithNullReplacement(String propertyName)
   at Microsoft.SqlServer.Management.Smo.FileGroup.get_IsFileStream()
   at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.VerifyFileGroup(FileGroup Fg, FileGroupInfo FgInfo, DatabaseInfo DbInfo)
   at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.EnsureFileGroups(Database FgParent, DatabaseInfo DbInfo)
   at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.EnsureDatabases()
   at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.DeployMetaDataThread()

There also seems to be a problem with guid primary keys casting to string.

Paul

Hi Paul.

We got it, there is a test being run that doesn't support SQL Server 2005. If possible, upgrading into SQL Server 2008 would keep you going. Nevertheless, it is being correct now.

Paul,



We will post a build later today (1.7.3.1) that will resolve the issue of the SQL Server 2005 FILESTREAM test.







In regards to this, I don't really know what you are talking about. When and where are you referring to this? What is your exception and stack trace?

The problem is in businesslayer.vb in the function GetIndexOfPrimaryKey
The code prior to the change used PrimaryKeyValues(lnCnt).ToString() to get the value of that portion of the key

The changed code uses CStr(PrimaryKeyValues(lnCnt)).Replace("'", "''") to get the portion of the key and address the issue of single quotes. CStr doesn't work on a guid.

What version were you on before you updated?

This has been addressed as well and will be in the 1.7.3.1 build posted later today.