December 23, 2011 at 9:19 am
Hi,
Our app has 6 servers, a common, 4 identical servers where the data has been farmed out and a historical server.
We've never really had a development environment, so they gave us a Sql Server and we installed 6 additional instances of Sql Server so production is replicated.
We don't want to connect via the instance name (no code change between Prod and Dev), so we configured each instance on it's own ip and I can connect to each instance via ip no problem.
The problem is that each instance of Sql Server Agent needs named pipes to connect to the instance and I have that turned off so we can use host file overrides to get to each instance via ip. No Sql Agent is problem.
Only tcpip protocol is enabled for each instance.
Listen All is turned off
Under TCPIP protocal, IP Addresses, IP1 is active and enabled, I gave each an address. We've tried with dynamic ports and all on 1433.
Can't get Sql Agent to work without named pipes it appears.
Any suggestions?
Thanks,
Steve
December 25, 2011 at 11:52 pm
See if below link helps you
http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/ see the reply written by "vince" on May 22, 2009 at 7:48 pm
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
December 26, 2011 at 9:33 am
Thanks, it took a while but we got it. In Sql Server Agent, there is a spot for local server alias and we substituted the ip.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply