The Administrator console fails to load and reports a WBEM error

Article translations Article translations
Article ID: 198652 - View products that this article applies to.
This article was previously published under Q198652
Expand all | Collapse all


When you try to start the SMS Administrator console, you may receive an error message that is similar to the following:
MMCAdminUI WBEM Error: (Error executing query (T_WbemSyncQueryToContainer))

Error : WBEM_E_FAILED Operation: ExecQuery ParameterInfo: select SiteCode, SiteName from SMS_Site where ReportingSiteCode="" Error Description: SQL Err>> #10025 Sev 9: Possible network error: Write to SQL Server Failed. ConnectionWrite (GetOverLappedResult()). NEXT: SQL Err>> #10005 Sev 1: DBPROCESS is dead or not enabled. (null)

The Adminui.log file may contain an error message that is similar to the following:
Info(ConnectServer): Connecting to server.
Network : \\SMS2003L116\root\sms\site_RA1
Wbem call failed: T_WbemSyncEnumToContainer_Core,
return code: -2147217407
Wbem call failed: T_WbemSyncEnumToContainer_Core,
return code: -2147217407 Query select SiteCode,
SiteName, ServerName, BuildNumber from SMS_Site where ReportingSiteCode="" fails or returns empty resultset. Query select * from SMS_Identification also fails or returns empty resultset SiteCode - SiteServerName , Provider Version : 2.50.3174.1003 SiteBuildNumber is 1239 Failed to set the connection.
error code: -2147217407


This error message can be caused by the SQL Server being out of available user connections.


To resolve this problem, increase the number of SQL Server user connections. To do this, perform the following steps:
  1. Start SQL Server Enterprise Manager.
  2. Right-click the SQL Server server name and click Configure on the shortcut menu.
  3. In the Server Configuration/Options dialog box, scroll to the User Connections entry and increase the number of connections in the Current column.
After making this change, you must stop and start the SQL Server service for the change to take effect. You can stop and start the service through the SQL Server Service Manager, Control Panel Services, or the command line with the net stop mssqlserver and net start mssqlserver commands.


Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.


Article ID: 198652 - Last Review: February 27, 2007 - Revision: 5.3
  • Microsoft Systems Management Server 2003
  • Microsoft Systems Management Server 2.0 Standard Edition
kbprb kbwbem KB198652

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from