Exchange 2007 Database not mountable - Event ID 9518, 9519

PAndreas
PAndreas used Ask the Experts™
on
Hi Experts,

since last Sunday I do have a very criitical failure with my Exchange 2007 in a Microsoft EBS 2007, all running on two Microsoft Hyper-V Server (Hyper-V01 hosting the "Mmgt Server an the Sec Server. Hyper-V02 hosting Msg Server and a stand alone Sharepoint Server).

But lets start from the scratch. All started on Sunday when Hyper-V02, after a dirty shutdown, booted the Msg Server from an old snapshot, a snapshot which was older than three month. All services and files had a timestamp 04.2009. So my first problem was a AD that did not run properly and a non working DNS, because of Kerberos Ticket and so on. Not a big deal on that one, some hours later AD and DNS where back in business. Now there was still the Exchange where I had several error messages like no permission here and no permission there (Security Pol, AD ...). A use of setup.exe /prepareAD from my Exchange CD fixed all the errors and the services came up and running. So far so good.

The one and only problem I still have is that I can not mount the Database anymore. A eseutil /mh reveilled that the DB had a dirty shutdown. So fixing this with eseutil /d and eseutil /p let my hope to erase all of my problems, but unfortenately it wasn't like that. Still the same error. The errors I get are Event ID9518 and 9519. My next thought was to create a new Database in a new Storagegroup which worked like a charms. But I still do not get the old one running and/or Mailboxes out of it.

Attached I added most of the logfiles.

I really hope to find some help here.


Greetz and Thx
Patrick
Protokollname: Application
Quelle:        MSExchangeFBPublish
Datum:         20.07.2009 17:03:55
Ereignis-ID:   8213
Aufgabenkategorie:Allgemein
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      srv-msg.cegos.local
Beschreibung:
Der Microsoft Exchange-Systemaufsichtsdienst konnte die Sitzung für den virtuellen Computer SRV-MSG nicht erstellen. Die Fehlernummer ist 0x80040111.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeFBPublish" />
    <EventID Qualifiers="49153">8213</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-07-20T15:03:55.000Z" />
    <EventRecordID>1400917</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-msg.cegos.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SRV-MSG</Data>
    <Data>0x80040111</Data>
  </EventData>
</Event>
 
 
------------------------------------------------------------------------------------------------------
 
 
Protokollname: Application
Quelle:        MSExchange ADAccess
Datum:         20.07.2009 16:44:57
Ereignis-ID:   2152
Aufgabenkategorie:Allgemein
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      srv-msg.cegos.local
Beschreibung:
Prozess w3wp.exe (OWA) (PID=4392). Fehler bei RPC-Anforderung an den Microsoft Exchange Active Directory-Topologiedienst. Fehler: 1753 (Error 6d9 from HrGetTopologyVersion). Stellen Sie sicher, dass der Dienst ausgeführt wird.  
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchange ADAccess" />
    <EventID Qualifiers="49156">2152</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-07-20T14:44:57.000Z" />
    <EventRecordID>1400909</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-msg.cegos.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>w3wp.exe (OWA)</Data>
    <Data>4392</Data>
    <Data>1753</Data>
    <Data>Error 6d9 from HrGetTopologyVersion</Data>
  </EventData>
</Event>
 
-----------------------------------------------------------------------------------------------------------
 
 
Protokollname: Application
Quelle:        MSExchangeFBPublish
Datum:         20.07.2009 16:38:55
Ereignis-ID:   8213
Aufgabenkategorie:Allgemein
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      srv-msg.cegos.local
Beschreibung:
Der Microsoft Exchange-Systemaufsichtsdienst konnte die Sitzung für den virtuellen Computer SRV-MSG nicht erstellen. Die Fehlernummer ist 0x80040111.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeFBPublish" />
    <EventID Qualifiers="49153">8213</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-07-20T14:38:55.000Z" />
    <EventRecordID>1400908</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-msg.cegos.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SRV-MSG</Data>
    <Data>0x80040111</Data>
  </EventData>
</Event>
 
 
------------------------------------------------------------------------------------------------------------
 
 
Protokollname: Application
Quelle:        MSExchangeIS
Datum:         20.07.2009 16:22:32
Ereignis-ID:   9518
Aufgabenkategorie:Allgemein
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      srv-msg.cegos.local
Beschreibung:
Fehler 0xfffffae7 beim Starten von Speichergruppe /DC=local/DC=cegos/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=First Organization/CN=Administrative Groups/CN=Exchange Administrative Group (FYDIBOHF23SPDLT)/CN=Servers/CN=SRV-MSG/CN=InformationStore/CN=First Storage Group im Microsoft Exchange Server-Informationsspeicher. 
MDB failed to start.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeIS" />
    <EventID Qualifiers="49158">9518</EventID>
    <Level>2</Level>
    <Task>6</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-07-20T14:22:32.000Z" />
    <EventRecordID>1400888</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-msg.cegos.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>0xfffffae7</Data>
    <Data>/DC=local/DC=cegos/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=First Organization/CN=Administrative Groups/CN=Exchange Administrative Group (FYDIBOHF23SPDLT)/CN=Servers/CN=SRV-MSG/CN=InformationStore/CN=First Storage Group</Data>
    <Data>MDB failed to start</Data>
    <Binary>5B444941475F4354585D00000E020000FFA41100000000000003000200008B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFBD442010000000000359201000000000E83240100F010480D713401004060480D713401004060480D713401004060480D713401004060480D4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B304010E7FAFFFF8B264010E7FAFFFF1F094010E7FAFFFFF31C4010E7FAFFFF730D4010E7FAFFFFBD4420100000000003592010000000000359201000000000CD4A201000000000BD5F201000000000CD4A201000000000BD5F2010000000000359201000000000CD4A201000000000BD5F201000000000</Binary>
  </EventData>
</Event>
 
 
--------------------------------------------------------------------------------------------------
 
 
Protokollname: Application
Quelle:        MSExchangeIS
Datum:         20.07.2009 16:22:32
Ereignis-ID:   9519
Aufgabenkategorie:Allgemein
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      srv-msg.cegos.local
Beschreibung:
Fehler 0xfffffae7 beim Starten von Datenbank 'First Storage Group\Mailbox Database' im Microsoft Exchange-Informationsspeicher.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeIS" />
    <EventID Qualifiers="49158">9519</EventID>
    <Level>2</Level>
    <Task>6</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-07-20T14:22:32.000Z" />
    <EventRecordID>1400887</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-msg.cegos.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>0xfffffae7</Data>
    <Data>First Storage Group\Mailbox Database</Data>
    <Binary>4661696C656420746F20636F6E666967757265204D4442005B444941475F4354585D00000E020000FFA41100000000000003000200008B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFD4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B2A4010E7FAFFFFBD442010000000000359201000000000E83240100F010480D713401004060480D713401004060480D713401004060480D713401004060480D4224010E7FAFFFF8B374010E7FAFFFF8B3B4010E7FAFFFF8B304010E7FAFFFF8B264010E7FAFFFF1F094010E7FAFFFFF31C4010E7FAFFFF730D4010E7FAFFFF</Binary>
  </EventData>
</Event>

Open in new window

dcdiag.log
eseutil-mh.txt
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
Try this.  Specifically resolution #3

http://support.microsoft.com/kb/896143

Author

Commented:
Here ist what I've done:

run eseutil /mh "e:\exchange server\mailbox\first storagegroup\mailbox database.edb"

the result on that was a Status: clean shutdown and Repair Counts: 2

So I backed up all the logfiles in the first storagegroup folder and deleted them afterwards.
The only file in there the mailbox database.edb. I then started the exchange services again
and tried to mount the database. The result was followring error message

--------------------------------------------------------
Microsoft Exchange Fehler
--------------------------------------------------------
Die Datenbank 'Mailbox Database' konnte nicht bereitgestellt werden.
Mailbox Database
Fehler
Fehler:
Exchange kann die angegebene Datenbank nicht bereitstellen. Angegebene Datenbank: SRV-MSG\First Storage Group\Mailbox Database; Fehlercode: MapiExceptionNotFound: Unable to mount database. (hr=0x80004005, ec=-1305)
.
--------------------------------------------------------
OK
--------------------------------------------------------
 
Commented:
Look at the properties of the store.  Verify the location listed in EMC matches the location of the actual file.  Also, make sure that the version of exchange you are using now matches the version that the databases are on.  If you are using restored databases that were backed up on SP1, make sure that exchange sp1 is installed.

Also check here.  http://support.microsoft.com/kb/925825

Author

Commented:
Thanks for that information cmcall, that was really a fact I haven't tried yet. But anywhy, bringing the Exchange to the same patchlevel as before and as the database has didn't solve the problem.

But I also got some new infomation about that. This morning I open a call at Microsoft tech support stateing my problem. After some investigation on that the support tech said, that the hole enviroment we build, which is in detail, a virtualized ESB Server running on two Hyper V server (non cluster), useing dynamic harddrives and running datasnapshots on all server as a recovery method, is NOT supported by Microsoft.
 
So the way to fix the problem with the exchagne is to create an new databse in a new storagegroup and run a recovery job from the last full backup we have.

Isn't that strange?

Author

Commented:
Some final words on this one ...

After a new mailbox database and a also a new public folder database was created, I ran a recovery job from our last fullbackup directly into the mounted datastores.
Some GB and hours later my BackupExec 12.5 /w Exchange agent stated successfull, everything was recovered and fine. After a reboot of the server and a quick view
into the event logs I started up my Outlook client - the first message almost jumping into my face was "Exchange is in recovery mode ...." I had the options to "go ahead"
or "work offline" or "cancel" so I decided to go by the first option and guess what, my outlook was online with my exchange and all my mails where back where they should be.

End of report

Greetz
Patrick

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial