After preparing a restored database from RTM, and having it setup with an upgraded R2 compatible modelstore (using the installation wizard and the upgrade guide), I installed a new R2 AOS and pointed to the database. I want to test how this will work before I do it on production.
I noticed a few problems in the installation log, a couple of stored procedures that did not get created due to missing columns. Obviously, the AOS has not even started, so the data upgrade has not yet begun. I am wondering if anyone has any previous experience on whether or not I can safely ignore these errors, or will they create unforeseen problems later down the road. As everyone else, I don't want to waste time on something that eventually will not work.
Here is a transcript of the errors:
2013-01-03 10:19:37Z Creating stored procedures post AOS install.
2013-01-03 10:19:37Z Creating stored procedure '[dbo].[getNumInternal]'.
2013-01-03 10:19:37Z An error occurred while Setup was creating the stored procedure [dbo].[getNumInternal] for access by login 'DOMAIN\daxaos'.
2013-01-03 10:19:37Z Reason: Invalid column name 'PARTITION'.
2013-01-03 10:19:37Z Invalid column name 'PARTITION'.
2013-01-03 10:19:37Z Invalid column name 'PARTITION'.
2013-01-03 10:19:37Z Error occurred when executing stored procedure '[dbo].[getNumInternal]'. Error:
2013-01-03 10:19:37Z ******************************************************************************************************
2013-01-03 10:19:37Z Invalid column name 'PARTITION'.
2013-01-03 10:19:37Z Invalid column name 'PARTITION'.
2013-01-03 10:19:37Z Invalid column name 'PARTITION'.
2013-01-03 10:19:37Z ******************************************************************************************************
2013-01-03 10:19:37Z Creating stored procedure '[dbo].[sp_GetNextRecId]'.
2013-01-03 10:19:37Z Creating stored procedure '[dbo].[sp_AddBIAnalysisServer]'.
2013-01-03 10:19:37Z An error occurred while Setup was creating the stored procedure [dbo].[sp_AddBIAnalysisServer] for access by login 'DOMAIN\daxaos'.
2013-01-03 10:19:37Z Reason: Invalid column name 'PARTITIONS'.
2013-01-03 10:19:37Z Invalid column name 'PARTITIONS'.
2013-01-03 10:19:37Z Invalid column name 'PARTITIONS'.
2013-01-03 10:19:37Z Error occurred when executing stored procedure '[dbo].[sp_AddBIAnalysisServer]'. Error:
2013-01-03 10:19:37Z ******************************************************************************************************
2013-01-03 10:19:37Z Invalid column name 'PARTITIONS'.
2013-01-03 10:19:37Z Invalid column name 'PARTITIONS'.
2013-01-03 10:19:37Z Invalid column name 'PARTITIONS'.
2013-01-03 10:19:37Z ******************************************************************************************************
2013-01-03 10:19:37Z Creating stored procedure '[dbo].[sp_AddReportServer]'.
2013-01-03 10:19:37Z An error occurred while Setup was creating the stored procedure [dbo].[sp_AddReportServer] for access by login 'DOMAIN\daxaos'.
2013-01-03 10:19:37Z Reason: Invalid column name 'ISSHAREPOINTINTEGRATED'.
2013-01-03 10:19:37Z Error occurred when executing stored procedure '[dbo].[sp_AddReportServer]'. Error:
2013-01-03 10:19:37Z ******************************************************************************************************
2013-01-03 10:19:37Z Invalid column name 'ISSHAREPOINTINTEGRATED'.