Apply MDAC 2.8 to all your client machines. Early versions of MDAC were not
instance aware. Cluster names (VitrualServerName\InstanceName) use the same
syntax as multi-instance SQL servers and look the same on an network.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org [quoted text, click to view] "Fonkberry" <Fonkberry@discussions.microsoft.com> wrote in message
news:296ABC73-4A0B-44BC-8221-F5498C903DDD@microsoft.com...
> We're having a problem with our web applications connecting to the SQL DB
> virtual server cluster. We are running SQL 2000 an '03 Server Cluster. The
> front-end web servers are Win2K, IIS 5. The web servers and the database
> server reside on the same LAN and the front end can ping the backend using
> either IP or SQL cluster name successfully.
>
> The clustering is functioning properly and has passed all failover testing
> scenarios including the SQL Server resources. The ASP code is using a
> Globaldb include file to point to a production database. When I point any
of
> 3 web servers to a single SQL server offering the same exact databases,
> users, logins, etc., IE makes the connections with no problem. When
> attempting to do the same to the clustered virtual server, we get either a
> "500 Internal Server" error or a blank page that says "Done" on the IE
status
> bar at the bottom of the window. No connection to the database is
completed
>
> Is there something we are missing to make this connection work? What can I
> look at?
>
> Thank you very much.
>