Video Screencast Help

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

Created: 26 Jul 2007 • Updated: 21 May 2010 | 2 comments
Hi,
 
We have multiple clients running Windows SBS 2003 along with Symantec Backup Exec 11d for SBS. They are all seeing the following error message:
 
Backup is successful, however is reporting the following error

Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 57860
Date: 18/07/2007
Time: 11:11:08 PM
User: N/A
Computer: <withheld>
Description:
An error occurred while attempting to log in to the following server: "<withheld>".
 SQL error number: "0011".
 SQL error message: "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
".

 For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
Data:
0000: 11 00 00 00 00 00 00 00   ........
0008: 00 00 00 00 00 00 00 00   ........
 
This appears to be happening on revsions 6235 & 7170 which have been fully patched via Liveupdate. This only appears to occur where they client is running an SQL server.
 
Can you please advise if there is a resolution to this fault or it it just has to be ignored?
 
Mnay Thnaks,
 
Chris Larsen

Comments 2 CommentsJump to latest comment

Lou Buffetta's picture
Hi Shane
 
This TechNote covers the error if you are not backing up SQL on the remote SBS servers.
 
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.
http://seer.entsupport.symantec.com/docs/264616.htm
 
NOTE: This doc cites version 10d and gives the old program location.
     Use these locations instead
       Backup Exec Server - C:\Program Files\Symantec\Backup Exec
       Remote Server - C:\Program Files\Symantec\Backup Exec\RAWS
 
If you are backing up SQL on these remote servers, it may be an authentication issue.
 
This error occurs when the credentials used by a backup or restore job have insufficient rights to the SQL Server being backed up or restored.  Logon accounts are assigned in selection lists and used by jobs.  One logon account is always assigned in a selection list for attaching to the Windows server, and an optional logon account can be assigned for the SQL Server selection on that Windows server.
 
If using SQL integrated security to perform an SQL backup or restore, the logon account assigned to the Windows server needs to have rights to back up or restore the SQL Server.  No logon account should be assigned to the SQL Server selection in this case.
 
If using SQL security, a logon account with administrator privileges needs to be assigned to the Windows server selection, and a logon account with SQL credentials needs to be assigned the SQL selection.
shane Scanlon's picture
Hi,
 
I have checked that the service account being used has Full Server Administration rights under SQL, as well as being the DB owners and we are still seeing the following:
 
An error occurred while attempting to log in to the following server: "<withheld>".
 SQL error number: "0011".
 SQL error message: "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
 
This appears 2 - 3 times at the start of the backup job but them stops and the SQL component of the backup is reporting as being successful.
 
 
I have also confirmed all Rescource Credentials via the Backup Exec Console.
 
Thanks,
 
Chris