locked
Error 18456, Severity: 14, State: 11 on SQL 2005 while connecting to instance from Management studio RRS feed

  • Question

  • I have installed SQL server 2005 on a Vista machine. During setup, I configured SQL server to run Network Service.

    I am trying to connect to the server instance from Management studio but not able to due to above error.

    How do i resolve this> Thanks in advance!

     

    The error log file has following information.

     

    2008-10-08 13:41:25.18 Server      Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
     Oct 14 2005 00:33:37
     Copyright (c) 1988-2005 Microsoft Corporation
     Standard Edition on Windows NT 6.0 (Build 6001: Service Pack 1)

    2008-10-08 13:41:25.18 Server      (c) 2005 Microsoft Corporation.
    2008-10-08 13:41:25.18 Server      All rights reserved.
    2008-10-08 13:41:25.18 Server      Server process ID is 668.
    2008-10-08 13:41:25.18 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
    2008-10-08 13:41:25.18 Server      This instance of SQL Server last reported using a process ID of 1320 at 10/8/2008 1:41:15 PM (local) 10/8/2008 8:41:15 PM (UTC). This is an informational message only; no user action is required.
    2008-10-08 13:41:25.18 Server      Registry startup parameters:
    2008-10-08 13:41:25.18 Server        -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
    2008-10-08 13:41:25.18 Server        -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
    2008-10-08 13:41:25.18 Server        -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
    2008-10-08 13:41:25.20 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2008-10-08 13:41:25.20 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2008-10-08 13:41:25.28 Server      Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
    2008-10-08 13:41:25.39 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2008-10-08 13:41:25.40 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
    2008-10-08 13:41:26.48 Server      Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
    2008-10-08 13:41:26.48 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2008-10-08 13:41:26.48 spid5s      Starting up database 'master'.
    2008-10-08 13:41:26.54 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2008-10-08 13:41:26.62 spid5s      SQL Trace ID 1 was started by login "sa".
    2008-10-08 13:41:26.67 spid5s      Starting up database 'mssqlsystemresource'.
    2008-10-08 13:41:26.92 spid9s      Starting up database 'model'.
    2008-10-08 13:41:26.92 spid5s      Server name is 'WFTESTSRV1'. This is an informational message only. No user action is required.
    2008-10-08 13:41:27.01 spid9s      Clearing tempdb database.
    2008-10-08 13:41:27.17 Server      A self-generated certificate was successfully loaded for encryption.
    2008-10-08 13:41:27.18 Server      Server is listening on [ 'any' <ipv6> 1433].
    2008-10-08 13:41:27.18 Server      Server is listening on [ 'any' <ipv4> 1433].
    2008-10-08 13:41:27.18 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2008-10-08 13:41:27.18 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
    2008-10-08 13:41:27.18 Server      Server is listening on [ ::1 <ipv6> 1434].
    2008-10-08 13:41:27.18 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
    2008-10-08 13:41:27.18 Server      Dedicated admin connection support was established for listening locally on port 1434.
    2008-10-08 13:41:27.24 Server      The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2008-10-08 13:41:27.24 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2008-10-08 13:41:27.24 spid5s      Starting up database 'msdb'.
    2008-10-08 13:41:27.56 spid5s      Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
    2008-10-08 13:41:27.68 spid9s      Starting up database 'tempdb'.
    2008-10-08 13:41:27.81 spid5s      Recovery is complete. This is an informational message only. No user action is required.
    2008-10-08 13:41:27.81 spid12s     The Service Broker protocol transport is disabled or not configured.
    2008-10-08 13:41:27.81 spid12s     The Database Mirroring protocol transport is disabled or not configured.
    2008-10-08 13:41:27.81 spid12s     Service Broker manager has started.
    2008-10-08 13:41:34.22 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2008-10-08 13:41:34.27 spid51      Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2008-10-08 13:41:34.28 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2008-10-08 13:41:35.17 spid51      Using 'xpsqlbot.dll' version '2005.90.1399' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
    2008-10-08 13:41:35.61 spid51      Using 'xpstar90.dll' version '2005.90.1399' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    2008-10-08 13:41:35.65 spid51      Using 'xplog70.dll' version '2005.90.1399' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    2008-10-08 13:42:25.83 Logon       Error: 18456, Severity: 14, State: 11.
    2008-10-08 13:42:25.83 Logon       Login failed for user 'REDMOND\sonalic'. [CLIENT: <local machine>]

    Wednesday, October 8, 2008 8:56 PM

Answers

All replies

  • Found the solution at http://blogs.msdn.com/sql_protocols/archive/2007/06/18/connecting-to-sql-server-2005-on-vista-and-longhorn.aspx

     

    Users can always connect to SQL Server using elevated privileges (run as Administrator), or connect as sa (if Mixed authentication mode was selected during install). Once connected, any user can be granted login privileges or added to the sysadmin fixed server role by executing

     

     

    Wednesday, October 8, 2008 9:06 PM
  • Sonali,

     

    Could you please elaborate your solution to the problem you mentioned earlier ?

     

    I am also getting the following same error meessage

     

    "The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies."

     

    I am using Windows 2008 server with SQL Server 2008. I tried to run the SQL Server service with local account that doesnt work. Then i made that account to local admin, doesnt work either. Then i use the domain user, doesnt work. Then i thought of removing this server from the domain, delete the entry for this server from the AD and then join the server back into the domain. This is make sure that AD issue is not there. this also doesnt solve the prob.

     

     

    Regards

    Prashant Thakwani

     

    Thursday, December 4, 2008 8:34 PM