Veritas v.10.0 stopped working after SP4 installation

[V_V__Chissek]

When I installed Veritas v.10.0 SP4 the program Veritas cannot start because it cannot access the SQL database. When I repaired the Veritas installation from the original CD, the program worked. However, the program would not start with the same original problem after a system reboot. I repaired the installation again. The backup program worked, but again quit working on a reboot.

I've searched the Veritas KB articles and tried anything that is remotely related to this problem but to no avail.

I am running MS Windows Server 2003 SP1. Didn't have any problems until I installed the Veritas Service Pack.

Thanks for help.

[Sharvari_Deshmu]

Hello,

Which version of SQL are you running?

Please try installing the latest BE version;

http://support.veritas.com/docs/279332

SP1 for BE 10d:

Symantec Backup Exec (tm) 10.1 (10d) for Windows Servers revision 5629 - Service Pack 1 - Includes Critical Security Updates

http://support.veritas.com/docs/282818



Thanks,

[V_V__Chissek]

The MS SQL server service manager is version 8.00.760.

I've installed the newer BE version (10d) and the service pack (SP1 for BE10d). BE worked after the installation. However it stopped working again on a reboot.

The following system error was logged after a server restart:

-The Backup Exec Device & Media Service service terminated with the following error:
-The database specified does not exist.

Thanks

[padmaja_rajopad]

Hi,

Is Backup Exec installed on a MSDE instance or a SQl instance?

Test the connection with the Backup Exec database with the help of:

How to perform a quick test connection to the Backup Exec SQL instance

http://support.veritas.com/docs/256661

Also run the MDAC component checker to check whether there are any mismatches.


Please download MDAC Component Checker from here:

"MDAC Utility: Component Checker"
http://www.microsoft.com/downloads/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&DisplayLang=en

Start the "Component Checker".

Select the first Option "Perform analysis of your machine and automatcially determine the release version"

Note down the displayed version.

Select the second option - "Perform analysis against a selected version".

Select the version displayed in the first option.

Check whether there any mismatches.

Regards,
Padmaja

[V_V__Chissek]

Backup Exec is using an MS version of the SQL engine. When I tested the connection, the BEDB database entry was not available. When I ran the BE10.d SP1 update again, the BEDB entry became available. And the connection tested correctly. However the BEDB entry disappeared on reboot and the BE stopped working again.

I ran the MDAC component check and one mismatch was found:

-
-






MSADCO.dll is a more recent version. This mismatch was also found after the BE10d SP1 was reinstalled and BE worked. I ran MDAC 2.8 installer, but didn't see any changes with a Component Checker.

The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ExceptionComponents doesn't contain any values.

Thanks

[Asma_Tamboli]

Hello,

Could you please perform the steps mentioned in the following Document:

http://support.veritas.com/docs/274102

Do update us on the issue!

Thanks!

[V_V__Chissek]

I went through the procedure in this support document and was able to start BE after that. However, the server went back to the same problem after a reboot. Somehow the SQL engine doesn't auto-detect the BE database. My BE installation is in the default location. Is there any environment variable that needs to be set or a registry entry for the MSDE SQL search paths?

[Shilpa_pawar_2]

Hi,

Is backup exec installed in SAN or cluster environment?

What all event ids related to BE or BE services are listed in application and system event log?

Try repairing BE database: http://seer.support.veritas.com/docs/265180.htm

Ensure that MSSQL$BKUPEXEC service is running after reboot and the startup type is set to automatic.

Thanks!

[V_V__Chissek]

No SAN and no cluster configuration is running.

System Log Fail Event IDs are 7001 and 7023.
No Application Log Fail Events are being recorded.
MSQL Server 2000 Application Log Pass Event IDs are 17055, 17176,
Warning Event ID is 19011

MSSQL$BKUPEXEC service autostarts and is running after each reboot.

Repaired the database as described in the document. No errors reported during the repair process. This step did not help: same error (database not found) after a restart.

Thanks

[shweta_rege]

Hello,


Kindly refer the following Document:

Backup Exec for Windows Servers Device and Media Service will not start with the error: "The database specified does not exist."

http://support.veritas.com/docs/267799



Thank You,


Shweta

[V_V__Chissek]

Did that. Please see my July 28 post.

Thanks.

[Gauri_Ketkar]

Hi,

For Windows 2003 Servers perform following steps

1. At Start > Run, type DCOMCNFG, and press Enter.

2. Expand Component Services and then Computers.

3. Right click on My Computer, and choose Properties.

4. Click on the "COM Security" tab (For Windows XP) or the "Default COM Security" tab (For Windows 2003).

5. Click on the "Edit Default" button in the "Access Permissions" section.

6. Add in the account that is specified for the Backup Exec services, along with the System account, and give them "Allow Access" rights.

7. Click OK, and then OK to close the application.

8. Start the Backup Exec services with the user account.

--- Except Remote agent Service and MSSQL$BKUPEXEC,all other BEservices are running under Domain Account and Automatic as startuptype ?


Update us on the same and revert for any further Query
Hope this will help you


Thank you
Gauri

[V_V__Chissek]

I went through these steps, but the other BE services will not start. The Remote Agent Service and the MSSQL$BKUPEXEC service were always starting. The other BE services only start when I attach the BEDB database manually.

Should the Remote Agent Service and MSSQL$BKUPEXEC run under the BE service account or a System account? Should all the other BEservices run under the logged-in domain account or the service account?

I was able to perform the backup after manually attaching the BEDB database and then starting the BE services, but the IDR wizard kept asking me for a user name and a password to connect to a local media server (which is located on the same machine). I do not run any remote backup tasks. After I supplied the user name and the password, the IDR wizard said that the media server was not found.

Thanks

[shweta_rege]

Hello,


Kindly refer the following Document:



http://support.veritas.com/docs/253199




Thank You,

Shweta