When trying to restore Exchange GRT information the job is successful but no data is restored.

Article:TECH57802  |  Created: 2008-01-19  |  Updated: 2012-07-16  |  Article URL http://www.symantec.com/docs/TECH57802
Article Type
Technical Solution



When trying to restore Exchange GRT information the job is successful but no data is restored.


 Cause 1: (Exchange 2007 and 2010) 

When restoring an Exchange mailbox or individual mailbox item from disk or tape, the restore job is successful but no data is restored. This can occur when the version of ese.dll that is present on the Backup Exec Server is different from the one on the Exchange Server. This condition usually arises when the Exchange server has been patched to more recent versions of service packs or rollup patches for Exchange, but the same service packs or rollup patches have not been applied to the Exchange 2007 Management Tools or Exchange Management Console 2010 installed on the Backup Exec server. 

To confirm this is the issue:

1. Duplicate the data from tape to disk (if the data is on tape).
2. Attempt to restore the data from disk after putting the restore operation in debug mode.
3. Look for the following error in the debug logs:
-514 The version of the log file is not compatible with the ESE version
Cause 2: (Exchange 2007)
The GRT tape backup job and restore job will be successful, but no individual mail items or mailboxes will get restored. The following will also show in the debug log:
Beremote Log: 
[7256] 12/29/08 09:17:45 Using EDB Provider for Browse/Backup.
[7256] 12/29/08 09:17:45 Logon: m_lpMAPISession->Logon returned 80004005
[256] 12/29/08 09:17:45 OPEN DATABASE FAILED: -510 There was a failure writing to the log file.
[7256] 12/29/08 09:17:45 MB2_Chgdir:Logon returned e000fea9
[7256] 12/29/08 09:17:45 TF xfer time = 44 seconds.  

The Exchange MAPI (Messaging Application Programming Interface) Link that Backup Exec requires to properly perform a GRT Tape Backup is broken.


Cause 1:
To resolve this issue update Exchange Management Tools or Exchange Management Console installed on the Backup Exec server to the same level of patches applied on the Exchange server. Confirm that the ese.dll versions match on both servers before retrying the restore operation.

If the error still happens after upgrading the tools on the Media server, then check the version of the following files:

* Ese.dll file found on the Exchange installation folder (default path is %Program Files%\Microsoft\Exchange Server\Bin) on the Media Server. For example, a 32bits server with Exchange Management Tools Service Pack 1 installed, should have an Ese.dll with version
* Ese.dll file found on the same Exchange installation folder but on the Exchange Server. This file on a 64bits Exchange server should be if Exchange 2007 Service Pack 1 is installed. The .3 and .5 denotes that the file is for 32bits or 64bits.

If this is ok, then check:

* Ese32.dll file inside the Backup to Disk folder, under the IMGxxxxxx folder that corresponds to the affected Backup Set. Compare this file with the Ese.dll file on the same folder. Both files should have the same version (except for the last .3 or .5).

If the files are not the same version, then copy the Ese.dll file from the Media Server and rename it to Ese32.dll, so that Ese.dll and Ese32.dll have the same version. Once changed, the version mismatch should not occur and the restore should be successful. 

Cause 2:
1. Uninstall and reinstall MAPI-CDO on the Exchange Server. Download it from http://www.microsoft.com/en-us/download/details.aspx?id=1004
2. Uninstall and reinstall the Remote agent on the Exchange server. 
3. Run another GRT Backup and restore to test.
Note: Reinstalling MAPI will only fix the issue for the backups taken after reinstalling MAPI.
Workaround for Old Backup Sets:
Duplicate data from tape to disk 

Legacy ID


Article URL http://www.symantec.com/docs/TECH57802

Terms of use for this information are found in Legal Notices