Forum Discussion

Michael68's avatar
Michael68
Level 4
13 years ago

BackupExec 2010 R3 beserver.exe stops with 0xe06d7363 . Database login timeout

Hello.

 

I am running BackupExec 2010 R3 Ver. 13 Rev 5204 on W2008 R2 64-bit. While the backup job is running I got the following error. Afterwards the BackupExec service is not running.

 

INFORMATION:

Log Name:      Application
Source:        Backup Exec
Date:          14.02.2012 00:00:35
Event ID:      57345
Task Category: (65535)
Level:         Information
Keywords:      Classic
User:          N/A
Computer:     
Description:
Database Exception Context:BENEDB::CreateCmd Error:-536837662: :: -2147467259:Login timeout expired :: DB Error Set 0: native=0xffffffff source=Microsoft OLE DB Provider for SQL Server hr=0x80004005 Login timeout expired

 For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Backup Exec" />
    <EventID Qualifiers="8192">57345</EventID>
    <Level>4</Level>
    <Task>65535</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-02-13T23:00:35.000000000Z" />
    <EventRecordID>13170</EventRecordID>
    <Channel>Application</Channel>
    <Computer></Computer>
    <Security />
  </System>
  <EventData>
    <Data>Database Exception Context:BENEDB::CreateCmd Error:-536837662: :: -2147467259:Login timeout expired :: DB Error Set 0: native=0xffffffff source=Microsoft OLE DB Provider for SQL Server hr=0x80004005 Login timeout expired</Data>
  </EventData>
</Event>

 

ERROR:

Log Name:      Application
Source:        Application Error
Date:          14.02.2012 00:00:37
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     
Description:
Faulting application name: beserver.exe, version: 13.0.5204.122, time stamp: 0x4eecd23b
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c
Exception code: 0xe06d7363
Fault offset: 0x000000000000cacd
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
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-02-13T23:00:37.000000000Z" />
    <EventRecordID>13172</EventRecordID>
    <Channel>Application</Channel>
    <Computer></Computer>
    <Security />
  </System>
  <EventData>
    <Data>beserver.exe</Data>
    <Data>13.0.5204.122</Data>
    <Data>4eecd23b</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.17651</Data>
    <Data>4e21213c</Data>
    <Data>e06d7363</Data>
    <Data>000000000000cacd</Data>
  </EventData>
</Event>

 

The backup job is then stopped with

Job ended: Dienstag, 14. Februar 2012 at 04:28:08
Completed status: Failed
Final error: 0xe0008821 - Job was recovered as a result of Backup Exec RPC service starting.  No user action is required.
Final error category: Job Errors

For additional information regarding this error refer to link V-79-57344-34849

I have made a "Check database consistency" and got "Starting database utility operation.
Performing database consistency check for BEDB database.
Database utility for server completed." So I did not a recover of the database yet, which I found as a suggested solution.

 

Thanks for help,

Michael

 

  • Hi,

     

    get hold of the latest SP for BE 2010 R3 and install this. Push-install the updates to any remote servers.

    Once done, check and make sure that the SQL maintenance task isn't running at the same time as your current backup job...could be a reason for it timing out. You can also check and make sure your AV isn't perhaps blocking the SQL service for any reason!

     

    Thanks!

4 Replies

  • Hi,

     

    get hold of the latest SP for BE 2010 R3 and install this. Push-install the updates to any remote servers.

    Once done, check and make sure that the SQL maintenance task isn't running at the same time as your current backup job...could be a reason for it timing out. You can also check and make sure your AV isn't perhaps blocking the SQL service for any reason!

     

    Thanks!

  • What is the size of the BEDB grown upto ? Free up space...

    From Tools - Options - Database Maintenance, select delete aged data...clear out job history as well to a certain extent...run the DB maintenance on a regular schedule

  • Hi,

     

    thank you for your suggestions. I will update the system. Where is the SQL maintenance task defined? In the MS SQL Management Studio? I remember that this can not be changed in the SQL Express version.

     

    Thanks,

    Michael