I have SBE2010R3 server CASO & MMS.
If i create New restore job in CASO i have next information message in windows logs->application
A memory dump has been captured C:\Program Files\Symantec\Backup Exec\BEDBG\beserver.exe_7372_0.dmp
And creates many files
After i see in windows logs->application -> Errors with text
Process beserver.exe requested memory dump but the maximum number of memory dumps has already been reached.
I delete this dump but after create New restore job his dmp creates again with other code(10624,11456,11984,3532)
If your error in Event Viewer is the same as that listed below, make sure you have BE 2010 R3 SP4 installed...
Clear the BEDBG folder as well so that older dumps are removed.
From the event viewer, post which module is beserver crashing on as well. Does it crash only when you attempt a restore ? if yes, does it matter which resource you try to restore or not ?
I removed all dump in folder BEDBG, but i run restore or backup job dmp create now.
In event viever only record:
Log Name: Application
Date: 04.08.2014 12:01:08
Event ID: 257
Task Category: (1)
A memory dump has been captured C:\Program Files\Symantec\Backup Exec\BEDBG\beserver.exe_12396_9.dmp
<Provider Name="BEDBG" />
<TimeCreated SystemTime="2014-08-04T09:01:08.000000000Z" />
<Data>C:\Program Files\Symantec\Backup Exec\BEDBG\beserver.exe_12396_9.dmp</Data>
Application event id 1000:
Faulting application name: beremote.exe, version: 13.0.5204.1279, time stamp: 0x53321a3b
Faulting module name: bedsnt5.dll, version: 13.0.5204.1279, time stamp: 0x53321a1d
Exception code: 0xc0000005
Fault offset: 0x000000000005fea3
Faulting process id: 0x2cc0
Faulting application start time: 0x01cfacc523687228
Faulting application path: C:\Program Files\Symantec\Backup Exec\beremote.exe
Faulting module path: C:\Program Files\Symantec\Backup Exec\bedsnt5.dll
Report Id: 93168f01-18e3-11e4-8626-e41f13b315d0
Edit the properties of the Backup Exec Remote Agent service and then over to the Recovery tab. Set the failure options to 'Restart the service' and observe the backups.
If the service still crashes, would recommend to log a formal support case.