[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1640
  • Last Modified:

Unable to start service after enabling TCP/IP

I've recently installed an instance of SQL Sever 2005 Express. Now I've googled and found that it doesn't support external connections by default - you need to enable TCP/IP then restart the service.

Once I enable TCP/IP (SQL Server Config Manager -> Protocols for SQLExpress) then try restart the service (SQL Server 2005 Services) it stops, but wont start again (times out).

Any ideas on what is going on???

Dave
0
flavo
Asked:
flavo
  • 2
  • 2
1 Solution
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
can you get the ERRORLOG file of the sql server instance, it should contain more information about what goes wrong.
0
 
flavoAuthor Commented:
Here's what that shows, I have no idea..

2007-11-25 01:28:23.10 Server      (c) 2005 Microsoft Corporation.
2007-11-25 01:28:23.10 Server      All rights reserved.
2007-11-25 01:28:23.10 Server      Server process ID is 5296.
2007-11-25 01:28:23.10 Server      Authentication mode is MIXED.
2007-11-25 01:28:23.10 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-11-25 01:28:23.10 Server      This instance of SQL Server last reported using a process ID of 572 at 11/25/2007 1:28:15 AM (local) 11/24/2007 3:28:15 PM (UTC). This is an informational message only; no user action is required.
2007-11-25 01:28:23.10 Server      Registry startup parameters:
2007-11-25 01:28:23.10 Server             -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-11-25 01:28:23.10 Server             -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-11-25 01:28:23.10 Server             -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-11-25 01:28:23.14 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-11-25 01:28:23.14 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2007-11-25 01:28:23.87 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2007-11-25 01:28:23.89 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2007-11-25 01:28:23.90 Server      Database mirroring has been enabled on this instance of SQL Server.
2007-11-25 01:28:23.90 spid5s      Starting up database 'master'.
2007-11-25 01:28:24.01 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2007-11-25 01:28:24.17 spid5s      SQL Trace ID 1 was started by login "sa".
2007-11-25 01:28:24.20 spid5s      Starting up database 'mssqlsystemresource'.
2007-11-25 01:28:24.21 spid5s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2007-11-25 01:28:24.56 spid5s      Server name is 'DAVE\EXPRESS2005'. This is an informational message only. No user action is required.
2007-11-25 01:28:24.56 Server      Error: 17182, Severity: 16, State: 1.
2007-11-25 01:28:24.56 Server      TDSSNIClient initialization failed with error 0xd, status code 0x10.
2007-11-25 01:28:24.56 spid8s      Starting up database 'model'.
2007-11-25 01:28:24.56 Server      Error: 17182, Severity: 16, State: 1.
2007-11-25 01:28:24.56 Server      TDSSNIClient initialization failed with error 0xd, status code 0x1.
2007-11-25 01:28:24.56 spid5s      Starting up database 'msdb'.
2007-11-25 01:28:24.56 Server      Error: 17826, Severity: 18, State: 3.
2007-11-25 01:28:24.56 Server      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.
2007-11-25 01:28:24.57 Server      Error: 17120, Severity: 16, State: 1.
2007-11-25 01:28:24.57 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.


Now as soon as I turn off TCP/IP


2007-11-25 01:30:11.01 Server      (c) 2005 Microsoft Corporation.
2007-11-25 01:30:11.01 Server      All rights reserved.
2007-11-25 01:30:11.01 Server      Server process ID is 5664.
2007-11-25 01:30:11.03 Server      Authentication mode is MIXED.
2007-11-25 01:30:11.03 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-11-25 01:30:11.03 Server      This instance of SQL Server last reported using a process ID of 5716 at 11/25/2007 1:29:26 AM (local) 11/24/2007 3:29:26 PM (UTC). This is an informational message only; no user action is required.
2007-11-25 01:30:11.03 Server      Registry startup parameters:
2007-11-25 01:30:11.03 Server             -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-11-25 01:30:11.03 Server             -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-11-25 01:30:11.03 Server             -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-11-25 01:30:11.03 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-11-25 01:30:11.03 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2007-11-25 01:30:11.78 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2007-11-25 01:30:11.79 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2007-11-25 01:30:11.79 Server      Database mirroring has been enabled on this instance of SQL Server.
2007-11-25 01:30:11.79 spid5s      Starting up database 'master'.
2007-11-25 01:30:12.06 spid5s      SQL Trace ID 1 was started by login "sa".
2007-11-25 01:30:12.09 spid5s      Starting up database 'mssqlsystemresource'.
2007-11-25 01:30:12.12 spid5s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2007-11-25 01:30:12.48 spid5s      Server name is 'DAVE\EXPRESS2005'. This is an informational message only. No user action is required.
2007-11-25 01:30:12.48 spid8s      Starting up database 'model'.
2007-11-25 01:30:12.48 spid5s      Starting up database 'msdb'.
2007-11-25 01:30:12.79 Server      A self-generated certificate was successfully loaded for encryption.
2007-11-25 01:30:12.79 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\EXPRESS2005 ].
2007-11-25 01:30:12.79 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$EXPRESS2005\sql\query ].
2007-11-25 01:30:12.79 Server      Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2007-11-25 01:30:12.82 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2007-11-25 01:30:13.06 spid8s      Clearing tempdb database.
2007-11-25 01:30:13.70 spid8s      Starting up database 'tempdb'.
2007-11-25 01:30:13.85 spid5s      Recovery is complete. This is an informational message only. No user action is required.
2007-11-25 01:30:13.85 spid11s     The Service Broker protocol transport is disabled or not configured.
2007-11-25 01:30:13.85 spid11s     The Database Mirroring protocol transport is disabled or not configured.
2007-11-25 01:30:13.87 spid11s     Service Broker manager has started.
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
the message to check out from that log is:
TDSSNIClient initialization failed with error 0xd, status code 0x10.

see here:
http://blogs.msdn.com/sql_protocols/archive/2005/10/14/480848.aspx
0
 
flavoAuthor Commented:
It wasn't a space, but I changed the IpAll TCP Dynamic Ports value to 1066 and it finally seems to work.

thx
Dave
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now