August 26, 2008 at 7:18 am
I've added a 3rd named instance to a server. When I try to make a DSN entry to it, I can see the other two existing named instances, but the new one doesn't appear in the list and I get an a Connection Failed, SQL Server does not exist or access denied error if I try to manually type in the Instance name. anybody have any thoughts off hand of what might be causing me this issue? I can get at the instance fine locally through Enterprise Manager. Under Server Properties the Remote Server Connections check box is checked. Any help would be appreicated.
August 26, 2008 at 7:50 am
Ok I changed the Client from TCP/IP to Named Pipes and it resolved the issue. Anybody better at SQL than I am tell me why that would resolve it? Thanks!
August 26, 2008 at 8:13 am
what were you using for the connection string? IP?
August 26, 2008 at 8:17 am
Steve Jones - Editor (8/26/2008)
what were you using for the connection string? IP?
I wasn't using a connect string (per say, I'm sure there is one in the background somewhere), I was using Windows ODBC Data Source Administrator.
August 26, 2008 at 11:53 am
Is the third sql 2005 instance configured with TCP/IP protocol enabled? Please check the protocols enabled for third instance under SQL Server configuration Manager.
MJ
August 26, 2008 at 11:55 am
It has Named Pipes and TCP/IP Protocols enabled.
August 28, 2008 at 11:09 am
Are you specifying TCP/IP port with server name or IP? Is browser service running?
MJ
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply