Forum Discussion

Backupday's avatar
Backupday
Level 4
13 years ago

Final error: 0xe000fe30 - A communications failure has occurred. (local backup)

Hi Guys,

I am having a problem with backup exec 2010

When i run a backup it will always give me this error message:
Final error: 0xe000fe30 - A communications failure has occurred.
Final error category: Server Errors

What i already tried :
Reinstalling beremote (did not work)
Cheking the ports (did not work)

What does work: exchange backup.

Thanx in advance
 

2010
Backing Up
Backup and Recovery
Backup Exec
MS Exchange
Windows
  • VJware's avatar
    VJware
    13 years ago

    Are you using any SQL databases ?

    If no, then attempt the following:

    - Stop the Remote Agent service

    - Rename the bedssql2.dll file to bedssql2.old ( typically found at \Program Files\Symantec\BackupExec\RAWS)

    Restart the remote agent service & all the BE services as well

    Re-attempt the backup

     

  • ZeRoC00L's avatar
    ZeRoC00L
    Level 6
    13 years ago

    Do you have BE 2010 R3 and all available service packs and hotfixes installed ?
    If not, please install R3 and run liveupdate to update BE !

  • VJware's avatar
    VJware
    Level 6
    13 years ago

    Not sure how did you re-install beremote.exe when its a local backup

    Exclude your BE services from any AV scans...also check if port 10000 is in use by some other process/app or not

  • Backupday's avatar
    Backupday
    Level 4
    13 years ago

    Hi i disabled the AV and had the same problem when i ran the backup without.

    I did a port check like you asked and the port is a good boy this time.
    TCP    **-srv01:10000         **-srv01.******.local:0  LISTENING so no problem on the port

    and I found this in the application log.
    Faulting application beremote.exe, version 13.0.5204.114, faulting module bedssql2.dll, version 13.0.5204.0, fault address 0x00031431.

  • VJware's avatar
    VJware
    Level 6
    13 years ago

    Try the solution per this KB - http://www.symantec.com/docs/TECH153810

  • Backupday's avatar
    Backupday
    Level 4
    13 years ago

    The link comes back with nothing when i use it.
    Could you check the link please?

  • VJware's avatar
    VJware
    Level 6
    13 years ago

    Are you using any SQL databases ?

    If no, then attempt the following:

    - Stop the Remote Agent service

    - Rename the bedssql2.dll file to bedssql2.old ( typically found at \Program Files\Symantec\BackupExec\RAWS)

    Restart the remote agent service & all the BE services as well

    Re-attempt the backup

     

  • Backupday's avatar
    Backupday
    Level 4
    13 years ago

    I am using backup exec to backup an sql db.
    Can i still try this solution?

  • VJware's avatar
    VJware
    Level 6
    13 years ago

    If there is no SQL on this remote server, it should be fine...

    this dll rename actually disables the SQL agent on the server where the change is made