Attempting to start the Backup Exec Server service fails with error message, Error 1053: The service did not respond to the start or control request in a timely fashion.

Article:TECH68533

Created: 2009-01-06

Updated: 2010-09-18

Article URL http://www.symantec.com/docs/TECH68533

Article Type
Technical Solution

Product(s)

Show all

Environment

Show all

Languages

Show all

Problem

Attempting to start the Backup Exec Server service fails with error message, Error 1053: The service did not respond to the start or control request in a timely fashion.

Error

Faulting application beserver.exe, version 12.5.2213.0, stamp 48d0f941, faulting module ntdll.dll, version 5.2.3790.3959, stamp 45d70ad8, debug? 0, fault address 0x0004afb2.

Solution

Event ID:

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 2/24/2009
Time: 10:28:39 AM
User: N/A
Computer: Server
Description:

Faulting application beserver.exe, version 12.5.2213.0, stamp 48d0f941, faulting module ntdll.dll, version 5.2.3790.3959, stamp 45d70ad8, debug? 0, fault address 0x0004afb2

1. On the Backup Exec server, open a command prompt console and change the directory to Backup Exec installation directory. (By default C:\Program Files\Symantec\BackupExec).

2. Run the command:

beserver -console

3. It may flash an error: "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll could not be loaded." The mscorwks.dll is a .NET related binary, so to fix the problem please refer to the solution listed below.

To resolve this issue:

1) a. Perform a Repair Install of .net framework
b. Reboot the Server

OR

2) a. Uninstall .net Framework
b. Reboot the server
c. Reinstall .net Framework

Microsoft .NET Framework Version 2.0 Redistributable Package

http://www.microsoft.com/downloads/details.aspx?familyid=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

After successful installation of .Net Framework all Backup Exec services should start.

Note: If the Backup Exec Services are in hung in a starting mode, use the Windows Task Manager to kill the processes, confirm all the services are stopped, and then restart them. If the processes cannot be ended in Task Manager, set all the Backup Exec Services to manual, reboot the server, and then attempt to start them again. If all the services startup properly, set them back to automatic.