Link to home
Start Free TrialLog in
Avatar of ndidomenico
ndidomenico

asked on

Problem starting the MSSQL$BKUPEXEC service with event id 7022 and 7034

After rebooting following a server crash (power failure), the BackupExec services will not start anymore. Everything else on the server runs fine. After reviewing the event logs, it looks like BE will not start because of a failure when loading the MSSQL$BKUPEXEC service, with the following errors in the event log:

Event ID: 7022
Service Control Manager
The MSSQL$BKUPEXEC service hung on startup

Event ID: 7034
Service Control Manager
The MSSQL$BKUPEXEC service terminated unexpectedly.

Is it a Mdac corruption ? Any idea how to fix this error ?

The server is running Windows Server 2003 SP2.
Backup Exec is v9.1.4691
Mdac is 2.82.3959

Thanks
ASKER CERTIFIED SOLUTION
Avatar of Joseph Daly
Joseph Daly
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It looks like your version of BE is one of the affected ones.
Avatar of ndidomenico
ndidomenico

ASKER

Tried the link but did not work. First, Outlook is not installed on the server, and Outlook Express was already set as the default email client. I tried to switch IE from OE to Hotmail to OE just to reset the setting but without success.

In fact, the two links are related to a different issue, which talks about the "Backup Exec Services hung on starting" while the issue I'm having is about "MSSQL$BKUPEXEC service hung on starting".

Any other ideas ? Mdac re-installation ?

Thanks
Update on the issue:
1) Tried re-installing mdac by doing a right-clic on c:\windows\inf\mdac.inf. Seems to have re-installed the files. Rebooted the server. The mssql$bkupexec service still fails to start.
2) Tried to run mdac_typ.exe v2.8 but setup gives the error "this setup does not support installing on this version of operating system."
Ended up re-installing Backup Exec and re-create the BE databases.

xxdcmast: the solution you provided was for a slightly different problem (BackupExec service instead of mssql$bkupexec), so I couldn't use your solution.