Applying Sms20o2k.Exe Hotfix Disables Client Functions

ID: Q238968

The information in this article applies to:

Microsoft Office 2000
Microsoft Systems Management Server version 2.0

SYMPTOMS

The "Instructions for Installing Microsoft Office 2000 with SMS 2.0" TechNet document is available at the following Microsoft Web site:

http://www.microsoft.com/SYSPRO/cdonline/o2ksms20.htm

This document includes the following information:

Apply the SMS 2.0 hotfix.
Before you install Office 2000, you need to apply the Sms20o2K.exe hotfix that is in the Office 2000 Resource Kit if your version of the Advertised Programs Manager is earlier than 100.1239.003

Applying the SMS 2.0 Hotfix
The Sms20o2K.exe file is necessary if you have a version of Smsapm32 that is earlier than to 100.1239.003. This fix is necessary for accurate status reporting when you install Office 2000 or any other Windows Installer application using SMS 2.0. Installing the hotfix to later versions, might cause problems, so check your version of Smsapm32 first.

If you perform the preceding steps to install the Office 2000 hotfix on a Systems Management Server (SMS) 2.0-based site that has been upgraded to Service Pack 1, file version mismatch problems may cause SMS client component failures.

CAUSE

This issue can occur if you apply the Sms20o2K.exe hotfix after applying SMS 2.0 Service Pack 1. The Sms20o2K.exe hotfix includes a version of the Apasetup.exe file that is earlier than the version of the Apasetup.exe file installed by SMS 2.0 Service Pack 1. Service Pack 1 contains cumulative hotfixes for SMS 2.0, and after it is applied to an SMS 2.0 site, the Sms20o2K.exe hotfix should not be applied.

RESOLUTION

To work around this issue, use either of the following methods:

Method 1

Re-apply SMS 2.0 SP1 to the site server. Note that this work around only takes effect after this propagates to all site systems and clients.

Method 2

Stop the SMS_Executive and SMS_Site_Component_Manager services.

Copy the service pack 1 source\smssetup\inboxes\clicomp.src\smsapm32\compver.ini file to the site server name\SMS\inboxes\clicomp.src\smsapm32 folder, where service pack 1 source is the source of your Service Pack 1 file, and site server name is your site server name.

Copy the service pack 1 source\smssetup\inboxes\clicomp.src\smsapm32\i386\Apasetup.exe file to the site server name\SMS\inboxes\clicomp.src\smsapm32\i386 folder.

Start the SMS_Executive and SMS _Site_Component_Manager services.

Verify all Client Access Point (CAP) servers receive the latest version of the Apasetup.exe file.

Permit clients to update by running the Smsls.bat file automatically during the log on process or manually from the CAP. Clients may also be manually updated by running the Systems Management tool in Control Panel and clicking Update on the Sites tab.

MORE INFORMATION

Client file version mismatch problems may generate the following entries in the Ccim32.log file:


Checking if component "Software Distribution" needs to be 
installed, upgraded or verified (offer index [4])$$
<CCIM32><Fri Aug 06 20:38:06.290 1999><thread=167 (0xA7)>
Component "Software Distribution" needs to be installed
$$<CCIM32><Fri Aug 06 20:38:06.290 1999><thread=167 (0xA7)>
Trying to open IPC connection with APM...
$$<CCIM32><Fri Aug 06 20:38:07.081 1999><thread=167 (0xA7)>
ERROR: Unable to establish a connection with APM - The system cannot find the file
specified.~~ $$<CCIM32><Fri Aug 06 20:38:13.089 1999><thread=167 (0xA7)>

NOTE: This error may be repeated for various optional components on the client computer.

Additional query words: prodsms smsapm32 o2k sms20o2k

Keywords : kbenv kbnetwork kbui kbSMS200
Version : WINDOWS:2000; winnt:2.0
Platform : WINDOWS winnt
Issue type : kbprb