cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec services stop unexpectedly

Service_Informa
Level 3

Sometimes the Backup Exec services stop and the two following messages displayed in the event log :

Faulting application name: beremote.exe, version: 13.0.4164.109, time stamp: 0x4cffac43
Faulting module name: ndmpsrvr.dll, version: 13.0.4164.116, time stamp: 0x4d7a6d14
Exception code: 0xc0000005
Fault offset: 0x0000000000191d48
Faulting process id: 0x13fc
Faulting application start time: 0x01cc2057a58179c8
Faulting application path: C:\Program Files\Symantec\Backup Exec\beremote.exe
Faulting module path: C:\Program Files\Symantec\Backup Exec\ndmpsrvr.dll
Report Id: 18315363-9873-11e0-a4bd-001b2141c355

And this one too :

A solution ?

1 ACCEPTED SOLUTION

Accepted Solutions

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

The maximum memory dumps error can be solved by removing (moving or deleteing ) the DMP files from inside the ..\backup Exec\BEDBG folder) However if you continue to have crashes more DMP files will be created so you do need to solve the cause at some point.

I'd suggest updating to 2010 R3 (13.0.5204) might be a useful starting point.

View solution in original post

2 REPLIES 2

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi,

 

Depends on what was happening when beremote.exe crashed...

First bit of troubleshooting is to download the available patches for BE and apply them to your media server before doing a push-install to your remote servers.

Also check and make sure that the RAWS agent on that server is running and publishing correctly to your media server (assuming it is a remote server).

 

Thanks!

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

The maximum memory dumps error can be solved by removing (moving or deleteing ) the DMP files from inside the ..\backup Exec\BEDBG folder) However if you continue to have crashes more DMP files will be created so you do need to solve the cause at some point.

I'd suggest updating to 2010 R3 (13.0.5204) might be a useful starting point.