Database Migration fails with the Error: Ad hoc update to system catalogs is not supported. (4253460)

When running the MessageStatsMigration.sql Script, or durig MessageStats installation the following errors are displayed:

MessageStats Installation:

Database Creation Successful - Database Migration Failed (See below)

Details:

Attempting to load SQL Script file - C:\Program Files\Quest Software\MessageStats\SQL\MessageStatsMigration.sql
SQL Script File Successfully Loaded

Attempting to Migrate Application Specific Database Objects
ERROR OCCURRED DURING DATABASE OBJECT MIGRATION WHILE EXECUTING THE FOLLOWING:

IF (SELECT CAST(LEFT(CAST(SERVERPROPERTY('ProductVersion') AS NVARCHAR(10)),
                CHARINDEX('.',CAST(SERVERPROPERTY('ProductVersion') AS NVARCHAR(10)))-1) AS INT)) > 8
BEGIN
  EXEC ('sp_configure ''show advanced options'', 1');
  EXEC ('RECONFIGURE');
  EXEC ('sp_configure ''Ole Automation Procedures'', 1');
  EXEC ('RECONFIGURE');
END
THE ERROR DESCRIPTION IS:
Ad hoc update to system catalogs is not supported

When Running MessageStatsMigration.sql

Killing database connections
DROP INDEX dbo.T_CustomRecipients.IX_T_CustomRecipientsDeletedObjectDate;DROP INDEX dbo.T_CustomRecipients.IX_T_CustomRecipientsOrgGUIDLastGatheringDate;DROP INDEX dbo.T_CustomRecipients.IX_T_CustomRecipientsDN;DROP INDEX dbo.T_CustomRecipients.IX_T_CustomRecipientsX500DN;DROP INDEX dbo.T_CustomRecipients.IX_T_CustomRecipientsOrgDNEmail;
Warning! The maximum key length is 900 bytes. The index 'IX_T_MailboxesMbxX500DN' has maximum length of 1024 bytes. For some combination of large values, the insert/update operation will fail.
Warning! The maximum key length is 900 bytes. The index 'IX_T_ExchMailEnabledObjectsOrgX500DN_2' has maximum length of 1040 bytes. For some combination of large values, the insert/update operation will fail.
Warning! The maximum key length is 900 bytes. The index 'IX_T_ExchMailEnabledObjectsOrgDNEmail_2' has maximum length of 1408 bytes. For some combination of large values, the insert/update operation will fail.
Changed language setting to us_english.
Changed language setting to us_english.
Changed language setting to us_english.
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 5808, Level 16, State 1, Line 1
Ad hoc update to system catalogs is not supported.
Changed language setting to us_english.
Changed language setting to us_english.
Changed language setting to us_english.
Changed language setting to us_english.
Changed language setting to us_english.
Changed language setting to us_english.
Changed language setting to us_english.
Warning! The maximum key length is 900 bytes. The index 'IX_T_LN_UsersMailConfiguration_MailFile' has maximum length of 1024 bytes. For some combination of large values, the insert/update operation will fail.
Changed language setting to us_english.
Changed language setting to us_english.
Caution: Changing any part of an object name could break scripts and stored procedures.
Changed language setting to us_english.
Changed language setting to us_english.

An "Ad hoc update to system catalogs is not supported" error is encountered during the Database Migration. 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, run the following queries against the Master database:

sp_configure 'show advanced options', 1

Then run

"RECONFIGURE"  (Without quotes)

The above test should fail with the same error message "Ad hoc update to system catalogs is not supported." If the "Allow Updates" option is set in the sp_configure stored proceedure.

WorkAround:

To work around this issue run the following commands to change the "allow updates" option back to zero

EXEC sp_configure ‘allow updates’, 0

Then run

"RECONFIGURE" (Without quotes)

Once you have run this successfully the MessageStats Database Migration should run successfully.