I’ve had some right good fun with Management Reporter recently, actually not so much fun, but the bane of my life (in the course of pretty much one day). And over the new few posts I’m going to share the trials and tribulations I have undergone.
A recent upgrade of Management Reporter resulted in a fairly generic error message being displayed while trying to configure the legacy connector (the connector type is not important for this error):
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):
02/11/2015 09:40:26 - Dropping [CLIENT_X\Joe Bloggs]... 02/11/2015 09:40:26 - .Net SqlClient Data Provider: Msg 15138, Level 16, State 1, Line 1 The database principal owns a schema in the database, and cannot be dropped. 02/11/2015 09:40:26 - Script execution error. The executed script: DROP USER [CLIENT_X\Joe Bloggs];
I opened up SQL Server Management Studio, expanded the Databases node, expanded Management Reporter and then expanded the Schema node.
Working down the list one by one checking the properties I found that the db_backupoperator schema had been changed to Joe’s ID:
After changing the Schema Ownerback to db_backupoperator, I was able to get past this error.
Stay tuned, as in the next post, I’ll cover the next problem I encountered in the upgrade of Management Reporter.