C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8INSTANCE2\MSSQL\Binn>sqlservr.exe -m -s SQL2K8INSTANCE2
2010-06-01 22:54:47.51 Server Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
Jul 9 2008 14:43:34
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Evaluation Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)
2010-06-01 22:54:47.53 Server Error: 17054, Severity: 16, State: 1.
2010-06-01 22:54:47.53 Server The current event was not reported to the Windows Events log. Operating system error = 1502(Le fichier journal d'événem
ents est plein.). You may need to clear the Windows Events log if it is full.
2010-06-01 22:54:47.53 Server (c) 2005 Microsoft Corporation.
2010-06-01 22:54:47.53 Server All rights reserved.
2010-06-01 22:54:47.53 Server Server process ID is 3692.
2010-06-01 22:54:47.53 Server Authentication mode is MIXED.
2010-06-01 22:54:47.53 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8INSTANCE2\MSSQL\Log\ERRORLOG'.
2010-06-01 22:54:47.53 Server This instance of SQL Server last reported using a process ID of 456 at 01/06/2010 22:54:27 (local) 01/06/2010 20:54:27
(UTC). This is an informational message only; no user action is required.
2010-06-01 22:54:47.54 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8INSTANCE2\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8INSTANCE2\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8INSTANCE2\MSSQL\DATA\mastlog.ldf
2010-06-01 22:54:47.56 Server Command Line Startup Parameters:
-m
-s SQL2K8INSTANCE2
SQL2K8INSTANCE2
2010-06-01 22:54:47.62 Serveur SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-06-01 22:54:47.62 Serveur Detected 2 CPUs. This is an informational message; no user action is required.
2010-06-01 22:54:48.48 Serveur Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2010-06-01 22:54:48.48 Serveur 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-06-01 22:54:48.65 Serveur Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of th
e NUMA configuration for this computer. This is an informational message only. No user action is required.
2010-06-01 22:54:48.68 Serveur Database Mirroring Transport is disabled in the endpoint configuration.
2010-06-01 22:54:48.70 spid7s Warning ******************
2010-06-01 22:54:48.70 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2010-06-01 22:54:48.70 spid7s Starting up database 'master'.
2010-06-01 22:54:49.71 spid7s 716 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is requ
ired.
2010-06-01 22:54:49.73 spid7s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2010-06-01 22:54:49.73 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is req
uired.
2010-06-01 22:54:49.87 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2010-06-01 22:54:49.90 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2010-06-01 22:54:49.90 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQL2K8INSTANCE2'.
2010-06-01 22:54:49.96 spid7s SQL Trace ID 1 was started by login "sa".
2010-06-01 22:54:49.98 spid7s Starting up database 'mssqlsystemresource'.
2010-06-01 22:54:50.01 spid7s The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2010-06-01 22:54:50.28 spid9s Starting up database 'model'.
2010-06-01 22:54:50.28 spid7s Server name is 'DPAW-ZINZINDOHU\SQL2K8INSTANCE2'. This is an informational message only. No user action is required.
2010-06-01 22:54:50.32 spid7s Information*: aucune langue prise en charge en texte intégral n'a été trouvée.
2010-06-01 22:54:50.34 spid10s Starting up database 'msdb'.
2010-06-01 22:54:50.34 spid12s Starting up database 'ReportServer$SQL2K8INSTANCE2'.
2010-06-01 22:54:50.34 spid13s Starting up database 'ReportServer$SQL2K8INSTANCE2TempDB'.
2010-06-01 22:54:50.37 spid14s Starting up database 'distribution'.
2010-06-01 22:54:51.28 Serveur A self-generated certificate was successfully loaded for encryption.
2010-06-01 22:54:51.31 Serveur Server is listening on [ 'any' <ipv4> 1558].
2010-06-01 22:54:51.31 Serveur Server is listening on [ 127.0.0.1 <ipv4> 4848].
2010-06-01 22:54:51.31 Serveur Dedicated admin connection support was established for listening locally on port 4848.
2010-06-01 22:54:51.57 spid16s 1 transactions rolled forward in database 'distribution' (9). This is an informational message only. No user action is
required.
2010-06-01 22:54:51.76 spid9s Clearing tempdb database.
2010-06-01 22:54:51.78 spid7s 0 transactions rolled back in database 'distribution' (9). This is an informational message only. No user action is req
uired.
2010-06-01 22:54:51.78 spid7s Recovery is writing a checkpoint in database 'distribution' (9). This is an informational message only. No user action
is required.
2010-06-01 22:54:51.89 spid15s 1 transactions rolled forward in database 'Logging_demo' (8). This is an informational message only. No user action is
required.
2010-06-01 22:54:51.99 spid14s 1 transactions rolled forward in database 'SNCF_BIS' (7). This is an informational message only. No user action is requ
ired.
2010-06-01 22:54:52.09 spid7s 0 transactions rolled back in database 'Logging_demo' (8). This is an informational message only. No user action is req
uired.
2010-06-01 22:54:52.09 spid7s Recovery is writing a checkpoint in database 'Logging_demo' (8). This is an informational message only. No user action
is required.
2010-06-01 22:54:52.29 spid7s 0 transactions rolled back in database 'SNCF_BIS' (7). This is an informational message only. No user action is require
d.
2010-06-01 22:54:52.29 spid7s Recovery is writing a checkpoint in database 'SNCF_BIS' (7). This is an informational message only. No user action is r
equired.
2010-06-01 22:54:52.48 spid13s 401 transactions rolled forward in database 'ReportServer$SQL2K8INSTANCE2TempDB' (6). This is an informational message
only. No user action is required.
2010-06-01 22:54:52.68 spid7s 0 transactions rolled back in database 'ReportServer$SQL2K8INSTANCE2TempDB' (6). This is an informational message only.
No user action is required.
2010-06-01 22:54:52.68 spid7s Recovery is writing a checkpoint in database 'ReportServer$SQL2K8INSTANCE2TempDB' (6). This is an informational message
only. No user action is required.
2010-06-01 22:54:52.68 spid7s Recovery completed for database ReportServer$SQL2K8INSTANCE2TempDB (database ID 6) in 1 second(s) (analysis 779 ms, red
o 544 ms, undo 165 ms.) This is an informational message only. No user action is required.
2010-06-01 22:54:52.92 spid12s 400 transactions rolled forward in database 'ReportServer$SQL2K8INSTANCE2' (5). This is an informational message only.
No user action is required.
2010-06-01 22:54:52.93 Erreur*: 17187, Gravité*: 16, État*: 1.
2010-06-01 22:54:52.93 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*: 127.0.0.1]
2010-06-01 22:54:52.95 Erreur*: 17187, Gravité*: 16, État*: 1.
2010-06-01 22:54:52.95 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*: 127.0.0.1]
2010-06-01 22:54:52.98 spid7s 0 transactions rolled back in database 'ReportServer$SQL2K8INSTANCE2' (5). This is an informational message only. No us
er action is required.
2010-06-01 22:54:53.01 spid7s Recovery is writing a checkpoint in database 'ReportServer$SQL2K8INSTANCE2' (5). This is an informational message only.
No user action is required.
2010-06-01 22:54:54.23 spid10s 346 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is requir
ed.
2010-06-01 22:54:54.42 spid7s 0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required.
2010-06-01 22:54:54.42 spid7s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is requi
red.
2010-06-01 22:54:54.59 spid7s Recovery completed for database msdb (database ID 4) in 3 second(s) (analysis 1760 ms, redo 1032 ms, undo 187 ms.) This
is an informational message only. No user action is required.
2010-06-01 22:54:55.56 spid9s Starting up database 'tempdb'.
2010-06-01 22:54:55.71 spid7s Recovery is complete. This is an informational message only. No user action is required.
2010-06-01 22:54:55.78 spid7s Launched startup procedure 'sp_MSrepl_startup'.
2010-06-01 22:54:58.04 Erreur*: 17187, Gravité*: 16, État*: 1.
2010-06-01 22:54:58.04 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*: 127.0.0.1]
2010-06-01 22:54:58.04 Erreur*: 17187, Gravité*: 16, État*: 1.
2010-06-01 22:54:58.04 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*: 127.0.0.1]
2010-06-01 22:54:58.23 Serveur 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 informationa
l message. Further action is only required if Kerberos authentication is required by authentication policies.
2010-06-01 22:54:58.23 Serveur SQL Server is now ready for client connections. This is an informational message; no user action is required.
2010-06-01 22:55:08.32 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer$SQL2K8INSTANCE2.
2010-06-01 22:55:08.37 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer$SQL2K8INSTANCE2TempDB.
2010-06-01 22:55:08.39 Erreur*: 17809, Gravité*: 20, État*: 3.
2010-06-01 22:55:08.39 Could not connect because the maximum number of '1' user connections has already been reached. The system administrator
can use sp_configure to increase the maximum value. The connection has been closed. [CLIENT*: 127.0.0.1]
2010-06-01 22:55:08.39 Erreur*: 17809, Gravité*: 20, État*: 3.
2010-06-01 22:55:08.39 Could not connect because the maximum number of '1' user connections has already been reached. The system administrator
can use sp_configure to increase the maximum value. The connection has been closed. [CLIENT*: 127.0.0.1]
2010-06-01 22:55:13.43 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer$SQL2K8INSTANCE2.
2010-06-01 22:55:13.48 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer$SQL2K8INSTANCE2TempDB.
2010-06-01 22:55:13.49 Erreur*: 17809, Gravité*: 20, État*: 3.
2010-06-01 22:55:13.49 Could not connect because the maximum number of '1' user connections has already been reached. The system administrator
can use sp_configure to increase the maximum value. The connection has been closed. [CLIENT*: 127.0.0.1]
2010-06-01 22:55:13.49 Erreur*: 17809, Gravité*: 20, État*: 3.
2010-06-01 22:55:13.49 Could not connect because the maximum number of '1' user connections has already been reached. The system administrator
can use sp_configure to increase the maximum value. The connection has been closed. [CLIENT*: 127.0.0.1]
2010-06-01 22:55:18.54 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer$SQL2K8INSTANCE2.
2010-06-01 22:55:18.59 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer$SQL2K8INSTANCE2TempDB.
2010-06-01 22:55:23.64 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer$SQL2K8INSTANCE2.
2010-06-01 22:55:23.68 spid51 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer$SQL2K8INSTANCE2TempDB.
2010-06-01 22:55:23.70 Erreur*: 17809, Gravité*: 20, État*: 3.
Partager