Backup Exec Server service fails to start or hangs and generates "Error 1067: The process terminated unexpectedly" or "Error 1053: the service did not respond in a timely fashion."

  • Article ID:100023093
  • Modified Date:
  • Product(s):


Backup Exec Server service fails to start and generates "Error 1067: The process terminated unexpectedly" or hangs and generates

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

Error Message

When attempting to start the BE Server service from the Windows services console:


Event ID Error occured-

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Faulting application beserver.exe, version 11.0.7170.32, faulting module beserver.exe, version  11.0.7170.32, fault address 0x00111c57.



 This issue may occur if "msgq0000000000.dat" file is corrupt.



1. Open Windows Explorer and browse to X:\Program Files\veritas\Backup Exec\Data\ (where X: stands for  the drive letter on which Backup Exec for Windows is installed)

2. Locate a file named " msgq0000000000.dat"

3. Stop all Backup Exec Services

4. Rename the above file to " msgq0000000000.old" (or any other name)

5. Attempt to start the Backup Exec Services and verify the Backup Exec Server service starts.

Explanation :
The msgq0000000000.dat is mainly used by Backup Exec Server service in CAS/MMS environment to pass on messages from the CAS to the MMS. The Backup Exec Server service checks this file while starting. If the file  is corrupt, the Backup Exec Server service will fail to start. If the file is not present in the Data folder or if it is renamed, Backup Exec will re-create the file automatically.



Was this content helpful?

Get Support