SMS: Client Install Fails on Windows NT 4.0: CLICORE.EXE Returns Exit Code=1

ID: Q220858

The information in this article applies to:

Microsoft Systems Management Server version 2.0

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

Windows NT Workstation 4.0 computers that have had the Zero Administration Kit (ZAK) modifications applied fail Systems Management Server 2.0 client installation.

The workstation's %windir%\Ms\Sms\Logs\Ccim32.log file shows the following:

Process "clicore.exe /S" finished; exit code = 1. <CCIM32>
ERROR - base component "SMS Client Base Components" install state set to "" <CCIM32>

When you review the Clicore.log, there is no indication that problems were encountered during installation.

The result is that the Cliex32.dll process never begins and the client installation does not successfully complete.

CAUSE

The Zero Administration Kit (ZAK) modification adds the following two registry values with the data type REG_SZ:


   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\temp=%SystemDrive%\temp

-and-


   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\tmp=%SystemDrive%\temp

This causes the Systems Management Server 2.0 client installation to fail. The corrected data type is REG_EXPAND_SZ.

WORKAROUND

Changing the data type for the preceding values from REG_SZ to REG_EXPAND_SZ allows the Systems Management Server 2.0 client installation to complete.

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

Record the existing values, and then delete them.
1. Start the Registry Editor (Regedt32.exe).
2. Locate the temp value under the following key in the registry:
```
         HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\ 
 
```
3. On the Edit menu, click String, record the value, and then click OK.
4. On the Edit menu, click Delete, and then click Yes.
5. Locate the tmp value under the following key in the registry:
```
          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\  
```
6. On the Edit menu, click String, record the value, and then click OK.
7. On the Edit menu, click Delete, and then click Yes.

Add the values back to the registry with the correct data type.

Locate the following key in the registry:


          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\

On the Edit menu, click Add Value, and then add the following registry value:


         Value Name: temp
         Data Type:  REG_EXPAND_SZ
         Value:      Enter value recorded for temp in step a.

On the Edit menu, click Add Value, and then add the following registry value:


         Value Name: tmp
         Data Type:  REG_EXPAND_SZ
         Value:      Enter value recorded for tmp in step a.

Quit Registry Editor.

STATUS

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

MORE INFORMATION

For additional information, please see the following article in the Microsoft Knowledge Base:

Q222967 ZAK Client Setup Does Not Create TEMP Folders Correctly

Additional query words: prodsms client installation

Keywords : kbClient kbSMS200 kbSMS200bug
Version : winnt:2.0
Platform : winnt
Issue type : kbbug