When looking at your SQL Server 2000 ERRORLOG file you may see a message similar to the following: 2007-12-25 12:01:30.47 spidxx Error: 15457, Severity: 0, State: 1. This error is usually followed with the additional message: 2007-12-25 12:01:30.47 spidxx Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install. You may also see the message(s) in the SQL Enterprise Manager > Management > SQL Server Logs interface.
The message Error: 15457, Severity: 0, State: 1 because it has a severity of 0 is an Informational message rather than an actual error message. The Error 15457 is generated when you open the SQL 2000 Enterprise Manager Properties and it is usually preceded with an error similar to the one listed below:
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Tip: The default System Message is: Configuration option '%ls' changed from %ld to %ld. Run the RECONFIGURE statement to install.
Note: SQL Severity numeric values 0 – 10 are all Informational Messages.
The particular message above simply means that someone has opened the SQL Server Properties to check or view its configuration and since it is an informational message it can be disregarded or ignored.
To test this open the SQL server MMC snap-in in question and right mouse click on the Server name and from the connect menu select “Properties” and then select “OK” to close the window. Then from the Management leaf select “SQL Server Logs” and open the “Current DD/MM/YYYY mm:ss” log file and scroll to the bottom and the last two entries will be displayed as
Source: spidxx
Date: YYYY-MM-DD hh:mm:ss.ms
Message: Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Message: Error: 15457, Severity: 0, State: 1
Note: You may have to refresh the Log file if the log is currently open from the context menu.
Tip: The Source SPID is not important as it is simply the Session ID for the current user that viewed the properties page and does not necessarily mean that they initiated any changes at the properties page. You can however run the following SQL query to determine the user name for the session ID if needed. Be sure to change the XX to the spid number listed in the source without the spid. For example if the session ID is spid99 enter 99:
Select System_User 'User Name' Where @@SPID = 'XX'
No Comments