My user wrote asp apps previous ran fine against SQL 2k sp3a on win2k. Now
we upgrade our SQL server to Windows 2003 Failover Clustering SQL 2k sp3a.
Then even she changed her connection string to new sql server, but her asp
program is no longer make connection to SQL Server.

I granted all the security. But looks she can't even make a connection.
Did she need upgrade her OLEDB, MDAC or some other system setting in order to
run against SQL server on Windows 2003 Failover cluster. All my other apps
are working fine.

Thanks.
Maggie

Make sure MDAC is 2.6 or higher on all clients. Earlier versions may not
understand named instances correctly. Cluster instances appear as named
instances.

Geoff N. Hiten
Microsoft SQL Server MVP


"Maggie" <Maggie (AT) discussions (DOT) microsoft.com> wrote

Her MDAC is 2.7 and sql ole db 08.10.9024. We have a default instance on the
Cluster. What could be problem right now?

"Geoff N. Hiten" wrote:

I would do all the normal network troubleshooting steps. Name Resolution,
Ping( by IP and then by name), SQL client tool (Query Analyzer) connection.
Somewhere along the way, it is not able to find or connect. Testing
everything in sequence will find the culprit. Don't let the fact that the
SQL server is on a cluster spook you. Once it is up and running, it looks
and acts just like any other SQL server to the outside world.

Geoff N. Hiten
Microsoft SQL Server MVP.

"Maggie" <Maggie (AT) discussions (DOT) microsoft.com> wrote

"Maggie" wrote

Are you connecting to one of the physical adresses or the virtual address??
Each node has it's own name and ip and the network the cluster has it's own
name and ip
Like eg
10.8.1.20 for the virtual cluster ip and
10.8.1.21 for the first node etc

HTH