What I did.

I created sql logins for the computer accounts of the site server

 

1. preinst /stopsite

2. backup database

3. restore database on new sql

4. gave admin permissions on sql server

5. Run setup and changed the sql name

I got errors

[6][05-04-2011 13:52:35] :Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException\r\nThe ConfigMgr console could not connect to the ConfigMgr site database. Verify that this computer has network connectivity to the SMS Provider computer and that your user account has Remote Activation permissions on both the ConfigMgr site server and SMS Provider computers. For more information, see "How to Configure DCOM Permissions for Configuration Manager Console Connections" in ConfigMgr Help.\r\n   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)
   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.BuildTreeWorker()\r\nThe ConfigMgr Provider reported an error.
\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe ConfigMgr Provider reported an error.\r\n   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)
   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nConfigMgr Error Object:
instance of __ExtendedStatus
{
 Operation = "ExecQuery";
 ParameterInfo = "SELECT * FROM SMS_Site WHERE ReportingSiteCode = ''";
 ProviderName = "WinMgmt";
};

Error Code:
ProviderLoadFailure
\r\nSystem.Management.ManagementException\r\nProvider load failure \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()\r\nManagementException details:
instance of __ExtendedStatus
{
 Operation = "ExecQuery";
 ParameterInfo = "SELECT * FROM SMS_Site WHERE ReportingSiteCode = ''";
 ProviderName = "WinMgmt";
};
\r\n

6. I did a reinstall of the sccm provider on the sccm server..

Still errors..

7. preinst /stopsite

8. run setup to change back to old SQL..

How Can I get the DB without errors on the new SQL box?

So you followed this?

http://technet.microsoft.com/en-us/library/bb680707.aspx

 

4. gave admin permissions on sql server

What about the computer account of the siteserver?

I added the computer account of the primary site server to the local admin group.

I used the steps as written above.

Is it because I added the computer accounts using sql before I added the Database?

I did this same for WSUS and that worked fine..

 

 

It should not matter in which order you added the account.

 

Is there something else to check is the log showing you something?

Now that I reversed the change I get the console op and running ...

After the transfer I used the sccm toolkit mp troubleshooter and found nu issues connecting to the DB.. All checks passed 

Review SQL server security logs using SQL management studio.

I found the issue solve it in my other post on WSUS ... had to do with the default database that was configured..

• Marked as answer by LA1976 Wednesday, April 06, 2011 1:49 PM

Can you please elaborate on what you did or link to the other post that did have the full answer.  This post is less than helpful without it.

Is your issue with CM07 or CM12? Have you performed a Site Reset after restoring SQL?