Re: SQL05 Mirroring Failover Problems

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi Dan,
How about running profiler and seeing what is going on when you're clients
are connecting.



"Dan" wrote:

Isn't this what the Failover Partner portion of the cn string is for?

http://msdn2.microsoft.com/en-us/library/5h52hef8(VS.80).aspx


"Roger Wolter[MSFT]" wrote:

Never mind. Upon further reflection, your clients are still connecting to
the primary after the database has failed over to the secondary. The
clients need to connect to the secondary when they can't connect to the
primary. This will require that the application close the connection when
it gets a failure at the primary and reopen the connection to the secondary.
If the application does this, you will still see the failure when it tries
to connect to the primary. If it then connect successfully to the
secondary, you can ignore the error when it tries the primary.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Roger Wolter[MSFT]" <rwolter@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:4216043C-D4D6-44DB-B2A9-83797EAA5216@xxxxxxxxxxxxxxxx
Database mirroring works on a per database basis so my guess would be that
your main database failed over to the secondary but the other databases
didn't and something in your application is still connected to one of the
other databases.

--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Dan" <Dan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:031614F7-6EF1-4600-A19B-EBD73040C1D2@xxxxxxxxxxxxxxxx
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.

Error:
"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?





.

Relevant Pages

  • Re: ADO Connection Timeout
    ... so what happens when a connection failure forces one station to revert ... to a local database? ... Further, you *will* have contention issues, Jet does not support record ... to the central server, but you are willing to live with periods where it ...
    (microsoft.public.data.ado)
  • Re: SQL05 Mirroring Failover Problems
    ... Isn't this what the Failover Partner portion of the cn string is for? ... the primary after the database has failed over to the secondary. ... it gets a failure at the primary and reopen the connection to the secondary. ... The problem arose when we went to shut down the primary server to replace ...
    (microsoft.public.sqlserver.clustering)
  • Re: Synching between Access and MSSQL
    ... The clients will only be disconnected a matter of a few days in most cases ... The challenge is that the information has to be tracked in a main database ... Working out the details of how to keep the data synchronized and accomodate ... I found code to allow an ADO connection to a local Access database but now I ...
    (microsoft.public.access.externaldata)
  • Re: ADO Connection Timeout
    ... When the first test is run, the results are stored in the central database. ... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
    (microsoft.public.data.ado)
  • Re: ADO Connection Timeout
    ... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
    (microsoft.public.data.ado)