cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec 2014: Failed Restore With Exchange 2013 (Mailbox Item)

djoyner
Level 2

I attempt to restore a mailbox item on Exchange 2013, but get Final error: 0xe00003bf - Cannot open one or more mail messages because of unknown Exchange Web Service errors.  Review the job log for more information.

Article TECH190749 says the cause is that during the restore process Backup Exec tries to establish Exchange Web Services (EWS) connection on the mailbox server instead of the Client Access Server (CAS) which results in the failure.  This may be true, however, our Exchange 2013 server is not only the mailbox server but is also CAS.  The only workaround is restoring to PST (Disclaimer: the server that you restore the PST to needs Outlook installed.)  Not a bad workaround if you only have a couple of items here and there to restore, but what if I need to do a brick-level restore of the whole mailbox?  Can it even do a brick-level restore?

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.

V-79-57344-959 - Unable to open the item [50% OFF] One-Click Audio Enhancement for your Mac - BOOM -...
V-79-57344-959 - Unable to open the item [TechRepublic] Computer vision and the future of mobile dev...
V-79-57344-959 - Unable to open the item [TechRepublic] Going in-house for app development - skipped...
V-79-57344-959 - Unable to open the item [TechRepublic] Myo armband makes smartglasses hands free - ...
V-79-57344-959 - Unable to open the item [TechRepublic] Kickstarter campaign pushes security for hom...
V-79-57344-959 - Unable to open the item  Password Expiration Report - ctia.org - skipped.

V-79-57344-959 - Unable to open the item $25 any Techtool App - Final 2 Days to Fix Your Own Mac - s...
3 REPLIES 3

pkh
Moderator
Moderator
   VIP    Certified
Brick level restore went out with Exchange 2003

VJware
Level 6
Employee Accredited Certified

This is quite a generic error. Reviewing the debug logs would help and i would recommend to log a formal support case.

djoyner
Level 2

According to the EWSLog generated by Exchange 2013, there is a compatiblity CAS version problem:

[33e0] 09/04/14 11:21:41  Failed in Connecting to EWS  Exchange Server doesn't support the requested version.

[33e0] 09/04/14 11:21:41  Trying Version Exchange2013

[33e0] 09/04/14 11:21:41  Could not use...... Version Exchange2013  Exchange Server doesn't support the requested version.

[33e0] 09/04/14 11:21:41  Trying Version Exchange2010_SP2

[33e0] 09/04/14 11:21:42  Could not use...... Version Exchange2010_SP2  Access is denied. Check credentials and try again.

[33e0] 09/04/14 11:21:42  Trying Version Exchange2010_SP1

[33e0] 09/04/14 11:21:42  Could not use...... Version Exchange2010_SP1  Access is denied. Check credentials and try again.

[33e0] 09/04/14 11:21:42  Trying Version Exchange2010

[33e0] 09/04/14 11:21:42  Could not use...... Version Exchange2010  Access is denied. Check credentials and try again.

[33e0] 09/04/14 11:21:42  Trying Version Exchange2007_SP1

[33e0] 09/04/14 11:21:42  Could not use...... Version Exchange2007_SP1  Access is denied. Check credentials and try again.

[33e0] 09/04/14 11:21:42  Failed in finding a compatible cas version  

[33e0] 09/04/14 11:21:42  AutoDiscover Failed in locating the url  Exchange Server doesn't support the requested version.

Appears to be a Microsof issue, according to Symantec.  I'm calling them now...