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

ID: Q235808

The information in this article applies to:

Microsoft Systems Management Server versions 2.0, 2.0 SP1

SYMPTOMS

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.

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
   -----------------------------------------------------------
   09/15/1999 02:43a             622,910  Apasetup.exe   Alpha
   09/15/1999 02:55a                  67  Compver.ini    Alpha
   09/15/1999 02:43a  1380.1031  279,824  Smsapm32.exe   Alpha
   09/15/1999 02:48a             362,522  Apasetup.exe   Intel
   09/15/1999 02:55a                  67  Compver.ini    Intel
   09/15/1999 02:44a  1380.1031  210,800  Smsapm32.exe   Intel

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

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:

Stop the SMS Executive and SMS Site Component Manager services on the site server.

Replace the SMS\Inboxes\Clicomp.src\Smsapm32\Compver.ini file with the Compver.ini file from the hotfix.

Replace the SMS\Inboxes\Clicomp.src\Smsapm32\Platform\Apasetup.exe file with the Apasetup.exe file from the hotfix.

Replace the SMS\Bin\Platform\Smsapm32.exe file with the Smsapm32.exe file from the hotfix.

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 : kbSMS200 kbSMS200bug kbSMS120 kbSMS120bug
Version : winnt:2.0,2.0 SP1
Platform : winnt
Issue type : kbbug