Here’s a new Knowledge Base article we published. This one talks about an issue where installing a System Center 2012 Operations Manager server fails with error 0x80131604.
Installing a System Center 2012 Operations Manager (OpsMgr) Management server fails with the following error:
Error: :Exception running sql string sp_configure 'show advanced options', 1 RECONFIGURE : Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Ad hoc update to system catalogs is not supported. Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install. [14:14:01]: Error: :StackTrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
Error: :RunAdminScripts failed with the following exception: : Threw Exception.Type: System.Reflection.TargetInvocationException, Exception Error Code: 0x80131604, Exception.Message: Exception has been thrown by the target of an invocation.
NOTE Operations Manager log files are located at %LocalAppData%\SCOM\Logs
An "Ad hoc update to system catalogs is not supported" error is encountered during the Intelligent Queue installation. This error means that SQL Server would not allow a change to its catalogs. This can occur if the setting for "allow updates" has been changed and set to 1. Starting with SQL Server 2005, direct updates to the system tables are not supported so we need to turn this setting off to make any further changes in the catalog and tables.
The SQL 'allow updates' option is present in the sp_configure stored procedure.
To test if this is the cause of your issue, manually run query below against the Master database:
sp_configure 'show advanced options', 1
"RECONFIGURE" (Without quotes)
If you are experiencing the issue described in this article, the command will fail with the message "Exception.Message: Ad hoc update to system catalogs is not supported."
To work around this issue, change the value to "0" with the query below. This will allow the SQL database to receive any changes/updates to its catalog.
EXEC sp_configure ‘allow updates’, 0
This will run successfully.
Once completed, restart the installation of the management server.
For the most current version of this article please see the following:
2713047 - Installation of a System Center 2012 Operations Manager server fails with Exception Error Code: 0x80131604
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
So I experienced this and made the changes to the DB, but now if I run setup again on the management server I started on it shows as a new install, will the upgrade continue if I continue?