As mentioned in the last post, I’ve been having some fun with Management Reporter recently. Unfortunately, Integration Manager the errors it produces are often less than useful. After resolving the issues with the schema owner, SQL Timeout and SQL Login, the attempt to upgrade Management Reporter produced another generic error message:
Management Reporter 2012
An error occurred while configuring 'Management Reporter Application Service'. Check the deployment log for details.
I opened up the deployment log and quickly found the error (I’ll only post the significant parts of the log as it is quite long:
04/11/2015 15:12:37 - .Net SqlClient Data Provider: Msg 9002, Level 17, State 4, Line 25 The transaction log for database 'ManagementReporter' is full due to 'ACTIVE_TRANSACTION'.
04/11/2015 15:12:37 - The database deployment failed. Additional information: Microsoft.SqlServer.Dac.DacServicesException: Could not deploy package. Error SQL72014: .Net SqlClient Data Provider: Msg 9002, Level 17, State 4, Line 25 The transaction log for database 'ManagementReporter' is full due to 'ACTIVE_TRANSACTION'.
This Management Reporter database is approximately 120GB in size, and the upgrade being attempted was from an older version (if I recall correctly) about CU6 to CU12; between these versions the database structure changed substantially and it was trying to make a copy of a huge table to change the table name.
The server in question was a little restricted on size to grow just for Management Reporter and the history of the reports wasn’t actually required. After a discussion with the people involved on the client side it was determined that a reimplementation of Management Reporter and import of the building blocks would be the best route to go down.
The import of the building blocks has a story of it’s own, which I will cover next.