SMS: Smsapm32 May Consume 100 Percent CPU Time on Windows NT SMS Clients

ID: Q240921

The information in this article applies to:

Microsoft Systems Management Server versions 2.0, 2.0 SP1

SYMPTOMS

When an advertisement is sent to clients, Smsapm32 may consume 100 percent of the CPU time on some clients and not run the advertisement. When this occurs, the following log entry may be generated:

SCHEDULER : Checking if a user is actually logged on.

CAUSE

This behavior occurs because Smsapm32 is attempting to determine whether a user is logged on or not and is getting stuck in a tight loop. This results in CPU time being consumed. During normal operation, the log entry should be followed within seconds by one of the following log entries:

SCHEDULER : A user is logged on to the system.

SCHEDULER : A user is not logged on to the system.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Systems Management Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English-language version of this fix should have the following file attributes or later:


   Date       Time  Version          Size    File name   Platform
   --------------------------------------------------------------
   9/20/99   3:48am 2.00.1380.1033   231,264 Abnwcli.dll  i386
   9/20/99   3:44am 2.00.1380.1033   256,864 Bindclin.dll i386
   9/10/99   7:49pm 2.00.1380.1023   158,544 Ccim32.dll   i386
   9/21/99   3:09pm                3,211,851 Clicore.exe  i386
   9/20/99   3:48am 2.00.1380.1033   157,536 Falclin.dll  i386
   9/20/99   3:49am 2.00.1380.1033   336,736 Mslmclin.dll i386
   9/20/99   3:44am 2.00.1380.1033   266,592 Ndsclin.dll  i386
   9/20/99   3:46am 2.00.1380.1033   408,848 Abnwcli.dll  Alpha
   9/10/99   7:49pm 2.00.1380.1023   253,200 Ccim32.dll   Alpha
   9/21/99   3:09pm                4,235,226 Clicore.exe  Alpha
   9/20/99   3:46am 2.00.1380.1033   285,968 Falclin.dll  Alpha
   9/20/99   3:46am 2.00.1380.1033   576,272 Mslmclin.dll Alpha
   8/05/99   6:55pm                      474 Basenta.ini
   8/05/99   6:55pm                      473 Basentx.ini
   8/05/99   6:55pm                      471 Basew9x.ini
   9/21/99   3:18pm                       67 Compver.ini

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

For additional information about this hotfix, click the article number below to view the article in the Microsoft Knowledge Base:

Q239564 SMS: Client Components Reinstalled During Periodic Verification

STATUS

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

MORE INFORMATION

To install the hotfix, follow these steps on the Systems Management Server (SMS) site server:

Log on to your site server using an account with administrative privileges.

On the site server, close the SMS Administrator console.

Run Q239564.exe and follow the directions in the wizard.

NOTE: The default Client Configuration Installation Manager (CCIM) polling interval is 23 hours. Therefore, it may take up to 23 hours to propagate the hotfixed files to the clients. To speed up this process, use any of the following methods:

Stop and restart the SMS Client Service on each client. For Microsoft Windows NT, simply stop and restart the service. For Microsoft Windows 95 or Microsoft Windows 98, a restart is required.

Create a software distribution for one of the Resource Kit tools (Setevnt.exe or Cliutils.exe), along with the appropriate parameters to start a CCIM work cycle. The tools are located on SMS 2.0 CD-ROM 2.

setevnt /q

Cliutils KICK "Client Configuration Installation Manager"

If you have the Networking Logon Client Installation option enabled, have users log off and back on.

Have users run SMSMan manually.

NOTE: You may need to restart Windows 95/98 clients after you install the hotfixed files to receive full hotfix functionality. To verify this, view the Clicore.log file after you install the hotfix. If you are required to restart, you see the following entry listed in the log file. Because of the nature of this hotfix, Microsoft recommends that you use a mandatory restart policy for all Windows 95/98 users after you install the hotfix.

Reboot required - disabling component until reboot
Manual:

Additional query words: prodsms

Keywords : kbSMS120 kbSMS120bug
Version : winnt:2.0,2.0 SP1
Platform : winnt
Issue type : kbbug