Home > SCCM > Could not connect to the configmgr site db

Could not connect to the configmgr site db

Well, I just lost an hour figuring out why I could not connect to the SCCM db this morning while other co-workers have no problem at all, so I thought to share the troubleshooting steps…

the exact error is: The 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. 
 

-logon to a site server and open the admin console with the same account : no problem

-logon to another client with the admin console installed (same account): no problem

-launch dcomcnfg and verify that “enable distributed com on this computer”  is checked (you can find that when you open the properties of your computer) : ok

-launch wbemtest and try to connect to \\siteserver\root\sms (modify the siteserver with your servername) : nok

-launch wmidiag and verify if all is well : nok

-check the smsadminui.log on your client

what do we find here:

[9][3/12/2009 9:38:36] :Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException\r\nThe ConfigMgr Administrator console could not connect to the ConfigMgr site database. Verify your user has read permissions to the ConfigMgr site and then try to connect again.
\r\n   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)
   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.BuildTreeWorker()\r\nAccess is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))
\r\nSystem.UnauthorizedAccessException\r\nAccess is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))\r\n   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

-last step: delete the profile under which you are attempting to launch the admin console

this did the trick for me!

Categories: SCCM Tags:
  1. No comments yet.
  1. No trackbacks yet.