The Backup Exec Remote Agent (beremote.exe) crashes on kernel32.dll during VMware backups

Article:TECH207680  |  Created: 2013-06-26  |  Updated: 2013-06-26  |  Article URL http://www.symantec.com/docs/TECH207680
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



When attempting to backup virtual machines with the Agent for VMware, the Backup Exec Remote Agent (beremote.exe) may crash with the errors below.


Error



Application Log error:
Faulting application name: beremote.exe, version: 13.0.5204.125, time stamp: 0x4f39758e
Faulting module name: kernel32.dll, version: 6.0.6002.18740, time stamp: 0x50b58f02

Crash Dump:
FOLLOWUP_IP:
beremote!main+362


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.


Supplemental Materials

SourceETrack
Value3234876
Description

AVVI: beremote randomly crashes on beremote!main+362



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


Terms of use for this information are found in Legal Notices