SQL05 Mirroring Failover Problems

Giganews Newsgroups
Subject: SQL05 Mirroring Failover Problems
Posted by:  Dan (D…@discussions.microsoft.com)
Date: Fri, 15 Jun 2007

I have set up SQL05 Mirroring with a witness server and everything was
working fine. We had a memory problem on the primary server, and the
mirroring worked, and it failed over to the secondary box as it should have.

Our application has the following in the cn string: 'Data
Source=sql1;Failover Partner=sql2;', and after the failover occured, the
application continued to run without a problem.

The problem arose when we went to shut down the primary server to replace
the RAM. When we did that, our application began throwing errors.

"An error has occurred while establishing a connection to the server.  When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)".

When we turned the primary server back on (but remained failed over to the
2nd box), the errors went away.

It appears that even if you are running on the 2nd box, the 1st still has to
at least be powered on. This doesn't really make sense to me, but is what
appears to be happening.

What is going on here? Do we have something configured incorrectly?