I get microsoft odbc sql server driver tcp/ip sockets general network error
and microsoft odbc sql server driver communication link faillure errors when
I open our client app and while I did a cluster failover.
Any reasons.

I have been using Mirroring now for a while and put the system into
production now after applying SQL sp 1.
We have a setup with a witness, principal and mirror with certificates (the
witness is on a webserver in a different domain, so we can't use integrated

Is there a way to detect if the principal or mirror is running the database?
I want build my own altert system, sending an SMS whenever a automatic
failover/failback happens.
Per Schjetne

is it possible to install SQL Server 2005 Standard Edition on two nodes of a
4-node-cluster? MSFT states that Standard Ed. supports two-node-clusters but
does it also supports a two-node-cluster within a 4-node Windows cluster?
Thanks and best regards

Does anyone else have problems with their cluster machines being able to see
the domain. i have 2 clustering setups on 2 different subnets and none of the
4 machines can see the domain, list the domain server, or connect to any of
the domain machines besides the domain controller ...

Our second node in an active/active SQL cluster (Win 2K SP4/ SQL2K SP2)
failed as a result (it seems) of a bad NIC at the public interface.
Cluster and SQL logs seem to support that the failover went
successfully, except for SQL job agent suddenly stopping on the first

the BOL state that a domain user account with two additional privileges (act
as part of OS and connect as service) and membership in the local
administrator group in all nodes is sufficient for installing SQL Server
2005. Has anybody successfully installed the product under these ...

Are there any solution to implement load balancing on one database between
two nodes of cluster?
Thanks in advance,
Leila

I have a Windows 2003 cluster already built. Then I script SQL server 2000.
Installing a Local instance goes good.  Installing SQL 2000 Virtual
unattended failed. I have read "You -cannot perform an unattended
installation to setup a failover cluster"

We recently change the IP of SQL Virtual server, the IP was updated using
the installation wizard. SQL Server starts but does not listens on port 1433,
below error is logged in event log
"19012 : SuperSocket Info: Bind failed on TCP port 1433."

The first pass at my SQL Server 2005 active/active install failed..
It appears to be complaining about the task scheduler on the other node, but
it is running..
I found the following article:

   On SQL Server 2000 Enterprise Edition with SP3a  running on Windows
Server 2003 Enterprise Edition in a Active \ Active Cluster.
There are two nodes on the cluster. Both nodes are active. There are 6
instances of SQL Servers running on each nodes.

I am being asked to migrate various SQL Databases, 2000  and 2005 to a single
large clustered enviroment.
I believe that you can install a single seperate instance of SQL 2000 on a
Virtual Machine (this is required as they each use differeing collation

I read in an article that SCSI is not supported in a Windows 2000 Datacenter
Server cluster. What about Advanced Server?
Thanks in advance,
Leila

i m facing a problem with my cluster setup, i have setup a 2 nde cluster but
my resources cannot filover to the 2nd node, if i move group it will always
fail to node 1,
i have checked the disk signature for both nodes and its the same, i have