SCCM Console not connecting to SMS Provider

Wednesday, January 07, 2009 2:29 PMJoshua6

0
Sign In to Vote
I have an issue every morning that my console on my SCCM server does not connect to the SMS database. I have configured WMI and DCOM permissions per Microsoft. This happens every morning on the SCCM Server and my SCCM XP console. This is a portion of the SCCM\AdminUI\Logs\SmsAdminUI.log:

Error Code:

Unexpected
\r\nSystem.Management.ManagementException\r\nUnexpected error \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][1/7/2009 8:19:03 AM] :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";
};
- Reply
- Quote

Answers

Thursday, January 08, 2009 12:15 PMJoshua6

0
Sign In to Vote
Sounds good, I will give them a call.

Thanks for your help anyway.

Josh
- Marked As Answer byJoshua6 Thursday, January 08, 2009 12:15 PM
- Reply
- Quote

All Replies

Wednesday, January 07, 2009 6:56 PMDonnie Taylor

0
Sign In to Vote
You said this happens on the server itself? Odd. The next time it happens, try this:

Start, Run, type "wbemtest".
Hit connect.
Change the Namespace field to "root\sms\site_<SITECODE>" (change the <SITECODE> to your site) and select connect.
Select query, and paste this in the "Enter Query" field - SELECT * FROM SMS_Site
Does it return any values when you hit apply?

Also, is this console on the SCCM server ONLY connecting to the local server? Are there any processes that run in the mornings - perhaps a SQL backup or something along those lines?
- Reply
- Quote
Wednesday, January 07, 2009 8:16 PMJoshua6

0
Sign In to Vote
Yes, it is only connecting to the local SCCM server. The only fix is a reboot. Firewall is off. The SCCM backup runs everynight at 10 PM. I cannot pinpoint if it is the SCCM Site Server having the issue, or the remote SQL Server.

When I run the command above, I receive this error in the MOF field:

instance of SMS_ExtendedStatus
{
CauseInfo = "";
Description = "Unable to get SQL connection.";
ErrorCode = 3242263810;
File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspobjectquery.cpp";
Line = 1861;
Operation = "ExecQuery";
ParameterInfo = "SELECT * FROM SMS_Site
\n";
ProviderName = "WinMgmt";
SQLMessage = "[IM005][0][Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_DBC failed";
SQLSeverity = 0;
SQLStatus = 0;
StatusCode = 2147749889;
};
- Reply
- Quote
Wednesday, January 07, 2009 8:39 PMWallyMSFT, Owner

0
Sign In to Vote
If you can't connect and run a query from wbemtest on the site server, then you have issues (of course you already knew that by posting here). I am not sure this is something we can fix in the forums, so I'd open a case with customer support on this one.

Good luck with it.
Wally Mead
- Reply
- Quote
Thursday, January 08, 2009 12:15 PMJoshua6

0
Sign In to Vote
Sounds good, I will give them a call.

Thanks for your help anyway.

Josh
- Marked As Answer byJoshua6 Thursday, January 08, 2009 12:15 PM
- Reply
- Quote
Thursday, June 25, 2009 1:05 AMNilanga Karunathilake

0
Sign In to Vote
Was there a fix to this problem? I'm experiencing intermittent errors similar on my SCCM Server.
Nilanga
- Reply
- Quote
Thursday, July 23, 2009 3:50 AMTronz-Omega

0
Sign In to Vote
Hi,

I seem to have the same problem. However i realised that there is some issue with passing WQL (SQL for WMI). I restarted WMI and SMS agent host service on the site server (or the affected server) and that fixed the problem.

Dont know why this happens but this is the solution to it.

Thanks
- Reply
- Quote