The connection to the Backup Exec database has been lost.

[Carol_Tompkins]

Just recently, we've begun to get the following error message

"The connection to the Backup Exec database has been lost. Make sure
that network cables are properly attached and plugged in, and that
services are running for the SQL Server instance on which the Backup Exec
database is installed"

Also, simultaneously the logon wizard is coming up. No changes have been made to logons or the server recently and it had been working fine prior to this for many months.

Any suggestions??? Thanks.

[Carol_Tompkins]

> Just recently, we've begun to get the following error
> message
>
> "The connection to the Backup Exec database has been
> lost. Make sure
> that network cables are properly attached and plugged
> in, and that
> services are running for the SQL Server instance on
> which the Backup Exec
> database is installed"
>
> Also, simultaneously the logon wizard is coming up.
> No changes have been made to logons or the server
> r recently and it had been working fine prior to this
> for many months.
>
> Any suggestions??? Thanks.

Also, we are running SBS 2000. We are not using the SQL component and haven't been, so nothing has changed recently.

[Deepali_Badave]

Hello,

In the application event viewer are you getting an Event ID: 57796, with the description: Database connection failed?

If so,

To troubleshoot these errors, check the version of MDAC that is installed on the machine.

If MDAC is a version older than MDAC 2.6 SP2, download and install the latest version of MDAC from the Microsoft web site:

http://www.microsoft.com/downloads/search.aspx?displaylang=en

Reboot the server after installing the new MDAC version.

Backup Exec 9.1 for Windows Servers revision 4691 installs MDAC version 2.8.

Please update us on this issue.

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.

[Carol_Tompkins]

No--there was an event ID 57796 but without the description about database connection failed. It just had information, not an error.

We already were running MDAC 2.8, but I updated to 2.8 SP1 and also did all Veritas updaes.

Unfortunately, nothing helped. Any other suggestions are appreciated.

[tejashree_Bhate]

Hello,

We suggest you to perform the following steps:
1. Download and run MDAC component checker from the following link:

http://support.microsoft.com/default.aspx?scid=kb;en-us;307255

2. After downloading the component checker, execute cc.exe.
A dialogue box appears "Component Checker-choose analysis type"

3. Select 'Perform analysis of your machine and automatically determine the release version' and click 'ok'

4. Component Checker comes out with the version of MDAC installed on your system
5. Click 'Yes' when prompted for 'Would you like to re-run query for a specific product release'
6. The "Component Checker-choose analysis type" window appears again
7. Select perform analysis against a specific version
8. From the drop down menu select MDAC 2.8 RTM and click 'ok'

9. A report is generated, showing mismatched fields in the resulting pane.

If there are mismatched fields, then the correct version can be acquired from the Microsoft site or from another system having the correct version.

Please write back if you have further doubts or queries.
Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

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



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.


Thanks.

[TJH]

We just had that same thing happen to one of our servers as well. In this particular case, the DNS entries for that server were incorrect. The services use a domain user login, so since the server wasn't able to verify the user, the connection would drop. Once we changed the DNS settings, and rebooted, it seems to be fixed. You may want to check the user account that the services are using to run.

**EDIT** - just noticed the date of the post. Oops.Message was edited by:
TJH