Cannot configure SQL Server Express 2005 for remote connections

[matman13]

Hello. I have SQLEXPRESS 2005 installed on my laptop running Windows XP Home Edition with SP2. I have an application that can connect to the local instance with no problem. The other day, I tried to configure SQLEXPRESS 2005 for a remote connection from my desktop. To date, I have been unable to figure out how to do this.

I have followed the instructions posted at various locations on the internet, but to no avail. While I can configure SQLEXPRESS 2005 to allow TCP/IP connections, I have been unable to restart the server.

Here is the pertinent snippet from the error log:

<time> Server A self-generated certificate was successfully loaded for encryption.
<time> Server Error: 26024, Severity: 16, State: 1.
2006-08-14 21:02:27.18 Server Server failed to listen on 'any' <ipv4> 0. Error: 0x277a. To proceed, notify your system administrator.
<time> Server Error: 17182, Severity: 16, State: 1.
<time> Server TDSSNIClient initialization failed with error 0x277a, status code 0xa.
<time> Server Error: 17182, Severity: 16, State: 1.
<time> Server TDSSNIClient initialization failed with error 0x277a, status code 0x1.
<time> Server Error: 17826, Severity: 18, State: 3.
<time> 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.
<time> Server Error: 17120, Severity: 16, State: 1.
<time> 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.

I have a feeling this problem is due to the way my system is configured, not necessarily how my SQLEXPRESS 2005 is configured. My laptop and desktop are connected via a wireless router, and both machines are running Norton Anti-Virus 2006. I've added sqlserver.exe and sqlbrowser.exe to the exceptions list for the Worm protection on the laptop, i.e., the server machine. There's not a setting at the router that would prevent the server from re-starting, is there?

Any help is GREATLY appreciated!

Matt

 

[NoCoolHandle]

Ok.. I don't know if I can fix your issues, but on my laptop I am runnig SQLExpress and have it configured and working accross the network... so...

What instructions did you follow?

All I did was use the Surface Area Configuration Tool
Then Allowed "Remote Connections" both TCP/IP and Named Pipes..

Also...
Re XP.. Are you using the Firewall? If so did you open the SQL port (1433 by default)

Regarding the failure to start, can you undo what you did and will it run? (assuming reg hacking or something like that)


Rob

 

[matman13]

I have followed the steps from several sites, including:

http://support.microsoft.com/?kbid=914277&SD=tech

http://www.datamasker.com/SSE2005_NetworkCfg.htm

At this point, all I want to do is enable remote connections using TCP/IP (no pipes). When I do that, though, the server fails to start, producing the error log I listed in the opening post. If I then disable the TCP/IP and go back to just the local connections, the server starts fine.

Is there a setup problem with my laptop? Something in the Network Connections? Do I need to use port forwarding or some such feature on my wireless router? I would assume that the server does not depend on the router in order to start, so I'm assuming it is a setting on my local machine. I'm just stumped as to what that is.

 

[NoCoolHandle]

Ok.. both sets of instructions look good.
The router shouldn't be any type of issue..

The error tends to indicate that the server can't listen on the port assigned.

That would tend to point it at your XP install.
I was also wondering if the XP fire wall could have some impact, but I have mine turned on, and it works. I have also tried shutting down ports and that didn't make any difference.

You might want to try turning of the XP firewall just to see if that is the issue (I can't imagine that you don't have tcp/ip installed - but that might be an issue.)

In the Configuration Manager is Shared Memory Enabled?
This was the only option that caused my server to Choke when disabled.. However the errors weren't quite the same.

Good Luck.

Rob

PS have you posted to the MS bbs? (not that it is usually as usefull as posting here, but.....)

 

[matman13]

Yes, shared memory is enabled, and yes, I've posted to the MS bbs.

OK. I opened SSCM and changed the TCP Port field in IPALL to be 2433 (I also cleared the TCP Dynamic Ports field). I then rebooted the machine. When I logged back in, I disabled Norton A/V. I then tried to start the service. It failed to start, and I got this in the error log.

<time> Server Error: 26024, Severity: 16, State: 1.
<time> Server Server failed to listen on 'any' <ipv4> 2433. Error: 0x277a. To proceed, notify your system administrator.
<time> Server Error: 17182, Severity: 16, State: 1.
<time> Server TDSSNIClient initialization failed with error 0x277a, status code 0xa.
<time> Server Error: 17182, Severity: 16, State: 1.
<time> Server TDSSNIClient initialization failed with error 0x277a, status code 0x1.
<time> Server Error: 17826, Severity: 18, State: 3.
<time> 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.
<time> Server Error: 17120, Severity: 16, State: 1.
<time> 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.

So, the server at least recognized the port I chose. I tried using port 45013, and the error log showed " 'any' <ipv4> 45013". As soon as I disable the TCP/IP protocol in SSCM, I can restart the server successfully, with or without Norton A/V running.

In my naive mind, this would seem to indicate some configuation problem on my machine itself. I can connect to the internet with no problem, so I don't think it's the TCP/IP protocol on the machine. Any other ideas? Any other things to try?

 

[NoCoolHandle]

Just a couple.

1 try uninstalling and reinstalling SQLE
2 uninstalling and reinstalling the network card.

not a very good solution (and it might still fail), but I have seen both things get slightly bent and reinstalling has worked.