Troubleshooting when the Server Fails to Start

If the server fails to start, check that the port number specified in the interfaces file is available.

00:00000:00002:2003/09/22 12:37:23.63 kernel  network name SERV_CORPNET, type ether, port 4559, filter NONE
00:00000:00002:2003/09/22 12:37:23.65 kernel  ninit: bind, Address already in use
00:00000:00002:2003/09/22 12:37:23.68 server  Error: 1602, Severity: 18, State: 2
00:00000:00002:2003/09/22 12:37:23.68 server  Unable to initialize network 0
00:00000:00002:2003/09/22 12:37:23.68 kernel  ninit: All master network
listeners have failed.  Shutting down.
00:00000:00002:2003/09/22 12:37:23.68 kernel  ueshutdown: exiting
00:00000:00016:2003/09/22 16:11:35.46 server  SQL Server shutdown by request.

1. Investigate the port assignment:
   1. Look in the interfaces file to identify the port number assigned to the server.
   2. Determine whether another process is using the same port number by entering:

      netstat -a

      If the port number is presented as a local address in the netstat output, you cannot use that port for the server. Another process is already using that port.

   3. To verify that the server port is in use, start the server manually. The server does not start if its assigned port number is already in use.

   See the installation documentation for your platform and the Utility Guide.

2. If a stale server process is retaining use of the port number, either:
   • Use the operating system kill command to terminate the process, or,
   • Use another port number for the server by modifying the interfaces file.
3. Start the server manually to confirm that the port number is available.

   See the installation documentation for your platform and the Utility Guide.