InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 18 Jun 2013 19:47:23 GMT20http://www.sqlservercentral.com/Forums/Topic1032231-1549-1.aspxnormally stopping and restarting the endpoints will cure the issueWed, 31 Oct 2012 04:19:01 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1032231-1549-1.aspxI was helped by the following: DROP\CREATE Mirroring Endpoint on Mirror Serser.Tue, 30 Oct 2012 09:45:47 GMTd-i-m-onhttp://www.sqlservercentral.com/Forums/Topic1032231-1549-1.aspxThank you so much, I had stuck production serverThu, 04 Oct 2012 12:49:22 GMTgianmhhttp://www.sqlservercentral.com/Forums/Topic1032231-1549-1.aspxYou should first have looked in your sqlserver errorlog.- what topology of mirroring were you using ?- did you have a look at your SQLServer ERRORLOG file ?- did you find related messages ?- are you capturing dbmirroring events you all your instances ?Please post your @@version info.Thu, 09 Dec 2010 09:20:50 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic1032231-1549-1.aspxI had this happen once, but when I tried to replicate it in a dev environment to try to trouble shoot it, I could not force it to repeat.I was in HSHA, mirroring is supposed to prevent split brain issues like this from happening, but that is exactally what I did, recovered one set of databases and re-initialized mirroring.What is the build version of your 2008 server, sp1, sp2, sp1 & some CU's. There was an issue with the way the transactions were passed along in mirroring that could cause mirroring to enter a suspended state, that was fixed in CU 5 for sp1 that we applied, but this is completely seperate from the issue you are posting about.If your running SP 2 it would have been fixed in there as well.Thu, 09 Dec 2010 09:05:45 GMTSQLBallshttp://www.sqlservercentral.com/Forums/Topic1032231-1549-1.aspxHi,today I had the problem, that after a restart of my two mirrored database servers on both servers all databases where in the state "Principal, disconnected, in recovery". So both databases weren't available.We "fixed" this with "ALTER DATABASE XXX SET PARTNER OFF" to bring the database back online...Did you ever saw this behaviour and know a better solution than removing the mirroring session from the database?Thanks in advance!Wed, 08 Dec 2010 17:21:14 GMTJetro