Unable open SCCM console
Hi,
I have problem to open my SCCM console and i get this message
" 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. For more information, see "How to Configure DCOM Permissions for Configuration Manager Console Connections" in ConfigMgr Help. "
After check the SmsAdminUI.log, i get below error message
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][10/27/2009 4:55:22 PM] :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";
};can anyone advice how to solve it? Thanks in advanced
Regards,
Chungb
Answers
- Just a quick update. I have found some install after SP2 had cleared the PATH environment variable entries. I re-added the PATH from a working Config Manager server (Test server cofigured the same as this one). After a reboot, the server has come back good and appears to be fully operational.
- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorMonday, November 09, 2009 3:59 AM
All Replies
- Hi Chungb,
Please run Wbemtest.
Connect to root\sms --> Enum Classes-->Select recursive- -->Select SMS_ProviderLocation () Click on instances
Could you find that there was any entry for this?
Also, on your SCCM database server, is there any Failure Audit messages in Event Viewer?
- Hi,
Yes, when i click on instances, it appear to have one object there " SMS ProviderLocation.SiteCode=..... ".
SCCM database server didn't show any error.
I will try to reinstall the .Net framework as i suspect it causing problem.
Regards,
Chung Boon
- Hi Eric,
I found this forum post from google as I too am affected by this same issue.
I have the same AdminUI error. Doesnt matter if if is a local console or on a remote computer, the same error appears. I have just applied SP2 however the site was functional after the upgrade.
When attempting the WBEMTEST issue above, when i clicked on instances, WBEMTEST crashed! (so assume that is bad).
We need to rebuild alot of servers soon so I am inclined to get started on reimaging and restoring this site server, but I was hoping for a quick fix if possible.
Nathan - Just a quick update. I have found some install after SP2 had cleared the PATH environment variable entries. I re-added the PATH from a working Config Manager server (Test server cofigured the same as this one). After a reboot, the server has come back good and appears to be fully operational.
- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorMonday, November 09, 2009 3:59 AM

