Article ID: 266232
Article Last Modified on 10/25/2006
APPLIES TO
- Microsoft Systems Management Server 2.0 Standard Edition
- Microsoft Systems Management Server 2.0 Service Pack 1
- Microsoft Systems Management Server 2.0 Service Pack 2
- Microsoft Systems Management Server 2.0 Service Pack 3
This article was previously published under Q266232
SYMPTOMS
On some Microsoft Windows 9x-based clients, when you install the Remote Control agent, the computer may stop responding (hang) while displaying low-resource error messages. While the computer hangs, a background process named Winoldap runs. When this issue occurs, the Remctrl.log file contains the following text:
NOTE: This error message is an example from a computer running Windows 95. Error messages may differ between operating systems.
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:
288239How to Obtain the Latest Systems Management Server 2.0 Service Pack
Hotfix Information
To resolve this problem for English-based clients, obtain the latest service pack for Systems Management Server version 2.0. To resolve this problem for International clients, obtain the latest service pack or obtain the Systems Management Server version 2.0 Service Pack 4 (SP4) Hotfix Rollup package (HRP). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
323206 SMS: List of Bugs Fixed in the Systems Management Server 2.0 Service Pack 4 Hotfix Rollup Package
WORKAROUND
To work around this issue, use any of the following methods:
- Quit the Winoldap process:
- On the client, press CTRL+ALT+DELETE to open the Close Program dialog box.
- Click Winoldap, and then click End Task.
- Reboot the client computer. The Remote Control agent should be installed properly after the client restarts.
- You can work around this problem by disabling the Remote Tools Client agent on the entire site.
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.
MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
When the client hangs, Remctrl.exe is attempting to determine the computer type. This detection is necessary so that Remctrl.exe can determine if the Nec-PC98 components need to be installed. The Pcdetect code first attempts to read a SetupMachineType registry value (from HKEY_LOCAL_MACHINE\ENUM\ROOT\*PNP0C01\0000) to determine the computer type. If this process does not succeed, Remctrl.exe loads a real-mode program (Pcddos.exe) to perform the computer-type detection.
To force LSM to perform a polling cycle when the LSM thread or Systems Management Server Executive service is stopped and restarted, set the following registry value to 0 (zero):
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Components\SMS_NT_LOGON_SERVER_MANAGER\Last Update Cycle
Additional query words: prodsms dell ibm
Keywords: kbqfe kbhotfixserver kbsms200presp5fix kbhardware _ik964 kbbug kbclient kbfix kbhelpdesk kbinterop kbremoteprog kbsms120bug kbsms200bug KB266232
