When running the install package for 1.6.5, it gets past the 'Install Visual Studio Templates' step successfully, but each time it gets about 75% done with 'Build StrataFrame Databases' and I get an error which says "An error occurred while deploying the meta-data to the server.  Please help so that I can get the new version installed.  Thanks.

Here is the info from the log file which shows the error during installation:

• 3/10/2008 1:06:56 PM -> Deploying meta-data for database 'StrataFrame'
• 3/10/2008 1:06:57 PM -> Ensuring Filegroups exist on database 'StrataFrame'
• 3/10/2008 1:06:57 PM -> Filegroup verification complete.
• 3/10/2008 1:06:57 PM -> Ensuring Tables exist on database 'StrataFrame'
• 3/10/2008 1:07:09 PM -> Table verification complete.
• 3/10/2008 1:07:09 PM -> Dropping unneeded filegroups for 'StrataFrame'
• 3/10/2008 1:07:09 PM -> Unneeded filegroups dropped on database 'StrataFrame'
• 3/10/2008 1:07:09 PM -> Ensuring Indexes exist on database 'StrataFrame'
• 3/10/2008 1:07:13 PM -> Index verification complete.
• 3/10/2008 1:07:13 PM -> Ensuring Foreign Keys exist on database 'StrataFrame'
• 3/10/2008 1:07:17 PM -> Foreign Key verification complete.
• 3/10/2008 1:07:17 PM -> Ensuring Views, Stored Procedures, and UDFs exist on database 'StrataFrame'
X 3/10/2008 1:07:17 PM -> An error occurred while deploying the meta-data to the server.SqlException
  Invalid object name 'fn_listextendedproperty'.

Source     : .Net SqlClient Data Provider

Stack Trace:
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteScalar()
   at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.AreExtendedPropertiesDeployed(DatabaseInfo dbInfo)
   at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.GetListOfViewsSprocsAndUdfsToDrop(DatabaseInfo dbInfo)
   at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.DropAllDeployedViewsSprocsAndUdfs(DatabaseInfo dbInfo)
   at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.EnsureViewsSprocsUdfs(Database parent, DatabaseInfo dbInfo)
   at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.EnsureDatabases()
   at MicroFour.StrataFrame.DBEngine.SQL.DatabaseMigrator.DeployMetaDataThread()

Are you running SQL Server 2000 or 2005? We starting using an extended property in this reelase, and though our research indicated that the fn_listextendedproperty was support in 2000 we did not actually setup a 2000 server for testing and only test on 2005 and above servers.  So my guess would be that you are on 2000 and this property is not supported.  Confirm this and we can go from there.

Yes, the SF data is on is a 2000 server.  We have 2005 servers and if this needs to be moved to one of those it can be done, but would rather not if we can find a better fix. 

You will be better served, especially in the long-term, if you move the StrataFrame database to a SQL Server 2005 instance.  There are going to be some 2005 and above features that we start taking advantage of...this will probably be the fastest route to a fix today for you as well.  I will look into this and load a SQL Server 2000 instance somewhere.

Just FYI I am loading a SQL Server 200 instance now for testing, but I am not sure when we will post a fix.  We are working through the issue.

I just moved my db to 2005 and it appears to have corrected the issue I was having.  Thanks for the help!

Good deal.  I am setting up another virtual test server that will get included in our tests so that this doesn't happen in the future.  It was just one of those things that slipped through

Was there a fix for this? I don't have the choice of using SQL 2005 at the moment.



Thanks!

The latest build that is out there should work fine on either 2000 or 2005, so you should be good.