<div>
<div class="content wysiwyg-content">
My SQL Server 2005 instance fails to start with the following error message:<br />
<br />
Event Type: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Error<br />
Event Source: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MSSQLSERVER<br />
Event Category: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(2)<br />
Event ID: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;26024<br />
Server failed to listen on 10.2.1.1 &lt;ipv4&gt; 1433. Error: 0x2741. To proceed, notify your system administrator.<br />
<br />
IP address 10.2.1.1 is one of four IP addresses on the server:<br />
<br />
IP1: Public IP (Disabled)<br />
IP2: Public IP (Disabled)<br />
IP3: 10.2.1.1 (Enabled)<br />
IP4: 127.0.0.1 (Enabled)<br />
<br />
IP3 (10.2.1.1) is not present when the server boots as this is the IP address of the server when it is hosting VPN sessions. It seems that SQL Server is trying to listen on this IP address when it starts but cannot find it - as I would expect; however, I do not expect it to abort its startup as a result.<br />
<br />
If I enable IP1 as well then the server starts fine, even though IP3 is still not available.<br />
<br />
I am looking for a way to allow SQL Server to startup when IP3 is unavailable without compromising the security of the box.
</div>
</div>


My SQL Server 2005 instance fails to start with the following error message:

Event Type:	Error
Event Source:	MSSQLSERVER
Event Category:	(2)
Event ID:	26024
Server failed to listen on 10.2.1.1 <ipv4> 1433. Error: 0x2741. To proceed, notify your system administrator.

IP address 10.2.1.1 is one of four IP addresses on the server:

IP1: Public IP (Disabled)
IP2: Public IP (Disabled)
IP3: 10.2.1.1 (Enabled)
IP4: 127.0.0.1 (Enabled)

IP3 (10.2.1.1) is not present when the server boots as this is the IP address of the server when it is hosting VPN sessions. It seems that SQL Server is trying to listen on this IP address when it starts but cannot find it - as I would expect; however, I do not expect it to abort its startup as a result.

If I enable IP1 as well then the server starts fine, even though IP3 is still not available.

I am looking for a way to allow SQL Server to startup when IP3 is unavailable without compromising the security of the box.

SQL Server Fails to Start

Microsoft SQL Server 2005 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. It includes support for managing XML data and allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets encapsulated within SOAP (protocol) requests.