Windows eventID 33152

[Steve_Painter_2]

Hi
We just upgrade BE9 to BE10, and the software cannot be started for some reasons.

I checked the event log, and there were countless entries of the below event.

Your help is really appreciated.
Thanks
Steve P.

=======EvenID 33152=======
Adamm Database Error: Driver Connect Failure!
Error = ERROR_DATABASE_DOES_NOT_EXIST
Server = ""
Active Node = ""
Instance = ""
Database = ""
=========================

[Renuka_-]

Hello,
1.Is backup Exec installed in an existing SQL database or in a MSDE instance of its own.
2.Are all BE services started, if not which ones are not, and what is the error recived while starting them.
3.Was the upgrade successfull, please check the last entry in the installation log: bkupinst.log.

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.

[Steve_Painter_2]

Hi

1. I don't know if v9.0 had its own MSDE instance. Maybe you can help verify.

2. Not all BE services started:
-BE Device & Media Service not able to start
-BE Exec Job Engine not able to start
-BE Exec Server not able to start
-The other BE services are started (including MSSQL$BKUPEXEC).

3. Here is the last line of the bkupinst.log:
09-01-2005,06:48:37 : ERROR: Failed to start service - BackupExecDeviceMediaService

This last line seems to be the result when I tried to unintall BE just now and not what happened after the upgrade yesterday.

Anyway, I cannot uninstall BE either. Here is the error:
Error 1402: Could not open key:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\DLO\2.0\AdminConsole. Verify that you have sufficient access to that key, or contact your support personnel.

I ran regedt32 and looked for the key. There is HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS key on the left, but there is nothing on the right (no subkey, no other values - except for one default entry).

In Control Panel | Add Remove Programs, there are 3 entries of BE:
-Veritas Backup Exec for Windows Server
(version 9.0.4454)
-Veritas Backup Exec for Windows Server
(version 10.0.5484)
-Veritas Update
(version 1.0.5484)

None of these can be uninstalled.

Please advise.
Thanks
Steve P.

> Hello,
> 1.Is backup Exec installed in an existing SQL
> database or in a MSDE instance of its own.
> 2.Are all BE services started, if not which ones are
> not, and what is the error recived while starting
> them.
> 3.Was the upgrade successfull, please check the last
> entry in the installation log: bkupinst.log.
>
> NOTE : If we do not receive your reply within two
> business days, this post would be marked assumed
> answeredand would be moved toanswered
> questions pool.

[Deepali_Badave]

Hello,

Perform the repair database an dverify the result.



How to run a Backup Exec database repair when the original Backup Exec database is found to be inconsistent
http://support.veritas.com/docs/265180


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Steve_Painter_2]

Thanks for the tip. The repair process showed the error below.

Starting database repair.
Stopping Services
Starting Services
Database repair for server SERVER ended with errors.


Steve

[Deepali_Badave]

Hello,

change all Backup Exec services to manual and then reboot the machine.
After reboot, start Backup Exec services. This step is for test purpose only.


If the issue persists, please start Beutility and then select "Drop existing database and reload from base". Refer following technote:



http://seer.support.veritas.com/docs/254014.htm


Note: All media sets, backup-2-disk folder, and other settings will have to be created or configured again, if the option Drop existing database and reload from base is selected

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Steve_Painter_2]

Thanks again for the tip.

Nope, it didn't work.

I can't uninstall. I can't install. It's in limbo mode - a real mess.

I removed the server from BEUtility, and now can't connect back to it.

Steve