SMS: Service Manager Does Not Connect to Secondary Site Servers

ID: Q214979

The information in this article applies to:
  • Microsoft Systems Management Server version 2.0
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

Systems Management Server Service Manager may fail to connect to secondary site servers, though connection to primary site servers is unimpeded. When you try to connect to a secondary site server, you get a message stating:

error communicating with the specified site and server
Because of this problem, you cannot control services of secondary sites nor modify the logging on features using Service Manager from the primary site server.


WORKAROUND

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).


To enable logging on services for a secondary site, use the remote management ability of Regedt32.exe:

  1. Click Run on the Start menu and type Regedit.


  2. Under the Registry menu, click Connect Network Registry.


  3. Type the name of the secondary site server in the Computer name text field.


  4. Once connected to the secondary server, expand Hkey_Local_Machine, then in turn expand Software, Microsoft, SMS, and Tracing.


  5. Click the component for which you want to enable logging on.


  6. In the right window pane, click Enabled and change the value to 1.


  7. Click OK to save the changed value.

    NOTE: To change the log file size, modify the MaxFileSize value in the right window pane.


Whether the component for which you just enabled logging on is a child thread of a service or a service of its own, you must stop and restart that service for the logging on to take effect.


STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 2.0. This problem has been corrected in the latest U.S. service pack for Systems Management Server version 2.0. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Additional query words: prodsms

Keywords : kbSMS200 kbSMS200bug kbSMSUtil kbSvcMgr
Version : winnt:2.0
Platform : winnt
Issue type : kbbug


Last Reviewed: July 8, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.