Post reply

Sql server logs

  • August 12, 2010 at 9:27 am

    #141526

    I see in the sql server logs, lot of messages every minute

    Message

    Login failed for user 'Server name'. [CLIENT: xxx.xx.xxx.xx](IP Address of the machine)

    It follows with

    Message

    Error: 18456, Severity: 14, State: 16.

    The server on which I am getting these messages is the dev server and the failing user is the production server.

    How can I resolve this?

    Thanks,

    Sushant

    Regards
    Sushant Kumar
    MCTS,MCP

  • August 12, 2010 at 9:37 am

    #1206119

    State 16 means that the user does not have permission to log into their target database.

    Usually happens when the user does not have permission to their default database.

    Check the default database for this user and make sure they have access or change the default database

  • August 12, 2010 at 10:29 am

    #1206182

    @ steve

    The application on server tries to login every 30 sec or so and get faield..

    Is there a possible way to block the connection attempt thru the sql server ?

    Thanks,

    Sushant

    Regards
    Sushant Kumar
    MCTS,MCP

  • August 12, 2010 at 12:19 pm

    #1206264

    You should look at Logon triggers. This was introduced in SQL 2005 SP2 if I am not mistaken.

    -Roy

  • August 12, 2010 at 12:29 pm

    #1206275

    Do you have any linked servers created? To me sounds like credentials are wrong!

  • August 12, 2010 at 1:34 pm

    #1206301

    @roy

    Where could I find Logon triggers?

    @Twinsoft

    There are few linked servers but that server from which the attempts to logon are there , is not added as linked server.

    Regards
    Sushant Kumar
    MCTS,MCP

  • August 12, 2010 at 1:45 pm

    #1206306

    Check this link

    You can rollback a connection attempt using logon triggers.

    -Roy

  • August 24, 2010 at 11:43 am

    #1211193

    any more views?

    Regards
    Sushant Kumar
    MCTS,MCP

Viewing 8 posts - 1 through 7 (of 7 total)

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