Unable to connect to configuration database due to SQL server port bind failure

Article ID: KB24746

Type: Support Content

Last Modified: 08-28-2014

Submitted By: Jeremy Welch

 

Product(s) Affected:

  • BlackBerry Enterprise Server for Microsoft Exchange
  • BlackBerry Enterprise Server for IBM Lotus Domino
  • BlackBerry Enterprise Server for Novell GroupWise
CollapseEnvironment
  • BlackBerry Enterprise Server
  • Microsoft SQL Server 2000 or MSDE
CollapseOverview

The BlackBerry Dispatcher service fails to start, and error 5608 appears in the System Logs in Event Viewer.

The following log lines may appear in the BlackBerry Dispatcher log:

[30058] (10/24 08:06:59.000):{0xB08} Starting Database
[30000] (10/24 08:06:59.015):{0xE28} [DIAG] EVENT=Register_thread, THREADID=0xE28, THREADNAME="CBESRpcServer"
[30000] (10/24 08:06:59.078):{0xB08} ADO ConnectionTimeout value = 30s
[20642] (10/24 08:07:29.648):{0xB08} Database error in OpenDB (err=0x80004005, native err=17) - [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
[20650] (10/24 08:07:29.648):{0xB08} OpenDB: COM Error (80004005): Unspecified error
[20652] (10/24 08:07:29.648):{0xB08} OpenDB: OPEN_DB failed

In the Application Log of the Microsoft SQL Server, the following error will appear when SQL attempts to start:

Type : Error
Date : 10/24/2010
Time : 7:16:56 AM
Event : 17055
Source : MSSQLSERVER
Category : (2)
User : N/A
Computer : SERVER01
Description:

The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) could not be found. It contains the following insertion string(s): .
19012

SuperSocket Info: Bind failed on TCP port 1433.

CollapseCause
This error is caused by SQL failing to bind to a predefined static port.
CollapseResolution

Identify the application using the port defined in the SQL configuration and configure it to ignore the port used by SQL.

To identify the application utilizing the port, follow these steps:

  1. Open the command prompt by clicking Start, then Run, and typing CMD
  2. Type in netstat -ban >c:\netstat.txt

    Note: in Windows Server 2008, administrator privileges are required to write to the root directory. Either run the command prompt with administrator, or specify a location that is not in the root, such as c:\temp\, for the output file.

  3. Open the output file
  4. Search for the SQL port in the Local Address column
CollapseAdditional Information

For more information on the Error 5608 written in the System Log, see KB04185

For more information on the Bind failed on TCP port error, see KB307197, or visit Microsoft Help and Support site and search for "SQL Server cannot bind to the TCP/IP port on which SQL Server is listening when the TCP\IP port is used by another application"

CollapseInternal Notes - RIM CONFIDENTIAL

Note: This section is for internal use only. Do not copy or distribute to end users, customers or other third parties.

It is possible that manually reserving the port specified by SQL will keep another application from reserving the port prior to SQL starting.

For instructions on reserving the ports that are required by BlackBerry Enterprise Server services, see KB812873, or visit the Microsoft Help and Support site  site and search for "How to reserve a range of ephemeral ports on a computer that is running Windows Server 2003 or Windows 2000 Server."

This is not specifically recommended by Microsoft to fix the above issue, but is designed to fix a range of issues with this cause.