Post reply

Login failed for user 'Invalid_login_Name'

  • April 29, 2010 at 2:53 am

    #218342

    Hi all,

    I've had a quick search and cant find anything specific to this issue, which although it's not actually causing any errors / failures, still requires resolving.

    I have many linked servers set up on a main SQL Server 2008 instance, the linked servers Source Instances are a mix of SQL 2000 and SQL 2005 on servers located off site. These linked servers have agent jobs which run loaclly and transfer data to the Main SQL 2008 instance.

    The jobs and resulting data transfers are working and completing successfully, however each time a job is run from a linked server Windows Event Viewer Application log and the SQL Server log for the main SQL 2008 target server show "Failure Audit" in Windows log and Source = Login for SQL Server log messages which advise;

    "Login failed for user 'Invalid_Login_Name'. Reason: Could not find a login matching the name provided. [CLIENT: <relevant IP address>].

    Like I say the connections actually do work and the jobs complete successfully and transfer the data but I continue to get these messages each time the jobs run. Baffling me. Any suggestions as to what may be causing this would be greatly appriciated.

    Thanks!

  • April 30, 2010 at 8:00 am

    #1160430

    It Happens usually with orphaned logins.

    Try this:

    use databasename

    sp_change_users_login 'report'

    and check to see if the result of this statement is the login in question.

    you can correct it as follows:

    sp_change_users_login 'update_one','login1','login1'

    Maninder
    www.dbanation.com

  • April 30, 2010 at 8:19 am

    #1160450

    Hi Maninder,

    Thanks for your reply.

    We have recently upgraded the target SQL Server to SQL 2008 which leaves orphaned users as a real possibility. However I've just double checked all DBs, including the system DBs and there are no orphaned users reported.

    The event viewer application logs indicate that its the master DB the issue is with, I tried granting access for the relevant login to master and adding to the public DB role in master. However this hasn't got rid of the messages.

    The sql login obviously has access as the linked server connections work as do the data transfers. Yet I still get this Failure Audit warning.

    regards,

    Ally.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply