Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Remote Agent failing because of vmwaretools.dll

Created: 13 Nov 2012 • Updated: 04 Feb 2013 | 1 comment
This issue has been solved. See solution.

I am seeing the failure listed below happening on my Backup Exec media server that is backing up a VMWare wnvironment.  It just started over the weekend.  Any help would be appreciated.

 

Log Name:      Application
Source:        Application Error
Date:          11/13/2012 3:47:02 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sabackup001.america.littelfuse.com
Description:
Faulting application beremote.exe, version 13.0.5204.127, time stamp 0x4fede72f, faulting module vmwaretools.dll, version 2.0.134.0, time stamp 0x4eb13705, exception code 0xc0000005, fault offset 0x004deee3, process id 0x548, application start time 0x01cdc0fb41cf8f64.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-11-13T09:47:02.000Z" />
    <EventRecordID>49759</EventRecordID>
    <Channel>Application</Channel>
    <Computer>sabackup001.america.littelfuse.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>beremote.exe</Data>
    <Data>13.0.5204.127</Data>
    <Data>4fede72f</Data>
    <Data>vmwaretools.dll</Data>
    <Data>2.0.134.0</Data>
    <Data>4eb13705</Data>
    <Data>c0000005</Data>
    <Data>004deee3</Data>
    <Data>548</Data>
    <Data>01cdc0fb41cf8f64</Data>
  </EventData>
</Event>

Comments 1 CommentJump to latest comment

Colin Weaver's picture

We have at least one private hotfix dealing with beremote crashes during VMware backups against Backup Exec 20120 R3, however to be issued with such a hotfix (which is similar to a beta) we have to confirm you do have the same problem and this needs a formal Technical Support Case.

SOLUTION