November 11, 2013 at 12:42 pm
Windows 2008R2 server had 2 instances of SQL 2005 installed, BACKUPEXEC and ACRONIS.
I installed SQL 2008R2 Express (64 bit), created database, and our software runs fine on the server.
When I try to run our software from a workstation, this error appears:
Connection failed:
SQLState: '08001'
SQL Server Error: -1
[Microsoft][SQL Native Client]SQL Interfaces: Server doesn't support requested protocol [xFFFFFFFF].
Connection Failed:
SQLState: 'HYT00'
SQL Server Error: 0
[Microsoft][SQL Native Client]Login timout expired
SQLState: '08001'
SQL Server Error: -1
[Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default setting SQL Server does not allow remote connections.
I have tried establishing a connection using ODBCAD32, and I can select the correct instance using this tool, but I still get exactly the same error message.
Since I am not responsible for the software running on SQL 2005, I am trying to be cautious in making any configuration changes.
The SQL 2005 install is 32 bit, while the SQL 2008R2 install is 64 bit (I can reinstall 32 bit version if this is an issue).
SQL Server Browser is running, but it is the 2005, 32 bit version that is running.
Any help would be appreciated.
Isaac Davidian
Datatech
November 12, 2013 at 3:55 am
http://blogs.msdn.com/b/sqlexpress/archive/2005/05/05/415084.aspx
I'm pretty sure this is still applicable to 2008R2 Express.
November 22, 2013 at 2:01 pm
Problem solved, but I don't know why, or if my explanation is correct.
Reviewed article referred to by MysteryJimbo, thank you. All 3 instances had TCP/IP enabled, but one 2005 instance did not have Named Pipes enabled. Turned it on, and the "Server doesn't support requested protocol" error no longer appeared. Instead, new error, "couldn't find named instance". So it appeared to be a browser problem.
From a client computer I tried logging in to one of the 2005 instances. The instance was found by the browser, but I was denied login since I did not have an account for it.
After that, I knew the browser was working, so I tried logging in to the 2008R2 instance. It worked, no errors!
It's as if, by having the browser find a 2005 instance, it also figured out there was a 2008R2 instance. Through all of the previous errors, I had verified that the browser service was running. No other changes were made.
Problem solved, but not the mystery.
Isaac Davidian
Datatech
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply