We have two active clustered sql servers and two separate IIS Load
balanced servers. We can connect to both instances of sql server
Enterprise manager and query analyzer (also tried an odbc connection)
thru local pc's.
I can get both IIS servers to connect to the default sql server
instance using sql ole db connections but I cannot get a connection to
work from IIS to the named instance of sql server. The error I
receive is as follows:
-2147467259
[DBMSSOCN]General network error. Check your network documentation.
I also tried to create an ODBC connection from one of the iis servers
to the named instance of sql server and it fails with a Connection
Failed general network error. Yet O can use my local pc and create an
odbc connection to the named instance of sql server with out an issue
(locally I have an option to let it dynamically determin the port in
the client config - I do not have this option on the IIS servers).
We found we had to add the Network Library=DBMSSOCN; string in our
connection to allow IIS to connect to the default instance of sql
server.
When we installed active clustered sql on the second server (the named
instance) we verified that the SQL Network Utility was set to allow
TCP/IP network connection a port was automatically set which was not
1433 and is different then the port on the defult instance of sql
server on the other active sql server box. Do we need to make sure
there is a network setting for this port somewhere?
Does anyone know how to correct this connection issue?

Hi

You have 2 options on the IIS Servers. Either use cliconfg.exe and create an
alias to configure the ports, or specify the port number in your connection
string by adding ",<pourtnumber>" to the instance name. e.g.
"virtualinstance1, 2500".

Regards
Mike

"tplumley" wrote:

Hi,

Cliconfg works for me but I didnt remove the NamedPipes as descibed in
http://support.microsoft.com/default...b;en-us;815431
If I removed the named pipes Im not able to failover the nodes anymore.
The next issue after you have the Named Pipes configured like
Server1\DB1 NamedPipes you can not add Server1\DB1 TCP/IP as it is saying
you have already configured this. It is not like that in Windows 2000.
But If you browse for servers in Query Analyser it is showing 2 times
Server1\DB1.
Another thing upgrade on the client side MDAC as you have on the SQL
server, otherwise you may have different issues. ADO2.5SP3 always looks first
for Named Pipes configured from ODBC even if you select TCP/IP in Client
Settings.

Regards,
C.Dimitrov

"Mike Epprecht (SQL MVP)" wrote: