asked on

ODBC SQL Server Driver Named Pipes

My client added some Microsoft Windows patches over the weekend and now their application is not working. Their SQL Server Database is set up on a cluster.

This is the error that my client came up with:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC SQL Server Driver][Named Pipes]Specified SQL server not
found.

This is what I have in the global.asa for the connection string:
Session("strUConnect") = "Driver={SQL Server};Server=(local);uid=xxxxxxx;pwd=xxxxxxx;database=xxxxxxx"

What could have cause their application to stop working just because they added some Microsoft Windows patch.

URGENT - Thank you!

ASKER CERTIFIED SOLUTION

curtis591

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Guy Hengel [angelIII / a3]

Check out the Server and Client Network tools from SQL Server, there you can see which network protocols are enabled. Normally, you choose the TCP/IP as default protocol (at the server and at the client), and it should work fine. I guess that the patch has reset the default to named pipes (silly NT)...

CHeers

oshe127

ASKER

We are having them check the utility now for TCP/IP and they are adding the exact name of the cluster in the server instead of it being local.

TheSpirit

You don't give away the versions of SQL/OS that are being used but you might want to checkout the Q article that documents rebind.exe Q239473 after OS updates.

oshe127

ASKER

Thanks!

The IP was half of the problem the other half was the global.asa, didn't have the cluster name it still said local.