June 2, 2011 at 7:31 am
Yesterday I installed a Named Instance of SQL Server 2008 on our development server. This server already has an instance of 2005 running on it. I kept getting error 26 when I would try to connect with SS Management Studio despite trying everytyhing under the sun. I made sure that "Allow Remote Connections" was checked, I made sure SQL Browser Service was running, I ran "sqlcmd -L" and the server is definitely in the list, I downloaded the new PortQryV2 utility and everything checked out with that. I Googled and read till the wee hours and finally came across a fix where someone suggested that I suffix the connection string with ", 1433". Which, WORKED! The Connection Window closed, and a connection appeared in my SQL Server Management Studio. HOWEVER...
When I expanded the tree under this server, which is showing up with the "Named Instance" name in SSMS, I noticed that the databases present were not those of the new 2008 instance, but rather the databases and tables, etc. of the 2005 <root> instance!
Can somebody please explain to me what is going on with this strange behavior? And I still can't successfully connect to my 2008 instance. What configuration changes need to take place to be able to connect to the 2008 Named Instance? HELP!
TIA,
KK
June 2, 2011 at 7:41 am
Additional Info: In SSMS on the remote machine that is connected it is displaying "SERVERNAME\SQLNAMEDINSTANCENAME,1433 (SQL Server 9.0.3042 - username)"
On the machine with both instances, the named instance connection is displaying "SERVERNAME\SQLNAMEDINSTANCENAME (SQL Server 10.50.1600 - username)"
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply