Mar
22
2012

Event ID: 57860 Source: Backup Exec Type Error Description: SQL error number: “4818”. SQL error message: “Login failed for user ‘domain\userid service account’.

While check Windows errors logs, came across these errors, solution is already provided by Symantec; basically this error is recieved when any type of backup is run by Backup exec agent on a server having Microsoft SQL Server installed. Details of issue are as below,

Solution provided by Symantec at following link: http://www.symantec.com/business/support/index?page=content&id=TECH29539


Problem

Event ID: 57860 “An error occurred while attempting to log in to the following server…SQL error number: “4818”. SQL error message: “Login failed for user ‘domain\user service account’.”.


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: “4818”. SQL error message: “Login failed for user ‘domain\user service account’.

OR

Error can be as below,

SQL error number: “0011”. SQL error message: “[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied


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 Pane \ 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.

—————-
Reference: http://www.symantec.com/connect/forums/backupexec-causes-4818-sql-login-event-log-error

Download PDF

Related Posts

About the Author: Nitin Garg

Indian born, trekker, biker, photographer, lover of monsoons... I love to blog the topics I research and find useful for self or online community to save time and energy :) Everything you read on my blog is my own personal opinion!

Leave a comment

Subscribe to this blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 64 other subscribers

Translate this blog!

EnglishFrenchGermanItalianPortugueseRussianSpanish

Calender

May 2018
M T W T F S S
« Nov    
 123456
78910111213
14151617181920
21222324252627
28293031  

View Post by Categories

%d bloggers like this: