SMS: SMSMon32 Process Hangs on Clients After Applying SMS 2.0 SP1

• Microsoft Systems Management Server version 2.0

SYMPTOMS

After you upgrade a Systems Management Server (SMS) 2.0 site to Service Pack 1 (SP1), client computers connected to the site may respond slowly or even appear to stop responding (hang). On these computers, the Smsmon32.exe process may be taking up most of the CPU processing time and not yielding to other processes.

CAUSE

The Smsmon32.exe process may hang during client upgrades to SP1 for any of the following reasons:

• One or more sites were upgraded in a single domain, multiple-site model. For additional information, see the following article in the Microsoft Knowledge Base:




Q236596 SMS: Client Components Fail to Install with SMS 2.0 SP1

• When clients from a site that has not been upgraded log on and run the SMS logon script, they receive the updated base components from the SMS logon point. However, when the client connects to the Client Access Point (CAP), a version mismatch (because the CAP is not upgraded) could cause Smsmon32.exe to hang on the client computers.

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).

When a client receives the version mismatch, a complete removal and reinstallation of the SMS client is necessary to correct the problem.

If there are active outstanding advertisements available for the clients when they upgrade from SMS 2.0 to SP1, Smsmon32.exe may appear to hang and the client computer may need to be restarted.

When the client computers reach this point, a complete removal and reinstallation of the SMS client is necessary. After the reinstallation is finished, the client has the updated components from the CAP server and functions properly.

If the client computers belong to more than one site, and if one of the sites no longer exists, Smsmon32.exe may hang when trying to contact the nonexistent site during the upgrade from SMS 2.0 to SP1. To work around this issue:

1. Stop all SMS services on a Windows NT client computer.



2. Edit the registry. Delete the site code of the nonexistent site from the following registry key:




HKEY_LOCAL_MACHINE\Microsoft\SMS\Client\InstalledSites

3. Start the client services.

MORE INFORMATION

To avoid some of these issues, see the following article in the Microsoft Knowledge Base before you upgrade SMS 2.0 to SP1:

Q238780 Best Practices for Applying SMS 2.0 SP1

Q236325 How to Obtain the Latest Systems Management Server Service Pack

Q237543 SMS: Service Pack Upgrade Considerations for Clients

Q236596 SMS: Client Components Fail to Install with SMS 2.0 SP1

Q238864 SMS: Windows 95/98 Clients Stop Responding or Become Unstable After SP1 Upgrade

Additional query words: multisite smsfaqtop

Keywords : kbSMS200 smssetup prodsms
Version : winnt:2.0
Platform : winnt
Issue type : kbprb