Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/235808

From BetaArchive Wiki
Knowledge Base

SMS: Smsapm32.exe May Report Status Incorrectly If Package Starts Another Instance

Article ID: 235808

Article Last Modified on 10/27/2006


  • Microsoft Systems Management Server 2.0 Standard Edition
  • Microsoft Systems Management Server 2.0 Service Pack 1

This article was previously published under Q235808


Smsapm32.exe may incorrectly report the successful completion of a package even though it may not have succeeded. This behavior can occur if the package starts another instance of itself to complete execution and the second instance does not finish successfully. A Microsoft Windows 2000 upgrade using Winnt32.exe is one package that exhibits this behavior.


To resolve this problem, obtain the latest service pack for Systems Management Server version 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

236325 How to Obtain the Latest Systems Management Server 2.0 Service Pack


Microsoft has confirmed this to be a problem in Systems Management Server version 2.0 This problem was first corrected in Systems Management Server version 2.0 Service Pack 2..


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

  1. Stop the SMS Executive and SMS Site Component Manager services on the site server.
  2. Replace the SMS\Inboxes\Clicomp.src\Smsapm32\Compver.ini file with the Compver.ini file from the hotfix.
  3. Replace the SMS\Inboxes\Clicomp.src\Smsapm32\Platform\Apasetup.exe file with the Apasetup.exe file from the hotfix.
  4. Replace the SMS\Bin\Platform\Smsapm32.exe file with the Smsapm32.exe file from the hotfix.
  5. Restart the SMS Executive and SMS Site Component Manager services.

NOTE: The default Client Configuration Installation Manager (CCIM) polling interval is 23 hours. Therefore, it may take up to 23 hours for the hotfix files to be propagated to the clients. To speed up this process, you can stop and restart the SMS Client service on each client. You can also create a software distribution for one of the Resource Kit tools (Setevnt.exe or Cliutils.exe) along with the appropriate parameter(s) to start a CCIM work cycle. For information about the proper syntax to use with these tools, see the Resource Kit documentation.

Additional query words: prodsms

Keywords: kbqfe kbhotfixserver kbbug kbfix kbsms200sp2fix KB235808