Article ID: 174787
Article Last Modified on 10/30/2006
APPLIES TO
- Microsoft Proxy Server 1.0 Standard Edition
- Microsoft Proxy Server 2.0 Standard Edition
This article was previously published under Q174787
SYMPTOMS
If you select (enable) logging and set up to go to a SQL Server database for the Web Proxy Service, sometimes upon rebooting, the service set up to use the SQL Server database will fail to log anymore.
CAUSE
This happens because the Web Proxy service relies on the SQL Server service to be started before that service can begin logging. If the Proxy service starts before the SQL Server service, it will not be able to log and the service will turn logging off.
NOTE: This is also true of the WWW service.
RESOLUTION
WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.
For these services to use SQL Server as a logging source, you will need to follow the steps below to make the Web proxy service or WWW service to wait for the SQL service to start:
Start Registry Editor (Regedt32.exe), and locate the following Registry subkey in the HKEY_LOCAL_MACHINE subtree:
\SYSTEM \CurrentControlSet \Services \W3SVC- Double-click the DependOnService.
- Add MSSQLServer (exactly as written) to the list of services.
- Click OK, and then quit Registry Editor.
- Shut down and restart Windows NT.
Keywords: kbprb KB174787
