Not able to connect SQLServer 2008 using windows athentication

  • Dear All,

    Iam not able to connect SQLServer 2008 [in windowserver 2008 (64 Bit O/s)] using windows athentication.

    Even, I don't have SA password to connect to check the issue.When I checked in the SQLServer Log I have found the below error.

    ERROR:18456, Severity: 14, State: 11.

    Login failed for user 'PULSE\Infrastructure'. Reason: Token-based server access validation failed

    with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]

    Can someone please advice how I can comeout from this issue?

    Your quick response is much appreciated.

    Thanks and Regards,

    Ravi.

  • What is your defaut Database?

    Check out this article:

    http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • Thanks.

    But when Iam trying the below link to run ssms.exe in windowserver 2008 facing the below warning.

    "http://sqlserverpedia.com/blog/sql-server-bloggers/connect-to-sql-server-as-nt-authoritysystem/"

    Warning: Due to security enhancements, this task will run at the time expected but not interactively.

    Please advice how to run the in CMD " c:\>at 23:00 /interactive "C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\ssms.exe"

    Thanks and Regards,

    Ravi.

  • Can someone please advise? as this is a production server.

    You rapid reply is much appreciated.

    Thanks and Regards,

    Ravi.

  • State 11 means the domain login trying to access sql server that wasnt explicitly added to sql server .Even though it can access OS, it cant login in to sql server. To overcome this error, you can add that domain login to sql logins explicitly provided you have create login permission.

    Thank You,

    Best Regards,

    SQLBuddy

  • Start cmd as [RUN as Administrator] then execute it

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

Viewing 6 posts - 1 through 5 (of 5 total)

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