June 15, 2011 at 3:38 am
2011-06-14 19:09:40.37 server Copyright (C) 1988-2002 Microsoft Corporation.
2011-06-14 19:09:40.37 server All rights reserved.
2011-06-14 19:09:40.37 server Server Process ID is 768.
2011-06-14 19:09:40.37 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2011-06-14 19:09:40.39 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2011-06-14 19:09:40.79 server SQL Server configured for thread mode processing.
2011-06-14 19:09:40.79 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2011-06-14 19:09:40.82 server Attempting to initialize Distributed Transaction Coordinator.
2011-06-14 19:09:40.82 server Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
2011-06-14 19:09:40.82 spid4 Starting up database 'master'.
2011-06-14 19:09:40.95 spid4 Server name is 'SD-PC'.
2011-06-14 19:09:40.95 spid5 Starting up database 'msdb'.
2011-06-14 19:09:40.95 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2011-06-14 19:09:40.95 spid6 Starting up database 'model'.
2011-06-14 19:09:40.95 server SQL server listening on 192.168.1.58: 1433.
2011-06-14 19:09:40.95 server SQL server listening on 127.0.0.1: 1433.
2011-06-14 19:09:40.96 spid8 Starting up database 'pubs'.
2011-06-14 19:09:40.96 spid10 Starting up database 'Northwind'.
2011-06-14 19:09:40.96 server SQL server listening on TCP, Shared Memory, Named Pipes.
2011-06-14 19:09:40.96 server SQL Server is ready for client connections
2011-06-14 19:09:40.98 spid11 Starting up database 'InfinityMasterModel'.
2011-06-14 19:09:40.98 spid12 Starting up database 'InfinityModel'.
2011-06-14 19:09:41.01 spid13 Starting up database 'InfinityMaster'.
2011-06-14 19:09:41.01 spid14 Starting up database 'monolo'.
2011-06-14 19:09:41.06 spid15 Starting up database 'sadepths'.
2011-06-14 19:09:42.28 spid6 Clearing tempdb database.
2011-06-14 19:09:43.39 spid51 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure 'sp_MSgetversion'.
2011-06-14 19:09:45.59 spid6 Starting up database 'tempdb'.
2011-06-14 19:09:46.99 spid4 Recovery complete.
2011-06-14 19:09:46.99 spid4 SQL global counter collection task is created.
2011-06-14 19:09:46.99 spid4 Launched startup procedure 'sp_notifyClients'
2011-06-14 19:09:47.20 spid52 Using 'ClientSocket.dll' version 'UNKNOWN' to execute extended stored procedure 'setclientsockets'.
2011-06-14 19:17:14.45 spid51 Error: 15457, Severity: 0, State: 1
2011-06-14 19:17:14.45 spid51 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2011-06-14 19:17:14.53 spid51 Using 'xplog70.dll' version '2000.80.2039' to execute extended stored procedure 'xp_msver'.
2011-06-14 19:17:20.76 spid51 Error: 15457, Severity: 0, State: 1
2011-06-14 19:17:20.76 spid51 Configuration option 'user connections' changed from 0 to 15. Run the RECONFIGURE statement to install..
What is this error and plz suggest me a solution for this ....plzzz
June 15, 2011 at 4:35 am
What error?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 15, 2011 at 4:38 am
2011-06-14 19:17:14.45 spid51 Error: 15457, Severity: 0, State: 1
2011-06-14 19:17:14.45 spid51 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2011-06-14 19:17:14.53 spid51 Using 'xplog70.dll' version '2000.80.2039' to execute extended stored procedure 'xp_msver'.
2011-06-14 19:17:20.76 spid51 Error: 15457, Severity: 0, State: 1
2011-06-14 19:17:20.76 spid51 Configuration option 'user connections' changed from 0 to 15. Run the RECONFIGURE statement to install.
what's this? how to reconfigure it?
June 15, 2011 at 5:07 am
Those aren't errors. They're just informational messages telling you that configuration options have changed.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 16, 2011 at 5:55 am
"Error" is a generic term in the SQL Server logs. You need to look at the Severity in order to understand if you're reading a true error or an informational message.
Read this page for more information: http://msdn.microsoft.com/en-us/library/aa937483(v=sql.80).aspx
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply