Forum Discussion

mmeeggaann's avatar
mmeeggaann
Level 5
12 years ago

Exchange GRT restore - Unable to open the item Database - skipped.

Exchange 2010 restore fails with "0xe00003bf - Cannot open one or more mail messages because of unknown Exchange Web Service errors"

 

Environment:

Exchange 2010 DAG - 1 active copy, 1 passive copy

2 servers with CAS role  - NLB 

The backup with GRT enabled works just fine, but I tried to restore an email to test and it failed:

 

 

Job Completion Status 

Job ended: Friday, February 14, 2014 at 2:51:23 PM

Completed status: Failed

Final error: 0xe00003bf - Cannot open one or more mail messages because of unknown Exchange Web Service errors. Review the job log for more information.

Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-959

Errors 

Click an error below to locate it in the job log

V-79-57344-959 - Unable to open the item Database - skipped.

V-79-57344-959 - Unable to open the item Database - skipped.

V-79-57344-959 - Unable to open the item Database - skipped.

 

Regarding this error, I found the following TN:

 

http://www.symantec.com/docs/TECH190749

 

But, I tried both solutions and it still doesn't work:

Restore redirect to the CAS server

and

Add in the host file the hostname and IP address

 

Does anyone have any ideas about what else it could be?

 

Media server is Backup Exec 2012 SP3, in fact it is the appliance 3600 R2.

 

 

 

 

 

 

 

 

14 Replies

  • @Problemcruncher

     

    Da mir hier niemand weiterhelfen konnte, haben wir auf BackupExec 2014 upgegraded.

    Zusätzlich hab ich dem Backup-Exec-User noch folgende Rechte spendiert (ich denke, dass es evtl. damit schon in der 2012er Version geklappt hätte):

     

    - Organization Management

    - Public Folder Management

    - Recipient Management

    - Server Management

     

    Damit passt bei uns alles so, wie es sein sollte.

    Viel Erfolg!!!

     

    Marco

  • Hallo!

    vielen Dank die schnelle Rückmeldung! Ich probiere gleich mal aus, ob es unter BE 2012 was hilft.

    Liebe Grüße und schönes Wochenende

    Stephan

     

     

  • Sorry, no solution at all. I pimped the RAM of the Exchange Server from 8 GB to 24 GB and moved it to a faster Hypervisor. This helped a little, the error comes now only about very 10 days.