Microsoft KB Archive/180255

From BetaArchive Wiki
Knowledge Base


Article ID: 180255

Article Last Modified on 8/11/1999



APPLIES TO

  • Microsoft Proxy Server 2.0 Standard Edition



This article was previously published under Q180255

SYMPTOMS

When you install Proxy Server 2.0 with the documentation and later remove the documentation through Setup, or if you install Proxy Server 2.0 without documentation and later add the documentation through Setup, the proxy services will fail to start.

After you restart the server system, the following two messages appear on the logon screen:

  • mspadmin.exe - DLL Initialization Failed Initialization of the dynamic link library C:\WINNT\system32\MSPHLPR.dll failed. The process is termination abnormally.
  • wspsrv.exe - DLL Initialization Failed Initialization of the dynamic link library C:\WINNT\system32\MSPHLPR.dll failed. The process is termination abnormally.

Service Control Manager adds the following two event log error entries:

   The Microsoft Proxy Server Administration service failed to start due to
   the following error: The service did not respond to the start or control
   request in a timely fashion.

   Timeout (120000 milliseconds) waiting for service to connect.
                

CAUSE

The Proxy Server Setup program deletes the Mspclnt.ini file in the Proxy Servers Client folder when the Proxy Server documentation is either installed or removed. This missing Mspclnt.ini file causes the proxy services to fail starting.

RESOLUTION

To work around the problem, use of the following procedures:

Method One

Uninstall and reinstall Proxy Server either with or without the documentation.

Method Two

  1. Back up the file Mspclnt.ini from the Proxy Servers Client folder.
  2. Run Setup to add or remove the documentation.
  3. Restore Mspclnt.ini when Setup has finished.


STATUS

Microsoft has confirmed this to be a problem in Proxy Server version 2.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords: kbbug kbnofix KB180255