Microsoft KB Archive/871164

= &quot;Error communicating with the specified SMS Site Server&quot; error message when you try to start SMS Service Manager in SMS 2.0 =

Article ID: 871164

Article Last Modified on 2/7/2007

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition

-





SUMMARY
''When you try to start Microsoft Systems Management Server (SMS) Service Manager in the SMS Administrator console, you receive an error message, and errors may be logged in the CompMgrProv.log log file.

This error can have many causes. This article contains troubleshooting steps that you can use to help resolve the error.''



SYMPTOMS
When you try to start Microsoft Systems Management Server (SMS) Service Manager in SMS 2.0, you receive the following error message:

Error communicating with the specified SMS Site Server.

Additionally, the following errors may appear in the CompMgrProv.log log file on the site server: ### CompMgrProv [05-09-02 16:18:53] *** ERROR *** CCompMgrProv::CreateInstanceEnumAsync: CheckSecurityRights failed. Return code: 0x80041003 ### CompMgrProv [07-30-02 15:50:02] *** ERROR *** CCompMgrProv::GetServiceControlsAccepted: serviceManager.QueryServiceStatus failed. Return code: 0x00000001



RESOLUTION
To troubleshoot this error message, follow these steps to make sure that your account has the required permissions:
 * 1) Click Start, click Run, type wbemtest, and then click OK.
 * 2) Click Connect, and then click Login.

Note By default, the Server \ Namespace box contains root\default.
 * 1) Click Query, type select * from SMScomponent, and then click Apply.

If you receive an &quot;Access Denied&quot; error message, make sure that SMS 2.0 with Service Pack 5 (SP5) or a later version of SMS is installed on your computer. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

299435 Cannot run SMS Service Manager after you apply a hotfix

After you complete this procedure, you may receive the following error message:

Number: 0x80041013

Facility: WMI

Description: Provider load failure

If you receive this error, the following error may appear in the Wbemcore.log log file: Loading provider(Wed Jul 31 11:09:29 2002) : Failed to CoGetClassObject provider SMS Component Management Provider: error code 0x80040154 (Class not registered) Error 80040154 occurred executing queued request Additionally, the following error may appear in the application log: Event ID: 12

Description: Failed to CoGetClassObject for provider &quot;SMS Component Management Provider&quot;. Class not registered (0x80040154). If you receive these errors, the SMS Component Management Provider (Cmprov.dll) may not be correctly registered. To correct this problem, follow these steps:  Click Start, click Run, type regedit, and then click OK. Make sure that the following subkeys exist in the registry:     </li></ul>

Each subkey contains an entry that contains the path of the Cmprov.dll file and a ThreadingModel entry whose value is &quot;Both.&quot;</li> If the subkeys are missing or are not complete, you can export the subkeys from a working SMS site server, and then import the subkeys on the computer where they are missing.</li></ol>

If the site server is running on a member server, make sure that the SMS Admins group has the required permissions to the namespace. To do this, use an account that is a member of the SMS Admins group or an account that is a member of a global group that is a member of the SMS Admins group. To make sure that the SMS Admins group has the required permissions, follow these steps:
 * 1) Click Start, point to Programs, point to Administrative Tools, and then click Computer Management.
 * 2) In the console tree, double-click Services and Applications, right-click WMI Control, and then click Properties.

Note You may have to click to select WMI Control before the Properties option is available on its shortcut menu.
 * 1) In WMI Control Properties, click the Security tab.
 * 2) Expand Root, click SMS, and then click the Security button.
 * 3) Make sure that the SMS Admins group has the following permissions:
 * 4) * Execute Methods
 * 5) * Provider Write
 * 6) * Enable Account
 * 7) * Remote Enable

After you have confirmed that the SMS Admins group has the required permissions, make sure that you are not experiencing the problem that is described in article 215015. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

215015 The SMS Admins group needs launch permissions to the Windows Management service

Make sure that your account is not a member of a nested group. SMS does not enumerate nested groups. When groups are members of other groups, SMS can discover only the first level of membership. For more information, see the &quot;Using Systems Management Server 1.2 and 2.0 with Windows 2000&quot; compatibility white paper. To obtain this white paper, visit the following Microsoft Web site:

http://www.microsoft.com/technet/sms/20/smswin2k.mspx

Make sure that the account that is listed in the  subkey has the Log on locally user right. To do this, follow these steps:
 * 1) Click Start, point to Programs, point to Administrative Tools, and then click Local Security Policy.
 * 2) Double-click Local Policies, and then click User Rights Assignment.
 * 3) Double-click Log on locally.
 * 4) Make sure that the account is listed, or that the account belongs to a group that is listed.

If you recently installed the SMS 2.0 Service Pack 4 (SP4) Hotfix Rollup Package (HRP) on your site servers and remote administration computers, the remote administration computers may not have the updated SMS Component Manager (Compmgr.exe). When you apply the HRP to a computer that has only the SMS Administrator console, the HRP Setup program does not copy the Compmgr.exe file to the \SMSAdmin\Bin\I386 folder.

If you experience connection problems after you apply the HRP to remote administration computers, manually update the Compmgr.exe file on the remote administration computers. To do this, quit the SMS Administrator console and then copy the Compmgr.exe file from the HRP source to the \SMSAdmin\Bin\I386 folder on each remote administration computer that experiences the problem.

Keywords: kbsmsutil kbsmsadmin kberrmsg kbtshoot kbsecurity kbmisctools kbprb KB871164

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.