INF: Listening on Multi-Protocol Fails on Startup
ID: Q160871
|
The information in this article applies to:
-
Microsoft SQL Server version 6.5
SUMMARY
When a computer running SQL Server is configured to listen only on the
multi-protocol network protocol, the MSSQLServer service may fail on the
startup of Windows NT Server. This problem may occur when Windows NT Server
is starting and the remote procedure call (RPC) service has not completed
initializing before SQL Server starts the server-side RPC Net-Library. You
will find the following errors in the SQL Server errorlog:
Using 'SSMSRP60.DLL' version '6.5.0.0' to listen on ''.
Error : 17826, Severity: 18, State: 0
Unable to set up ListenOn connection ''.
OS Error : 1899, The endpoint mapper database could not be created.
conn_hdlr: Unable to initialize Communication Layer
MORE INFORMATION
Configure the computer running SQL Server to listen on either another
network protocol or another protocol in addition to multi-protocol.
One other way to resolve this problem is to modify the Windows NT Server
registry to force the MSSQLServer service to depend on the RPC service,
requiring that the RPC service be initialized before MSSQLServer service
attempts to start.
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.
- Start the Registry Editor (Regedt32.exe) and navigate to the following key:
HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\MSSQLServer
- Click the MSSQLServer subkey. On the Edit menu, click Add Value.
- Enter the following:
Value Name: DependOnService
Data Type: REG_MULTI_SZ
Data: RpcSs
- Click OK and quit Registry Editor.
- Shut down and restart the computer running Windows NT Server.
Additional query words:
Multiprotocol
Keywords : kbenv kbinterop kbnetwork kbusage SSrvGen SSrvLAN
Version : 6.5
Platform : WINDOWS
Issue type :