cancel
Showing results for 
Search instead for 
Did you mean: 

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

DieGoettlichen
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.

 

1 ACCEPTED SOLUTION

Accepted Solutions

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi,

 

Try running a repair of BE on the media server using Add/Remove Programs to see if this fixes it. If not, next thing to check is your AV/firewall to see if it is perhaps blocking BE now for some obscure reason.

Lastly, if this doesn't fix things, remove SP1, and then reapply it.

Thanks!

View solution in original post

31 REPLIES 31

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi,

 

Try running a repair of BE on the media server using Add/Remove Programs to see if this fixes it. If not, next thing to check is your AV/firewall to see if it is perhaps blocking BE now for some obscure reason.

Lastly, if this doesn't fix things, remove SP1, and then reapply it.

Thanks!

rainer_fuebi
Level 2
Partner

I have exactly the same problem. I tried:

1) repair -> no success

2) Uninstall SP1  - >no success.

Any other ideas?

 

EliasA
Moderator
Moderator
Employee CPEP

When you say "Uninstall SP1 ->no success" you mean you still get the crashes without SP1?  Just trying to determine if this is specific to SP1 or not.  Can you clarify please?

rainer_fuebi
Level 2
Partner

yes, It is still not working. So far I can not tell you what the problem is. Just before without SP1 it was working. I am trying tomorrow a few things.

 

David_Palmersto
Level 4

Anybody got a support incident already that we can tag to?

 

Here is one of our crashes:

Log Name:      Application
Source:        Application Error
Date:          6/2/2012 12:21:03 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      STBACK1110.heli-cal.local
Description:
Faulting application name: beserver.exe, version: 14.0.1798.105, time stamp: 0x4fa3de95
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000005
Fault offset: 0x0000000000031f19
Faulting process id: 0xd3c
Faulting application start time: 0x01cd404a691e33ad
Faulting application path: C:\Program Files\Symantec\Backup Exec\beserver.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 828d7520-ac83-11e1-9c7d-782bcb51a019
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-06-02T07:21:03.000000000Z" />
    <EventRecordID>41782</EventRecordID>
    <Channel>Application</Channel>
    <Computer>STBACK1110.heli-cal.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>beserver.exe</Data>
    <Data>14.0.1798.105</Data>
    <Data>4fa3de95</Data>
    <Data>ntdll.dll</Data>
    <Data>6.1.7601.17725</Data>
    <Data>4ec4aa8e</Data>
    <Data>c0000005</Data>
    <Data>0000000000031f19</Data>
    <Data>d3c</Data>
    <Data>01cd404a691e33ad</Data>
    <Data>C:\Program Files\Symantec\Backup Exec\beserver.exe</Data>
    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
    <Data>828d7520-ac83-11e1-9c7d-782bcb51a019</Data>
  </EventData>
</Event>

David_Palmersto
Level 4

Spent almost 2 hrs on support phone, came to conclusion that our local problems need a clean slate, so I'm starting with any Dell firmware/updates, them moving on to Windows 2008 R2 and SP updates, then back to ONLY installing BE2012, then SP1, then any hotfixes if they still show.  We'll see then what our status may be..

 

DieGoettlichen
Level 3

Hi,

repairing using the software management in the control panel worked for me. I left the SP1 installed. However I had to do this for two servers. Usually the installation routine should ensure that such kind of actions should not be necessary.

However thanks for the help!

Bembel
Level 3

We are running a Windows Server 2008 R2 SP1 (German, latest updates) on VMware 5.0.1 (SCSI DirectPath I/O -> HP Autoloader 1/8 G2), machine was upgraded from BE 2010 to 2012 a few weeks ago, just updated to BE 2012 SP1 last Friday (June 1st) afternoon and in the first night beserver.exe crashed:

Protokollname: Application
Quelle:        .NET Runtime
Datum:         02.06.2012 04:00:29
Ereignis-ID:   1026
Aufgabenkategorie:Keine
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      <FQDN>
Beschreibung:
Anwendung: beserver.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: Ausnahmecode c0000005, Ausnahmeadresse 0000000073728193

...followed by...

Protokollname: Application
Quelle:        Application Error
Datum:         02.06.2012 04:00:31
Ereignis-ID:   1000
Aufgabenkategorie:(100)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      <FQDN>

Beschreibung:
Name der fehlerhaften Anwendung: beserver.exe, Version: 14.0.1798.105, Zeitstempel: 0x4fa3de95
Name des fehlerhaften Moduls: iplops.dll, Version: 14.0.1798.105, Zeitstempel: 0x4fa3de38
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000068193
ID des fehlerhaften Prozesses: 0x900
Startzeit der fehlerhaften Anwendung: 0x01cd3ff8ff74b546
Pfad der fehlerhaften Anwendung: D:\Program Files\Symantec\Backup Exec\beserver.exe
Pfad des fehlerhaften Moduls: D:\Program Files\Symantec\Backup Exec\iplops.dll
Berichtskennung: baff6e56-ac56-11e1-bf3c-005056ac000e
 

Another thing I found out - if the service is running in the night, it always stops around 4am...at least the last three days it did with the same error messages (.NET and application). It additionally stopped Saturday while running backups.

 

EliasA
Moderator
Moderator
Employee CPEP

Bembel, after installation of SP1 did you reboot the media servers?  In addition, as we continue to investigate this issue, following the advice of DieGoettlichen above, did you try to turn a repaire on the software to see if that clears up the issue?

 

Bembel
Level 3

Dear Elilas,

the machine was rebooted on Saturday evening after I found out that something strange was going on. Furthermore I did not try to repair anything since I have an open case at Symantec and did not want to interfere with their work - and the possibility to contribute to a possible general solution for this incident.

Actually I set the Backup Exec service to automatically restart which it did tonight as it crashed again around 4am and was successfully started afterwards (no active backup job at that time).

Cheers!

ronnysteiner
Not applicable

I got the same issue as described here:

Name der fehlerhaften Anwendung: beserver.exe, Version: 14.0.1798.105, Zeitstempel: 0x4fa3de95

Name des fehlerhaften Moduls: beserver.exe, Version: 14.0.1798.105, Zeitstempel: 0x4fa3de95

Ausnahmecode: 0xc0000005

Fehleroffset: 0x00000000003844ec

ID des fehlerhaften Prozesses: 0x1888

Startzeit der fehlerhaften Anwendung: 0x01cd42ee0197a9f1

Pfad der fehlerhaften Anwendung: C:\Program Files\Symantec\Backup Exec\beserver.exe

Pfad des fehlerhaften Moduls: C:\Program Files\Symantec\Backup Exec\beserver.exe

Berichtskennung: 46cae1e2-aee1-11e1-ab48-e61f13aa23e3

here is the .NET error:

Application: beserver.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: exception code c0000005, exception address 00000000012144EC

I tried the following:

repair installation (after applying SP1)

disabling AV software

removing/adding .NET Framework 4

Now I'm trying to remove SP1 and look if it works afterwards.

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...this seems to be a common problem at the moment. Uninstall it, and try installing manually (if you downloaded and installed through LiveUpdate), or vice versa. If it still doesn't work, uninstall it and also check the Known Issues section to see if this is listed there. If so, vote it up...

EliasA
Moderator
Moderator
Employee CPEP

Thanks for the note Bembel (and anyone else encountering this error with SP1) - Please feel free to send me a DM with your email address, so that I can send you an email as soon as we have the fix for this issue some users are encountering.

dkapell_hcc
Level 3

we are also having this problem on a brand new server with a fresh install of BE 2012 sp1.

HNeumann
Level 4

Hi,

we are having exact the same error. I´ll try a repair installation. When it´s done, I'll be in touch.

HNeumann
Level 4

Hallo,

repair installation fixed the problem for me. The Hyper-V job runs without errors.

tomsch
Not applicable

 

Anwendung: beserver.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: Ausnahmecode c0000005, Ausnahmeadresse 0000000000FD45EC
 
SP1 deinstalled
Repair installation wont work...service doesnt start
 

HNeumann
Level 4

After repair installation the Server runs in trial mode, you have to apply al the License files again :( Very annoying...

Sush---
Level 6
Employee Accredited Certified

Check this technote which has a workaround for the issue if the crash is on iplops.dll :

http://www.symantec.com/docs/TECH190472 : Backup Exec server service crashes 4 AM after installing Backup Exec 2012 Service Pack 1

 

Thanks,

-Sush...