none
Sql Server 2008 logs Authentication mode incorrectly avoids remote login

    Question

  • Im trying to connect SQL server 2008 Express R2 installed on XP sp3 pc through ODBC SQL Server driver with a Windows 7 PC. I managed to define static IP ports and setup firewall. Now the ODBC connection successfully gets created by accepting uid : sa and my password given.

    Now Im getting "login failed for user ". " msg from my application. When I run the same application with same ODBC connection created in the SQL server PC it works fine. The two pcs operate in a workgroup.

    Following  is the error log. Im surprised to note that the server logs its in Mixed mode initially and later makes a cry that its in Windows Authentication mode. !!!!

    010-07-25 15:19:53.76 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86)
        Apr  2 2010 15:53:02
        Copyright (c) Microsoft Corporation
        Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 3, v.3311)

    2010-07-25 15:19:53.76 Server      (c) Microsoft Corporation.
    2010-07-25 15:19:53.76 Server      All rights reserved.
    2010-07-25 15:19:53.76 Server      Server process ID is 3552.
    2010-07-25 15:19:53.76 Server      Authentication mode is MIXED.
    2010-07-25 15:19:53.76 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
    2010-07-25 15:19:53.76 Server      This instance of SQL Server last reported using a process ID of 1848 at 7/25/2010 3:19:52 PM (local) 7/25/2010 9:49:52 AM (UTC). This is an informational message only; no user action is required.
    2010-07-25 15:19:53.76 Server      Registry startup parameters:
         -d c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\master.mdf
         -e c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG
         -l c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
    2010-07-25 15:19:53.78 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2010-07-25 15:19:53.78 Server      Detected 2 CPUs. This is an informational message; no user action is required.
    2010-07-25 15:19:54.19 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.
    2010-07-25 15:19:54.28 Server      Node configuration: node 0: CPU mask: 0x00000003:0 Active CPU mask: 0x00000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2010-07-25 15:19:54.31 spid7s      Starting up database 'master'.
    2010-07-25 15:19:54.42 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2010-07-25 15:19:54.62 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
    2010-07-25 15:19:54.68 spid7s      SQL Trace ID 1 was started by login "sa".
    2010-07-25 15:19:54.68 spid7s      SQL Trace ID 2 was started by login "sa".
    2010-07-25 15:19:54.68 spid7s      Starting up database 'mssqlsystemresource'.
    2010-07-25 15:19:54.73 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
    2010-07-25 15:19:55.10 spid10s     Starting up database 'model'.
    2010-07-25 15:19:55.11 spid7s      Server name is 'LION\SQLEXPRESS'. This is an informational message only. No user action is required.
    2010-07-25 15:19:55.12 spid7s      Informational: No full-text supported languages found.
    2010-07-25 15:19:55.12 spid7s      Starting up database 'msdb'.
    2010-07-25 15:19:55.52 Server      A self-generated certificate was successfully loaded for encryption.
    2010-07-25 15:19:55.53 Server      Server is listening on [ 'any' <ipv4> 1433].
    2010-07-25 15:19:55.53 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
    2010-07-25 15:19:55.53 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
    2010-07-25 15:19:55.53 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
    2010-07-25 15:19:55.54 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. 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.
    2010-07-25 15:19:55.54 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2010-07-25 15:19:55.55 spid10s     Clearing tempdb database.
    2010-07-25 15:19:56.82 spid10s     Starting up database 'tempdb'.
    2010-07-25 15:19:56.91 spid13s     The Service Broker protocol transport is disabled or not configured.
    2010-07-25 15:19:56.91 spid13s     The Database Mirroring protocol transport is disabled or not configured.
    2010-07-25 15:19:56.93 spid13s     Service Broker manager has started.
    2010-07-25 15:19:56.93 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2010-07-25 15:22:22.93 Logon       Error: 18456, Severity: 14, State: 58.
    2010-07-25 15:22:22.93 Logon       Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.1.8]
    2010-07-25 15:22:33.48 Logon       Error: 18456, Severity: 14, State: 58.
    2010-07-25 15:22:33.48 Logon       Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.1.8]
    2010-07-25 15:23:34.73 Logon       Login succeeded for user 'sa'. Connection made using SQL Server authentication. [CLIENT: 192.168.1.8]
    2010-07-25 15:23:35.51 spid51      Starting up database 'UltraQ_DB'.
    2010-07-25 15:23:35.70 spid51      Starting up database 'UltraDB'.
    2010-07-25 15:23:39.01 Logon       Login succeeded for user 'sa'. Connection made using SQL Server authentication. [CLIENT: 192.168.1.8]
    2010-07-25 15:23:48.62 Logon       Error: 18456, Severity: 14, State: 58.
    2010-07-25 15:23:48.62 Logon       Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.1.8]
    2010-07-25 15:25:23.40 Logon       Error: 17806, Severity: 20, State: 14.
    2010-07-25 15:25:23.40 Logon       SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure.  [CLIENT: 192.168.1.2].
    2010-07-25 15:25:23.40 Logon       Error: 18452, Severity: 14, State: 1.
    2010-07-25 15:25:23.40 Logon       Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 192.168.1.2]
    2010-07-25 15:25:42.22 Logon       Login succeeded for user 'sa'. Connection made using SQL Server authentication. [CLIENT: 192.168.1.2]
    2010-07-25 15:26:00.89 Logon       Login succeeded for user 'sa'. Connection made using SQL Server authentication. [CLIENT: 192.168.1.2]
    2010-07-25 15:30:49.85 Logon       Error: 18456, Severity: 14, State: 58.
    2010-07-25 15:30:49.85 Logon       Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.1.2]
    2010-07-25 15:33:17.08 Logon       Error: 18456, Severity: 14, State: 58.
    2010-07-25 15:33:17.08 Logon       Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 192.168.1.2]

    Any help is appreciated. Thanking in advance

    Sunday, July 25, 2010 5:46 PM

All replies