none
HELP - Error: 17187, Severity: 16, State: 1 RRS feed

  • Question

  •  

    Hi,

     

    I've installed SQL Express 2008 edition on a Windows 2003 Standard server with 2 CPU's and 4GB ram. The application using this SQL DB is Altiris Deployment server.

    I'm getting an error message, well several, but this one seems to happen on every reboot and 8 times:-

     

    This is the information from the log file:-

     

    2008-11-19 17:23:37.06 Server      Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
     Jul  9 2008 14:43:34
     Copyright (c) 1988-2008 Microsoft Corporation
     Express Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2)

    2008-11-19 17:23:37.06 Server      (c) 2005 Microsoft Corporation.
    2008-11-19 17:23:37.06 Server      All rights reserved.
    2008-11-19 17:23:37.06 Server      Server process ID is 1340.
    2008-11-19 17:23:37.06 Server      Authentication mode is WINDOWS-ONLY.
    2008-11-19 17:23:37.06 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2008-11-19 17:23:37.06 Server      This instance of SQL Server last reported using a process ID of 1348 at 19/11/2008 17:21:48 (local) 19/11/2008 17:21:48 (UTC). This is an informational message only; no user action is required.
    2008-11-19 17:23:37.06 Server      Registry startup parameters:
      -d c:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
      -e c:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
      -l c:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2008-11-19 17:23:37.09 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2008-11-19 17:23:37.09 Server      Detected 2 CPUs. This is an informational message; no user action is required.
    2008-11-19 17:23:37.29 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-11-19 17:23:37.35 Server      Node configuration: node 0: CPU mask: 0x00000001 Active CPU mask: 0x00000001. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2008-11-19 17:23:37.53 spid7s      Starting up database 'master'.
    2008-11-19 17:23:37.60 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2008-11-19 17:23:37.70 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2008-11-19 17:23:37.76 spid7s      SQL Trace ID 1 was started by login "sa".
    2008-11-19 17:23:37.81 spid7s      Starting up database 'mssqlsystemresource'.
    2008-11-19 17:23:37.81 spid7s      The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
    2008-11-19 17:23:38.17 spid10s     Starting up database 'model'.
    2008-11-19 17:23:38.17 spid7s      Server name is 'win2k3-ALTRIS197'. This is an informational message only. No user action is required.
    2008-11-19 17:23:38.17 spid7s      Informational: No full-text supported languages found.
    2008-11-19 17:23:38.21 Server      A self-generated certificate was successfully loaded for encryption.
    2008-11-19 17:23:38.23 Server      Server is listening on [ 'any' <ipv4> 1433].
    2008-11-19 17:23:38.23 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2008-11-19 17:23:38.23 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
    2008-11-19 17:23:38.23 spid7s      Starting up database 'msdb'.
    2008-11-19 17:23:38.23 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.
    2008-11-19 17:23:38.28 spid10s     Clearing tempdb database.
    2008-11-19 17:23:38.40 spid10s     Starting up database 'tempdb'.
    2008-11-19 17:23:38.43 spid13s     The Service Broker protocol transport is disabled or not configured.
    2008-11-19 17:23:38.43 spid13s     The Database Mirroring protocol transport is disabled or not configured.
    2008-11-19 17:23:38.46 spid13s     Service Broker manager has started.
    2008-11-19 17:23:38.46 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2008-11-19 17:23:38.71 Logon       Error: 17187, Severity: 16, State: 1.
    2008-11-19 17:23:38.71 Logon       SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 192.168.75.53]
    2008-11-19 17:23:38.71 Logon       Error: 17187, Severity: 16, State: 1.
    2008-11-19 17:23:38.71 Logon       SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 192.168.75.53]
    2008-11-19 17:23:38.71 Logon       Error: 17187, Severity: 16, State: 1.
    2008-11-19 17:23:38.71 Logon       SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 192.168.75.53]
    2008-11-19 17:23:38.73 Logon       Error: 17187, Severity: 16, State: 1.
    2008-11-19 17:23:38.73 Logon       SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 192.168.75.53]
    2008-11-19 17:23:38.73 Logon       Error: 17187, Severity: 16, State: 1.
    2008-11-19 17:23:38.73 Logon       SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 192.168.75.53]
    2008-11-19 17:23:38.73 Logon       Error: 17187, Severity: 16, State: 1.
    2008-11-19 17:23:38.73 Logon       SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 192.168.75.53]
    2008-11-19 17:23:39.73 Logon       Error: 17187, Severity: 16, State: 1.
    2008-11-19 17:23:39.73 Logon       SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 192.168.75.53]
    2008-11-19 17:23:39.75 Logon       Error: 17187, Severity: 16, State: 1.
    2008-11-19 17:23:39.75 Logon       SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 192.168.75.53]
    2008-11-19 17:23:40.23 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/win2k3-altris197.win2k3dir.com ] for the SQL Server service.
    2008-11-19 17:23:40.23 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/win2k3-altris197.win2k3dir.com:1433 ] for the SQL Server service.
    2008-11-19 17:23:40.23 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2008-11-19 17:23:40.96 spid51      Starting up database 'eXpress'.
    2008-11-19 17:23:41.04 spid51      Recovery is writing a checkpoint in database 'eXpress' (5). This is an informational message only. No user action is required.
    2008-11-19 17:23:41.29 spid51      Setting database option RECURSIVE_TRIGGERS to ON for database eXpress.

     

    Has anyone got any ideas?

     

    Thanks

    S

     

    Wednesday, November 19, 2008 10:07 PM

All replies

  • I think it just means that some client application is trying to access your SQL Server BEFORE it's completely ready.

     

    Thanks,

    Varsham

     

    Thursday, November 20, 2008 6:12 AM
  • Hello,

     

    Altiris Deployment Solution needs a Sql Server 2000 at least.

    Varsham is very clever : Altiris needs that the Sql Server instance is started, but starts before Sql Server .

    The solution : to modify the start-up so that Altiris begins to start after Server Server

    I have no idea to do that especially if the computer is a Dell or HP

    You should contact the provider of your computer

     

    Have a nice day

     

    Thursday, November 20, 2008 10:08 PM
    Moderator