Solved

Issue with Connecting a 2003 R2 server to a 2008 R2 MSSQL Express instance

Posted on 2011-09-15
9
463 Views
Last Modified: 2012-06-27
Trying to link a 2003 website with a 2008 R2 SQL database.

I setup the Client Tools for the 2003 server so it could (theoretically) establish a connection with a 2008R2 SQL instance.  This is a 2008R2 Express install.

The latest error I've been getting is:

Microsoft SQL Server Native Client Version 10.50.1600

Running connectivity tests...

Attempting connection
[Microsoft][SQL Server Native Client 10.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
[Microsoft][SQL Server Native Client 10.0]Login timeout expired
[Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.

TESTS FAILED!


The firewall is off.  The named pipes TCP/IP and other connectors are all turned on.  I can't connect to this server instance (to browse and see databases from any ODBE or connection string through a .UDL file) from any machine.

Anyone have any ideas?  Is it possible to get these two different machines or server types to talk to each other?
0
Comment
Question by:ChocolateRain
  • 4
  • 4
9 Comments
 
LVL 59

Expert Comment

by:Kevin Cross
ID: 36546762
Hi.

Since this is SQLExpress, you should connect to it as SERVERNAME\SQLEXPRESS unless you explicitly installed as another named instance or the default instance. Check that first.
0
 
LVL 5

Expert Comment

by:VENKAT KOKULLA
ID: 36547493
please check out the below points:

1) First check it's a named instance or default--if it's default instance try to connect as 'local', if it's a named instance try to connect as 'SERVERNMAE\INSTANCENAME'.

2) please make sure SQLBrowser service is running

3)  Please check the errorlog for the sql express instance and make sure
TCPIP and Named pipes are enabled. You shall also see the port for

C:\Program Files\Microsoft SQL Server\MSSQL.x\MSSQL\LOG

4) Try different protocols by using SQLCMD to test

sqlcmd -S np:\\127.0.0.1\pipe\MSSQL$instancename\sql\query
sqlcmd -S tcp:servername\instancename
sqlcmd -S tcp:servername\instancename,portnumber

Note: You may need to change the servername, instancename, portnumber
properly according to your server configurations.

Go through this link mite helpout:
http://blogs.msdn.com/b/sql_protocols/archive/2005/10/22/sql-server-2005-connectivity-issue-troubleshoot-part-i.aspx

If you have any update, please feel free to let us know.
0
 
LVL 1

Author Comment

by:ChocolateRain
ID: 36550304
Ok, the server instance name is AGCV0080\SQLEXPRESS.

The SQLBrowser service wasn't running but it is now.
I don't see the named pipes in the log file.

Although the "sqlcmd -S np:\\127.0.0.1\pipe\MSSQL$instancename\sql\query" command shows me a new prompt, which I assume it is a query prompt in the server.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 59

Expert Comment

by:Kevin Cross
ID: 36550862
Is AGCV0080\SQLEXPRESS what you are using in the tests where you got failures earlier? If not, then try with that and post back.
0
 
LVL 1

Author Comment

by:ChocolateRain
ID: 36568146
What it turned out to be is a certain ESXi host.  For some reason that I've yet to get to the bottom of, when this VM was running on this ESXi host it wouldn't allow connections between the SQL server and any VM or PC trying to connect to it.  

Strange.  Anyone seen that before?  Anyone want to guess the cause of it?

Didn't think a problem like this would be solved via vMotion, but there it is.
0
 
LVL 59

Expert Comment

by:Kevin Cross
ID: 36568283
I have seen issues where a blue screened or failed VM flooded network interface and so caused problems. Other than failures and silly things like when using templates you may end up with the same SID on all guests, that sounds strange. Glad you found it though.

What was running on that VM? Maybe it was a conflict similar to a failed VM. For example, if that VM was running software that is network intensive it could have the same effect. Check configuration on the NIC, ensure it is not acting as a router/firewall; otherwise, you may have trouble where you VMotioned it to.
0
 
LVL 1

Accepted Solution

by:
ChocolateRain earned 0 total points
ID: 36590295
One of the ports that the ESXi server was connected to for its default VLAN connection was set as an "Auto" port on the HP Procurve switch side.  This was causing other weird problems.  It should've been in the Default VLAN untagged and tagged for the DAG and VOIP network.

0
 
LVL 59

Expert Comment

by:Kevin Cross
ID: 36590401
Good find. That way you won't end up with the issue again in the future.
Best regards, Kevin
0
 
LVL 1

Author Closing Comment

by:ChocolateRain
ID: 36941307
Found my own solution again.
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question