Forum Discussion

RaviAAG's avatar
RaviAAG
Level 3
12 years ago

'Backup Exec Remote Agent' terminates unexpectedly

This is the information that appears in the Application log of the event viewer.

 
Log Name:           Application
Source:                Application Error
Date:                    29/12/2012 5:38:44 PM
Event ID:              1000
Task Category:     (100)
Level:                   Error
Keywords:            Classic
User:                    N/A
Computer:           SQLServer
 
Description:
Faulting application beremote.exe, version 12.5.2213.144, time stamp 0x4a6f92dd, faulting module bedssql2.dll, version 12.5.2213.133, time stamp 0x49c7f283, exception code 0xc0000005, fault offset 0x000000000003e927, process id 0x48c, application start time 0x01cde1f83afed0e7.
12.x and Earlier
Agents
Backup and Recovery
Backup Exec
Error messages
Remote Agent for Windows Servers
Troubleshooting
  • RaviAAG's avatar
    RaviAAG
    12 years ago

    Hi Gurvinder,

    The workaround we have in place (backup the SQL databases in a separate job from the rest) is working fine for now.

    This issue is now resolved for the time being despite no solution being found. Eventually we will be upgrading to the latest version of Symantec Backup Exec.

    RaviAAG

14 Replies

Sort By
Show More
  • RaviAAG's avatar
    RaviAAG
    Level 3
    12 years ago

    Gurvinder - The System account and domain administrator account has full control of the directory. I was able to install RAWS locally without any issues. How does installing it locally affect the BE software rather than doing a push install? I have attached the beremote dump as well as media server & SQL server remote agent debug.

    pkh - I am running Microsoft SQL Server 2008 (10.0.4067) and Symantec Backup Exec v12.5. I have verified that the version of SQL I am running is supported.

    Craig - I will get back to you within 90 minutes regarding the status.

     

  • RaviAAG's avatar
    RaviAAG
    Level 3
    12 years ago

    Hi Craig,

    Sorry for the late response. I do have a workaround in place for now - I am now doing the SQL server backup separately from the other system backups and I am not experiencing any issues at the moment, however, this workaround is not ideal since I would like to be doing the SQL server backup & other system backups together in one backup job.

    RaviAAG

  • Gurvinder's avatar
    Gurvinder
    Moderator
    12 years ago

    10.0.4067 ? Do you have SP2 on SQL 2008 

    12.5 SCL only has support for 32/64 bit SQL 2008 (does not mention about SP1 or SP2)

    Please refer the SCL - http://www.symantec.com/docs/TECH62301

    And this is the error you are getting on all the databases. Seem we are unable to handle this and crash.

     

    [12184] 01/09/13 10:49:08 SQL2_StartCommand = BACKUP DATABASE [AAG_MAXIMIZER] TO VIRTUAL_DEVICE='BE_SQLAgent-AAG_MAXIMIZER__673add83_b711_4462_a20b_0dccde30219f_' WITH name='Backup Exec SQL Server Agent', SNAPSHOT
    [4228] 01/09/13 10:49:29 SQL2: PrepareForFreeze: SQL command failed before VD transfer
     
    I would recommend an upgrade to 2010 R3 and see if this works there.
  • RaviAAG's avatar
    RaviAAG
    Level 3
    12 years ago

    Hi Gurvinder,

    The workaround we have in place (backup the SQL databases in a separate job from the rest) is working fine for now.

    This issue is now resolved for the time being despite no solution being found. Eventually we will be upgrading to the latest version of Symantec Backup Exec.

    RaviAAG