Showing results for 
Search instead for 
Did you mean: 

Random beserver.exe crashes after upgrade to Backup Exec 2012 SP1

Level 3

After the upgrade to Backup Exec 2012 SP1 the beserver.exe crashes randomly on different managed media servers, causing the communication with the CASO to stall. The media servers as well as the CASO are all Windows 2008 R2 machines, including latest service pack and Windows updates. Attached you will find a picture of the event viewer.



Level 4

Hello! I get this error after installing SP1.


Log Name:      Application
Source:        Application Error
Date:          2012-06-07 10:07:35
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MyComputer
Faulting application name: beserver.exe, version: 14.0.1798.105, time stamp: 0x4fa3de95
Faulting module name: serdll.dll, version: 14.0.1798.503, time stamp: 0x4fc09f1f
Exception code: 0xc0000005
Fault offset: 0x0000000000014335
Faulting process id: 0xef8
Faulting application start time: 0x01cd448483069049
Faulting application path: C:\Program Files\Symantec\Backup Exec\beserver.exe
Faulting module path: C:\Program Files\Symantec\Backup Exec\serdll.dll
Report Id: d679ef69-b077-11e1-b031-001cc461f152
Event Xml:
<Event xmlns="">
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <TimeCreated SystemTime="2012-06-07T08:07:35.000000000Z" />
    <Security />
    <Data>C:\Program Files\Symantec\Backup Exec\beserver.exe</Data>
    <Data>C:\Program Files\Symantec\Backup Exec\serdll.dll</Data>


Downloaded SP1 manually and installed as admin. Still crashes......


Level 4

Hallo Xodar

try a repair installation first.

Level 3

Same things has happened to me after installing sp1.

Level 2

I got an email from Symantec Support which helped me to fix the issue.


  • stop all BE services
  • ensure SQL Server (BKUPEXEC) service is still running
  • open a command prompt (I started it with administrative privileges, not sure if it's needed though)
  • type bemig and wait until the command has completed
  • start all BE services again

Now I'm able to open the Backup Exec Console again and run my Backup Jobs.

Hopefully this helps some of you to fix the issue.


Level 6
Employee Accredited Certified

That would not be a right way to fix this issue as it will make all the other good things in SP1 completely ineffective. If your beserver.exe is crashing on beserver.exe then we do have a proper script to resolve this issue. I would suggest you to please contact Support on the same case number and ask for the right help.

Could you also PM me the case number where this steps were performed? May be the tech was not completely aware of the new script as continuous development is going on to resolve these issues.

Please PM me the case number.



Level 3

How about providing the script instead of just mentioning it?

Level 2



I was contacted by Symantec Support. They provided me the official solution which you can find here:

PS: I couldn't run the script yet because I have some running jobs at the moment.

I hope this helps.



Level 3

Thanks, but didn't work.


c:\Program Files\Symantec\Backup Exec>sqlcmd -E -S localhost\bkupexec -d bedb -i
Sqlcmd: '-d bedb -i fix.sql': Unexpected argument. Enter '-?' for help.

Level 6
Employee Accredited Certified

Is your Backup Exec installed on the default instance BKUPEXEC.... if not then change the instance name in the above command.

Also before running the script please ensure that you are getting the same error in the event viewer because we have seen beserver service crashing on other modules too and that will have some different fix.




Not applicable

Had the same problem, looks like sqlcmd is somehow allergic to the file path of BEWS (long name/spaces/rights?).  I moved the fix.sql to c:\temp and run it from there without an issue.


Not applicable

Hello. Same problem here: after trying all the above suggestions, I've noticed that every time I install SP1 I got a "successful install" notification in event viewer but no request for rebooting. If I launch BE2012 I'm told I must reboot the system, and so I do. BUT server doesn't restart properly: it's stuck between CTRL-ALT-CANC pressed and logon credentials and no RDP connection or remote shutdown is allowed. I have to brutally shutdown the server, and the second time it reboots properly.

This happens every time I've tried installing the SP1, both via LiveUpdate and via standalone installer.

If I remove the SP1, BE2012 works correctly, so at this time I have to work without it.

I'm following this thread hoping to see a solution.

Employee CPEP

I wanted to send out a note to everyone on this thread that we are in the process of uploading SP1a to the Symantec Live Update Servers.  I'm expecting this update to be available for download through Live Update around 7pm EST (6/12/2012).