Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

BE 2012 login errors with Windows SQL 2008 R2

Created: 19 Nov 2012 • Updated: 21 Nov 2012 | 3 comments

I am trying to backup a SQL 2008 R2 server with BE for Windows 2012.  The backup fails because the login failure below.   Any else able to backup a SQL 2008 R2 database server?

Log Name:      Application
Source:        Backup Exec
Date:          11/19/2012 1:03:55 PM
Event ID:      57860
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GTBST851.rodgers.inc
Description:
An error occurred while attempting to log in to the following server: "gtbst851.rodgers.inc\MSSQLSERVER".
 SQL error number: "4818".
 SQL error message: "Login failed for user 'RODGER-1\backupagent'.
".

 For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Backup Exec" />
    <EventID Qualifiers="8192">57860</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-11-19T18:03:55.000000000Z" />
    <EventRecordID>4835</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GTBST851.rodgers.inc</Computer>
    <Security />
  </System>
  <EventData>
    <Data>gtbst851.rodgers.inc\MSSQLSERVER</Data>
    <Data>4818</Data>
    <Data>Login failed for user 'RODGER-1\backupagent'.
</Data>
    <Binary>18480000000000000000000000000000</Binary>
  </EventData>
</Event>

Comments 3 CommentsJump to latest comment

Donald Eady's picture

Verify that the service account has the appropriate rights 

http://www.symantec.com/docs/TECH184449

 
additionally you may want to manage the system logon accounts and change the password and just reenter the password to verify that it was not previously mistyped.
 

I hope this posting was helpful

  

pkh's picture

Try renaming your  bedssql2.dll file to bedssql2.old. See this article

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

VJware's picture

Renaming the dll would effectively disable the usage of the Agent for SQL..

Pls ensure then account used by Backup Exec has sysadmin privileges...and dbdatareader, dbdatawriter is present under user mapping for those databases as well...Give full permissions to the Backup exec account to the SQl registry key on the SQL server as well.