Forum Discussion

PRR's avatar
PRR
Level 3
14 years ago
Solved

Backup Exec Server service stopping automatically.

I am having issues with my Backup Exec and Remote Agent setup.

I have an Windows XP machine with Backup Exec 2010, which connects through a local area network to a Server 2003 (R2) machine which holds the physical removable media, and the Backup Exec Remote Agent package.

Up until recently, and for reasons I can't explain, the Backup Exec 2010 no longer connects to the Media Server on the Server 2003 machine anymore, claiming that the Backup Exec services have stopped. I check the services.msc on the Server 2003 machine, and indeed the Backup Exec Server service is stopped and the services that have this as a dependency (Backup Exec Agent Browser & Backup Exec Job Engine) are also stopped. When trying to start the Backup Exec Server service, I get the following message:

"The Backup Exec Server service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."

Is this by design? I've never noticed this occur before, and it's stopping the Windows XP Backup Exec 2010 client from connecting to the Media Server on the Server 2003 machine as the other services need to run off it.

I have tried a machine reboot, I have tried repairing the Remote Agent install on the Server 2003 machine, I have also reinstalled from fresh, but the problem persists.

Any help would be greatly appreciated.

Thanks.

2010
Backing Up
Backup and Recovery
Backup Exec
Backup Exec (media server only)
  • PRR's avatar
    PRR
    14 years ago

    Hello folks, very sorry for the incredibly late conclusion of this. Have been using a basic BAT copy as a temporary backup onto an ExtHDD. Think it's likely an actual tape drive fault, as it's started throwing up errors, and not loading Media Libraries correctly in Computer Management and so on recently, we're going to get that replaced. Thanks for taking a look into the issue and such, but I'm really starting to think it's a device fault over BackupExec.

    Thanks very-many.

20 Replies

Show More
  • VJware's avatar
    VJware
    Level 6
    14 years ago

    C:\Program Files\Symantec\Backup Exec\RAWS\
    should not be the value for that key...It should simply be C:\Program Files\Symantec\Backup Exec

  • PRR's avatar
    PRR
    Level 3
    14 years ago

    Thanks for the reply, I have amended the key to read 

    C:\Program Files\Symantec\Backup Exec 

    on the Server 2003 machine, and have attempted to restart all the services, but the same issue occurs. It fails to start and I receive the same Application Log errors.

     

    Event ID: 57806
    "The Backup Exec service 'Backup Exec Server' failed to start because it uses a Windows Server account that does not have the following necessary privileges: 
    Create a Token Object 
     
     Ensure that you are logged on with an account that has administrative privileges. Then, click Tools > Backup Exec Services > Services credentials. If you cannot access the Administration Console, on the Connect to Media Server screen, click Services > Services credentials.  Change the service account information so that it has administrative privileges, and then restart the Backup Exec service."
     
    And this immediately after:
     
    Event ID: 57802
    "The Backup Exec Server Service did not start.  An internal error (10) occurred in object 13. "
     
    Thanks for the time spent, so far.
  • VJware's avatar
    VJware
    Level 6
    14 years ago

    Try using a different logon account with all the necessary privileges & make sure it is in the Domain\ID format

  • PRR's avatar
    PRR
    Level 3
    14 years ago

    I have followed the suggestions in regards to running a repair via Add/Remote Programs on the Media Server, and I have also followed the steps in the BEDB repair link, and the problem persists. In the BEUtility, by Database doesn't quite look the same as in the images, mine has a blue icon with a question mark next to it; I'm uncertain of the relevence of this though, it may just be showing as that due to the services not being able to start. Regardess, I've attached a screenshot showing this, just incase it's of use.

  • PRR's avatar
    PRR
    Level 3
    14 years ago

    I have tried multiple different login accounts applied both via services.msc (respecting the Domain\AccountName format) and through the Backup Exec services (making sure the Domain is selected as it's a seperate field) screen. The accounts are both members of the Administrators, and Backup Operators group. Are any other groups or special permissions required?

    Thanks both for the replies so far.

  • VJware's avatar
    VJware
    Level 6
    14 years ago

    These are the requirements - http://www.symantec.com/docs/TECH36718

  • CraigV's avatar
    CraigV
    Moderator
    14 years ago

    ...that shows that the services aren't running.

    If BE is fully patched, are you then on the latest version which is 2010 R3? If not, consider upgrading to that and patching with SP2.

    Also, check and make sure that no firewalls or AVs are blocking access to the server...

  • PRR's avatar
    PRR
    Level 3
    14 years ago

    After taking a look at the above link, and scouting around, I am currently running the support tool (http://www.symantec.com/business/support/index?page=content&id=TECH135126) which has picked up a few various issues (such as older versions of Backup Exec still registering as being installed), so I'll take a look at solving all these in order and then let you know if the problem persists.

    Thanks for the help thus far. Will keep you updated.

  • PRR's avatar
    PRR
    Level 3
    14 years ago

    Hello folks, very sorry for the incredibly late conclusion of this. Have been using a basic BAT copy as a temporary backup onto an ExtHDD. Think it's likely an actual tape drive fault, as it's started throwing up errors, and not loading Media Libraries correctly in Computer Management and so on recently, we're going to get that replaced. Thanks for taking a look into the issue and such, but I'm really starting to think it's a device fault over BackupExec.

    Thanks very-many.