Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP forum
Unanswered

Management Reporter Upgrade Failed

Posted on by 15

Hello,

We're attempting to upgrade our old Management Reporter database from 2012 (RU2) to 2012 (CU16). I followed the instructions in this article:    .

The upgrade runs for about 90 minutes and then crashes. Deployment log contains the following error description. Need help please!

1/11/2023 10:10:58 AM - [2023-01-11 10:10:58.820]PostDeployment script starts executing.
Machine: BDCMRS500
1/11/2023 10:11:12 AM - Inserting repository link for reports...
Machine: BDCMRS500
1/11/2023 10:11:12 AM - Updating scheduled report groups...
Machine: BDCMRS500
1/11/2023 10:11:12 AM - Updating XBRL tables...
Machine: BDCMRS500
1/11/2023 10:11:12 AM - Checking existing data against newly created constraints
Machine: BDCMRS500
1/11/2023 10:11:13 AM - .Net SqlClient Data Provider: Msg 547, Level 16, State 0, Line 23 The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_File_Data". The conflict occurred in database "ManagementReporter2012", table "Reporting.Data", column 'Hash'.
Machine: BDCMRS500
1/11/2023 10:11:13 AM - Script execution error. The executed script:
ALTER TABLE [Reporting].[ControlTreeCriteria] WITH CHECK CHECK CONSTRAINT [FK_ControlTreeCriteria_XbrlDimensionNamespaceID];

ALTER TABLE [Reporting].[ControlNote] WITH CHECK CHECK CONSTRAINT [FK_ControlNote_ControlReference];

ALTER TABLE [Reporting].[ControlReference] WITH CHECK CHECK CONSTRAINT [FK_ControlReference_Data];

ALTER TABLE [Reporting].[ControlXbrlMappingSetDetail] WITH CHECK CHECK CONSTRAINT [FK_ControlXbrlCompanyMappingDetail_ControlReference];

ALTER TABLE [Reporting].[ControlColumnCriteria] WITH CHECK CHECK CONSTRAINT [FK_ControlColumnCriteria_XbrlDimensionNamespaceID];

ALTER TABLE [Reporting].[ControlRowCriteria] WITH CHECK CHECK CONSTRAINT [FK_ControlRowCriteria_ControlReference];

ALTER TABLE [Reporting].[ControlRowCriteria] WITH CHECK CHECK CONSTRAINT [FK_ControlRowCriteria_ControlReference2];

ALTER TABLE [Reporting].[ControlColumnCriteria] WITH CHECK CHECK CONSTRAINT [FK_ControlColumnCriteria_NamespaceID];

ALTER TABLE [Reporting].[ControlTreeCriteria] WITH CHECK CHECK
Machine: BDCMRS500
1/11/2023 10:11:13 AM - An error occurred while the batch was being executed.
Machine: BDCMRS500
1/11/2023 10:11:13 AM - Updating database (Failed)
Machine: BDCMRS500
1/11/2023 10:11:13 AM - The database deployment failed. Additional information: Microsoft.SqlServer.Dac.DacServicesException: Could not deploy package.
Warning SQL72015: The table [Connector].[VersionHistory] is being dropped, data loss could occur.
Warning SQL72015: The table [Reporting].[License] is being dropped, data loss could occur.
Error SQL72014: .Net SqlClient Data Provider: Msg 547, Level 16, State 0, Line 23 The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_File_Data". The conflict occurred in database "ManagementReporter2012", table "Reporting.Data", column 'Hash'.
Error SQL72045: Script execution error. The executed script:
ALTER TABLE [Reporting].[ControlTreeCriteria] WITH CHECK CHECK CONSTRAINT [FK_ControlTreeCriteria_XbrlDimensionNamespaceID];

ALTER TABLE [Reporting].[ControlNote] WITH CHECK CHECK CONSTRAINT [FK_ControlNote_ControlReference];

ALTER TABLE [Reporting].[ControlReference] WITH CHECK CHECK CONSTRAINT [FK_ControlReference_Data];

ALTER TABLE [Reporting].[ControlXbrlMappingSetDetail] WITH CHECK CHECK CONSTRAINT [FK_ControlXbrlCompanyMappingDetail_ControlReference];

ALTER TABLE [Reporting].[ControlColumnCriteria] WITH CHECK CHECK CONSTRAINT [FK_ControlColumnCriteria_XbrlDimensionNamespaceID];

ALTER TABLE [Reporting].[ControlRowCriteria] WITH CHECK CHECK CONSTRAINT [FK_ControlRowCriteria_ControlReference];

ALTER TABLE [Reporting].[ControlRowCriteria] WITH CHECK CHECK CONSTRAINT [FK_ControlRowCriteria_ControlReference2];

ALTER TABLE [Reporting].[ControlColumnCriteria] WITH CHECK CHECK CONSTRAINT [FK_ControlColumnCriteria_NamespaceID];

ALTER TABLE [Reporting].[ControlTreeCriteria] WITH CHECK CHECK

at Microsoft.SqlServer.Dac.DeployOperation.ThrowIfErrorManagerHasErrors()
at Microsoft.SqlServer.Dac.DeployOperation.<>c__DisplayClass14.<>c__DisplayClass16.<CreatePlanExecutionOperation>b__13()
at Microsoft.Data.Tools.Schema.Sql.Dac.OperationLogger.Capture(Action action)
at Microsoft.SqlServer.Dac.DeployOperation.<>c__DisplayClass14.<CreatePlanExecutionOperation>b__12(Object operation, CancellationToken token)
at Microsoft.SqlServer.Dac.Operation.Microsoft.SqlServer.Dac.IOperation.Run(OperationContext context)
at Microsoft.SqlServer.Dac.ReportMessageOperation.Microsoft.SqlServer.Dac.IOperation.Run(OperationContext context)
at Microsoft.SqlServer.Dac.DeployOperation.Microsoft.SqlServer.Dac.IOperation.Run(OperationContext context)
at Microsoft.SqlServer.Dac.OperationExtension.Execute(IOperation operation, DacLoggingContext loggingContext, CancellationToken cancellationToken)
at Microsoft.SqlServer.Dac.DacServices.InternalDeploy(IPackageSource packageSource, Boolean isDacpac, String targetDatabaseName, DacDeployOptions options, CancellationToken cancellationToken, DacLoggingContext loggingContext, Action`3 reportPlanOperation, Boolean executePlan)
at Microsoft.SqlServer.Dac.DacServices.Deploy(DacPackage package, String targetDatabaseName, Boolean upgradeExisting, DacDeployOptions options, Nullable`1 cancellationToken)
at Microsoft.Dynamics.Performance.Deployment.Database.DatabaseDeployer.TryPerformDeployment(Boolean forceNew)
Machine: BDCMRS500
1/11/2023 10:11:13 AM - Database deploy status: False
Machine: BDCMRS500
1/11/2023 10:11:13 AM - The database deployment failed. Check the deployment log for details. The database deployment failed. Check the deployment log for details.
Machine: BDCMRS500
1/11/2023 10:20:43 AM - The database deployment failed. Check the deployment log for details.

Categories:
  • Greg Byer Profile Picture
    Greg Byer 2,586 on at
    RE: Management Reporter Upgrade Failed

    We've seen problems when upgrading from a lower version like CU2 all the way to CU16.  You could do it in steps -- CU2 to CU9 to CU13 to CU16.  But if you're moving to a new server, I would just export the reports from MR CU2, do a brand new install of MR CU16 on the new server, then import the reports.  You'll need to add users back to MR Security and set up any report groups or report schedules that you had.  Any historical report versions you had in the Report Library would be lost.  

  • RJarrell Profile Picture
    RJarrell 277 on at
    RE: Management Reporter Upgrade Failed

    I think it may be the big jump from 2 to 16. Theoretically, it should work, but I have seen issues in the past. 

    Here is another post where someone had similar issues but from and to different versions:    

    If I were in your shoes, I would probably consider the one recommendation where the exported all of the reports within MR, uninstalled, and installed the new version. Then they just uploaded the old reports back intot he new version. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Anton Venter – Community Spotlight

Kudos to our October Community Star of the month!

Announcing Our 2024 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Dynamics 365 Community Newsletter - September 2024

Check out the latest community news

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,532 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 228,501 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Product updates

Dynamics 365 release plans