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.

Article:TECH29539  |  Created: 2003-01-10  |  Updated: 2013-03-15  |  Article URL http://www.symantec.com/docs/TECH29539
Article Type
Technical Solution

Product(s)

Issue



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.


Error



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.

In some Backup Exec version, also observed the following issue and error similar to this:

Backups fail with an error "V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine". Beremote.exe application errors on module bedssql2.dll

V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine.
The media server will use the local agent to try to complete the operation. Unable to initialize Remote Agent.

Event ID: 57860 "An error occurred while attempting to log in to the following server //XXXX. SQL error number: "0011"" is seen when backing up a server with SQL installed.

Error Signature

szAppName : beremote.exe  szAppVer : 12.5.2213.175

szModName : bedssql2.dll  szModVer : 12.5.2213.175  offset : 0002fee7


Cause



 
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. 

Or 
 
One or more SQL Databases are corrupted on the remote machine.

Solution




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 (Figure 1)

for 11d and above :
 
\Program Files\Symantec\Backup Exec\
 
Figure 1
 

If SQL is installed on a remote server, browse to the installation directory for the Remote Agent:

\Program Files\VERITAS\Backup Exec\RANT (Figure 2)

for 11d and above:

\Program Files\Symantec\Backup Exec\RAWS

Figure 2
 

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. Restart 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.

Supplemental Materials

Value57860
Description

An error occurred while attempting to log into the following server... SQL error number "0011"


Value11
Description

SQL error number: "0011"



Legacy ID



264616


Article URL http://www.symantec.com/docs/TECH29539


Terms of use for this information are found in Legal Notices