Backup Exec Server Service fails to start with an Error 1053

Article:TECH74665  |  Created: 2009-01-19  |  Updated: 2012-10-24  |  Article URL http://www.symantec.com/docs/TECH74665
Article Type
Technical Solution

Product(s)

Issue



Could not start the Backup Exec Server service on local computer.
 


Error



Error 1053: The service did not respond to the start or control request in a timely fashion.


Cause



When the beserver -console command is executed: 
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: "The application or DLL C:\Program Files\Symantec\Backup Exec\BeSQL.dll is not a valid windows image. Please check this against your installation diskette"
 
 
 
4. This issue occurs as the BeSQL.dll file is corrupted at the source installation directory C:\Program Files\Symantec\Backup Exec and does not allow the Server Service to start.

5. You may confirm this by right clicking the BeSQL.dll file and selecting properties. Notice that there is no "Version" Tab for this file which means it is corrupted.

Solution



There are two methods to resolve this issue:
 
METHOD-1:
 
Run Repair install of Backup Exec from Add or Remove Program which will fix missing or corrupt files, shortcuts, and registry entries.
 
NOTE:- This will require the Backup Exec Installation source. If it is already available on the media server, repair installation will continue, else it will prompt to browse through the location to provide the installation source. If you have it over the network, you may select that location but if you do not have the installation source, you need to either download it online and then continue or follow METHOD - 2.
 
METHOD-2:
 
1. Browse through C:\Program Files\Symantec\Backup Exec on the Media server in question.
 
2. Rename the BeSQL.dll to BeSQL.dll.old
 
3. Connect to any other media server in the network with same Backup Exec Version and at same patch level.
 
4. Browse through default installation location for Backup Exec (C:\Program Files\Symantec\Backup Exec)
 
5. Copy the BeSQL.dll file from that location
 
6. Paste this file at C:\Program Files\Symantec\Backup Exec on the Media server in question.
 
7. Now try starting the Backup Exec Server Service and it should start successfully
 
OR
 
1. Browse through C:\Program Files\Symantec\Backup Exec on the Media server in question.
 
2. Rename the BeSQL.dll to BeSQL.dll.old
 
3. Connect to any remote server in the network where Remote Agent for Windows Server is installed with same Backup Exec Version and at same patch level.
 
4. Browse through default installation location for RAWS (Default: C:\Program Files\Symantec\Backup Exec\RAWS)
 
5. Copy the BeSQL.dll file from that location
 
6. Paste this file at C:\Program Files\Symantec\Backup Exec on the Media server in question.
 
7. Now try starting the Backup Exec Server Service and it should start successfully
 
Additional Steps:
 
-Check whether the Remote agent service is running or not.
-If it is stopped then try to start it
-If it doesn't start then check the event viewer
-configure the NDMP port properly and make sure it is listening.
-configure the NDMP port in the hosts file in windows directory
-Telnet or use the Netstat command.
-Start the Remote agent service and then the Server service will start

Supplemental Materials

SourceError Code
Value1053
Description

The service did not respond to the start or control request in a timely fashion



Legacy ID



332254


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


Terms of use for this information are found in Legal Notices