Article ID: 239899 - Last Review: October 27, 2006 - Revision: 4.2

SMS: Administrator Console Cannot Connect After Reinstallation

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

This article was previously published under Q239899

Expand all | Collapse all

SYMPTOMS

After fully removing and reinstalling Microsoft Systems Management Server (SMS) 2.0 on a server that is running Microsoft Windows NT or Microsoft Windows 2000 with a new site code that is alphanumerically greater than a previously installed site, SMS Administrator consoles cannot connect to the new site server.

Whether the SMS Administrator Console is excuted locally or remotely, the SMS Administrator Console is unable to connect to the SMS Site Database. The SMS Administrator Console displays the following message:

Connection Failed

Also, SMSprov.log contains the following error message:

11A][Mon 10/02/2000 19:50:57]:CSspClassManager::Initialize, Reading SQL db info from registry for sitecode WWW... [11A][Mon 10/02/2000 19:50:57]:NOTE:If the site has just been installed, the registry may not yet be set up and the follwing may be normal: [11A][Mon 10/02/2000 19:50:57]:
*
E:\OPALSP2\sdk_provider\nt\smsprov\SspClassManager.cpp(437) : Failed to find specific provider config, failing INIT this time around, will try again.

SMSProv.log is located on the server where the SMS Provider is installed. During SMS primary site installation, the SMS administrator can choose the location of the SMS Provider. It can be installed on the SMS site server, or a remote SQL server. After it is installed, it cannot be relocated unless SMS is reinstalled.

Back to the top

CAUSE

When you remove a site server, its namespace is not removed from the Windows Management Instrumentation (WMI) repository (previously known as WBEM) for the server.

Back to the top

WORKAROUND

To work around this behavior, on the site server provider perform the following steps:

Run the C:\Winnt\System32\Wbem\Wbemtest.exe utility locally.
Click Connect.
In the Server/Namespace box, type root\sms, and then click Login.
After you are connected, click Enum Classes.
Click Recursive, and then click OK.
Scroll down and double-click SMS_ProviderLocation().
Click Instances.
You should see two "SMS__ProviderLocation.SiteCode='XXX'" entries. Select the old site's site code, and then click Delete.
Double-click the __Namespace object.
Click Instances.
You should see two "__Namespace.name='site_XXX'" entries. Select the old site's site code, and then click Delete.
Close Wbemtest.