Mirroring suspended

Category: sql server mirroring

Question

rsherron on Mon, 09 Mar 2015 16:47:11


I currently have mirroring defined and working properly for a database on my SQL 2014 Instance.  I am trying to define mirroring for a new database on this instance. I am using the same principal, mirror and witness server as for the first database. I do not get an error when defining or starting the mirroring, but the mirroring state immediately goes to suspended.  

When looking in the logs I found this, but I am having trouble finding the cause.  

From Event Viewer>

Database mirroring will be suspended. Server instance 'ACOBSQL02' encountered error 2905, state 2, severity 25 when it was acting as a mirroring partner for database 'OpenAgent'. The database mirroring partners might try to recover automatically from the error and resume the mirroring session. For more information, view the error log for additional error messages.

The SQL dump is showing an Access_Violation. 

I am running SQL 2014 standard 12.0.2000.8 on Windows 2012 R2.  This is hosted in Amazon Cloud.

Replies

Lydia Zhang on Tue, 10 Mar 2015 03:31:48


Hi rsherron,

Could you please apply the most recent cumulative update package on SQL Server 2014 to see if the issue is fixed?  For the process of installing hotfixes on SQL Server that is configured to use database mirroring, please review this KB article.

However, if the issue still persists, I suggest you open a case on Microsoft CSS (http://support.microsoft.com/ ). There will be a technical support engineer assigned to analysis the SQL dump files and give you a solution to this issue.

There is a similar article for your reference:
http://support.microsoft.com/kb/2811723

Thanks,
Lydia Zhang

If you have any feedback on our support, please click here.


Lydia Zhang
TechNet Community Support



rsherron on Tue, 10 Mar 2015 12:19:34


Here is info from the minidump...

0:050> .ecxr
rax=000000000000022b rbx=0000000000000100 rcx=0000000231e1d390
rdx=00000000000022b0 rsi=0000000231e1d390 rdi=0000000231e1d390
rip=00007ff94d439f7b rsp=000000006ca4cd60 rbp=0000000000000000
 r8=000000000000022b  r9=0000000000000000 r10=0000000000000100
r11=000000000000012b r12=0000000000000000 r13=00000000635301b8
r14=000000006ca4ce30 r15=00000000635301b8
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
sqlmin!CountRecoveryManager::GetNode+0x4b:
00007ff9`4d439f7b 488b4208        mov     rax,qword ptr [rdx+8] ds:00000000`000022b8=????????????????
0:050> kc
  *** Stack trace for last set context - .thread/.cxr resets it
Call Site
sqlmin!CountRecoveryManager::GetNode
sqlmin!CountRecoveryManager::RedoRowCountDelta
sqlmin!RecoveryMgr::RedoRowCountDeltas
sqlmin!RecoveryMgr::AnalyzeLogRecord
sqlmin!DBMRedoManager::AnalyzeLogRecord
sqlmin!DBMRedoManager::RunAnalysis
sqlmin!DBMRedoManager::ApplyLogSegment
sqlmin!DBMRedoManager::Execute
sqlmin!SubprocEntrypoint
sqldk!SOS_Task::Param::Execute
sqldk!SOS_Scheduler::RunTask
sqldk!SOS_Scheduler::ProcessTasks
sqldk!SchedulerManager::WorkerEntryPoint
sqldk!SystemThread::RunWorker
sqldk!SystemThreadDispatcher::ProcessWorker
sqldk!SchedulerManager::ThreadEntryPoint
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart

I used the script from http://support.microsoft.com/kb/918992/ to regenerate the logins for the principle server and recreated one login.  After doing this I was able to establish the mirroring this morning. I have been monitoring it for the last 20 minutes and it has remained active.  I will continue to monitor the health of the mirror, but I think I may  have found my issue.