FIX: Event ID: 57860 “An error occurred while attempting to log in to the following server… SQL error number: “0011” is seen when backing up a server with SQL installed

Exact Error Message

Event ID: 57860 Source: Backup Exec Type: Error Description: An error occurred while attempting to log in to the following server: “SERVERNAME”. SQL error number: “0011”. SQL error message: “[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
 
Details:
 
This error will occur when performing any type of backup on a server running Microsoft SQL Server or Microsoft SQL Server Desktop Engine (MSDE), even if the SQL Agent Backup is not being performed. “bedssql2.dll” will always be initialized and loaded on every server that is running the “Backup Exec Remote Agent Service ” whether the SQL agent and license is installed or not.
 
Cause:
 
One or more SQL Databases are corrupted on the remote machine, or the SQL database no longer exists on the remote machine.

Workaround:

Perform the following to resolve this issue:

1. On the SQL server, stop the Backup Exec Remote Agent Service from Windows Control Panel > Services.

2. If SQL is installed on the media server (i.e. if SQL is on the same machine as Backup Exec), within Windows Explorer browse to the installation directory for Backup Exec, which by default is:

\Program Files\VERITAS\Backup Exec\NT

for Backup Exec version 11d and above, the default location is 

\Program Files\Symantec\Backup Exec\
 
If SQL is installed on a remote server, browse to the installation directory for the Remote Agent:

\Program Files\VERITAS\Backup Exec\RANT

for 11d and above:

\Program Files\Symantec\Backup Exec\RAWS

3. Rename the bedssql2.dll file to bedssql2.old

4. Start the Backup Exec services

If the SQL/MSDE is installed on a Remote Server:

1. Stop Remote Agent service on the remote server.
2. Rename the bedssql2.dll file to bedssql2.old on the remote server.
3. Start the Remote Agent service.
4. Re-Start the Backup Exec services on the media server.
5. Run the Backup job and check the result.

WARNING:  Renaming the bedssql2.dll will effectively disable the SQL agent on the server it is renamed upon.  If the SQL agent is purchased in the future, the issue with the corrupt database(s) must be resolved first, and backup of the SQL servers on which the bedssql2.dll was changed is desired – the bedssql2.old file MUST be renamed back to bedssql2.dll. 

Leave a Reply

Your email address will not be published. Required fields are marked *