Sql Server 2005 fail to start up if there are spaces after tcp port


When you try to start sql server 2005, it may fail and in the errorlog, it shows:

Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0xd, status code 0x10

Error: 17826, Severity: 18, State: 3.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

And you checked protocol configuration, nothing looks unusual.


One possible reason is that there are spaces after the tcp port on the server side. You can go to SQL Server Configuration Manager, choose the server instance, right click TCP/IP and see the properties, check whether there trailing spaces in the TcpPort field.

Essentially, SQL Server 2005 does not allow trailing spaces in Server-side TcpPort field, this is a breaking change from SQL Server 2000. The error that you would see in the error log depend upon whether the instance set "ListenAll" to "Yes" or "No".

If "Yes":

   TDSSNIClient initialization failed with error 0xd, status code 0x10

If "No":

   TDSSNIClient initialization failed with error 0xd, status code 0x19


  Go to SQL Server Configuration Manager, edit the server-side TcpPort and remove the trailing blank.


KB article number 907853


Ming Lu, SQL Server Protocols


Comments (7)

  1. impu says:

    I am having the same problem with SQL Server Express 2005 and did notice the space.  But deleting the space did not resolve the problem.  I also notice the following prior to the Code 0x10

     TDSSNIClient initialization failed with error 0xd, status code 0x1

  2. Hi, impu

      1) By default Express 2005 has TCP disabled, whether you specified the port and were trying to restart the server?

      2) There is another blog that talking about server startup fail:http://blogs.msdn.com/sql_protocols/archive/2005/10/31/487090.aspx#comments

    If your case is none of them, could you go to SQL Server Configuration Manager and check how protocols were configured, which protocol was enabled? More importantly, could you attach any error info in the server log? There is another blog that help you troubleshoot from status or error code in the server error log.




  3. SQL Server 2005 could fail to bring up due to various causes, there are several great blogs that talk…

  4. lesbian rape says:

    Best of all people w can talk…

  5. Solange says:

    Thanks a million.  Your help saved me a whole lot of frustation.

  6. Charles says:

    Thanks a million! I had spent so many hours changing all sorts of options before I stumbled across your website.

    Now, my problem is solved! Thank you.

Skip to main content