SMS: A Large .tmp File Is Created When You Install a Client

Hotfix Download Available
View and request hotfix downloads

View products that this article applies to.

This article was previously published under Q320066

SYMPTOMS

When you install or upgrade a client computer that is running Systems Management Server (SMS) 2.0, a large temporary (.tmp) file may be created in the %SystemRoot%\MS\SMS\Core\Bin folder on the client computer. Typically, this file is named ~glh000*.tmp. When this issue occurs, Clicore.exe may use 90 percent or more of the client's CPU resources. The .tmp file grows until the client runs out of hard disk space, and you receive an error message. The error message states that the client installation did not succeed and to contact your administrator.

Back to the top

CAUSE

This issue may occur if the Clicore.exe file becomes corrupted as it is copied to the client. This issue may also occur if the Clicore.exe file on the site server, client access point (CAP), logon point, or client is corrupted. The Clicore.exe file may be corrupted if any of the following conditions exist:

The Clicore.exe file has a different time and date stamp than the Clicore.exe file in the SMS 2.0 source.
The Clicore.exe file is a different size than the Clicore.exe file in the SMS 2.0 source.
When you run the clicore.exe /x command from a command prompt, a list of client installation files that are contained in the Clicore.exe file that are available for extraction does not appear.

Back to the top

RESOLUTION

Service Pack Information

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

288239 (http://support.microsoft.com/kb/288239/EN-US/ ) How to Obtain the Latest Systems Management Server 2.0 Service Pack

Back to the top

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English-language version of this fix for SMS 2.0 Service Pack 3 (SP3) sites should have the following file attributes or later:

   Date         Time   Version        Size     File name     Platform
   ------------------------------------------------------------------
   01-Mar-2001  18:50  2.0.1493.3258  586,512  Boot32nd.exe  Alpha
   01-Mar-2001  18:50  2.0.1493.3258  586,512  Boot32nw.exe  Alpha
   01-Mar-2001  18:50  2.0.1493.3258  586,512  Boot32wn.exe  Alpha
   01-Mar-2001  18:50  2.0.1493.3258  374,528  Boot32nd.exe  X86
   01-Mar-2001  18:50  2.0.1493.3258  374,528  Boot32nw.exe  X86
   01-Mar-2001  18:50  2.0.1493.3258  374,528  Boot32wn.exe  X86

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

Back to the top

How to Install the Hotfix

To install the hotfix, use the appropriate method.

Use the Hotfix Installer

NOTE: This method works only for Intel-based computers.

Create a folder in a location that is accessible to your SMS site servers.
Copy the update file (Q320066.exe) and platform folders to the new folder. Arrange the new folder structure so that the update file is located one folder "above" the platform folders.
From each of the primary and secondary SMS site servers in your environment, log on to your site server by using an account with administrator permissions.
Quit the SMS Administrator console, if it is running.
Run Q320066.exe, and then follow the instructions in the wizard.

Manual Installation

Create a folder in a location that is accessible to your SMS site servers.
Copy the platform folders that contain the hotfix files to the new folder.
From each of the primary and secondary SMS site servers in your environment, log on to your site server by using an account with administrator permissions.
Quit the SMS Administrator console, if it is running.
Stop all SMS services.
Replace the Boot32nd.exe file in the Sms_root_folder\Bin\Platform folder with the version from the hotfix.
Replace the Boot32nw.exe file in the Sms_root_folder\Bin\Platform folder with the version from the hotfix.
Replace the Boot32wn.exe file in the Sms_root_folder\Bin\Platform folder with the version from the hotfix.
Restart all SMS services.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Systems Management Server 2.0 Service Pack 5.

Back to the top

MORE INFORMATION

Corrupted Clicore.exe files have occurred in two scenarios:

The more common variation of this problem is addressed in hotfix Q287990. In this case, the corruption occurs during the remote client installation. The Q287990 hotfix includes changes to the server-side components that are responsible for remote client installation. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
287990 (http://support.microsoft.com/kb/287990/EN-US/ ) Large .tmp File Is Created When You Install or Upgrade an SMS 2.0-based Client
The hotfix that is described in this article addresses a less common variation of the problem. In this case, files may become corrupted while the client copies files to itself.

You can apply both of these hotfixes if you suspect that you are experiencing the issue that is described in this article. The hotfixes are complementary; they contain different files. The hotfix that is described in this article contains client-side files. The Q287990 hotfix contains server-side files.

Back to the top