Backup Exec 2012 fails to detect Exchange server resources after an Exchange update or service pack is installed

Article:TECH212774  |  Created: 2013-11-25  |  Updated: 2013-11-25  |  Article URL http://www.symantec.com/docs/TECH212774
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Issue



After installing an Exchange Service pack or minor update, Information Store resources are no longer available under the server container object in Backup Exec 2012.


Error



Backup Exec does not detect Exchange.  From beremote debug log on the Exchange server, this is visible as follows:

BEREMOTE: [11/22/13 12:01:37] [16472]     2013-11-22T12:01:37.025 [fsys\ese]           - [FSYS:ESE07]   FindDrives ... This is not an Exchange Server (0)
BEREMOTE: [11/22/13 12:01:37] [16472]     2013-11-22T12:01:37.134 [fsys\ese]           - CreateTempDLE: \\Venus
BEREMOTE: [11/22/13 12:01:37] [16472]     2013-11-22T12:01:37.150 [fsys\ese]           - CreateTempDLE: \\Venus
BEREMOTE: [11/22/13 12:01:37] [16472]     2013-11-22T12:01:37.150 [fsys\ese]           - CreateTempDLE: \\Venus
BEREMOTE: [11/22/13 12:01:37] [16472]     2013-11-22T12:01:37.212 [fsys\ese]           - [FSYS:ESE07]   ESE_SurrogateCalling ... Error: got invalid version (0)
BEREMOTE: [11/22/13 12:01:37] [16472]     2013-11-22T12:01:37.212 [fsys\ese]           - [FSYS:ESE07]   ESE_SurrogateCalling ... Error: got invalid version (0)
BEREMOTE: [11/22/13 12:01:37] [16472]     2013-11-22T12:01:37.212 [fsys\ese]           - [FSYS:ESE07]   ESE_SurrogateCalling ... Error: got invalid version (0)


Environment



This has been observed in environments with a stand-alone Exchange server


Cause



This issue is suspected to be caused by missing registry entries or files used by Backup Exec to detect Exchange.


Solution



-------
 
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
 
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see  http://www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
 

NOTE:
Customers experiencing this issue are encouraged to contact Symantec Technical Support as data is still being collected to assist in resolving this issue.
 


Supplemental Materials

SourceETrack
Value3373876
Description

EXCH: After installing Exchange 2010 SP3, BE does not identify mailbox server as an Exchange server.



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


Terms of use for this information are found in Legal Notices