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

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

Created: 27 Feb 2012 • Updated: 29 Feb 2012 | 16 comments
This issue has been solved. See solution.

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
 

Comments 16 CommentsJump to latest comment

ZeRoC00L's picture

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 !

If this response answers your concern, please mark it as a "solution"

VJware's picture

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 picture

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.

Backupday's picture

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

VJware's picture

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

SOLUTION
Backupday's picture

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

VJware's picture

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

VJware's picture

Usually the bedssql2.dll is referenced when it is altered...especially due to SQL databases corruption...Might want to have the DBA check the consistency of the SQL dBs

Backupday's picture

I tried to run a backup without the sql db the remote agent still crashes.
Faulting application beremote.exe, version 13.0.5204.114, faulting module bedssql2.dll, version 13.0.5204.0, fault address 0x00031431.
And again bedssql2.dll i will try the rename and see how it goes.

Backupday's picture

After renaming bedssql2.dll the backup worked without any problems.
So i could say that those sql dbs need a checkup?

VJware's picture

Yep, as most plausible reason is some corruption amongst the SQL databases which alters that dll

Backupday's picture

Thank you very mutch VJware.
i will have one of our sql admins take a look at it.