Error: 15457, Severity: 0, State: 1

Question

Error: 15457, Severity: 0, State: 1

Jpotucek

SSCoach

Points: 18583
More actions
December 28, 2005 at 12:46 pm

#152684

I am getting these errors in my event log periodically:
Error: 15457, Severity: 0, State: 1
and then
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..
I'm not sure what to make of these errors or how to begin researching.. can anyone help??

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

noeld SSC Guru Points: 96590 More actions · Answer 1

I've seen this type of messages when monitoring tools change the 'show advanced options' and forget to execute RECONFIGURE after it.

because this is a server wide setting all that is needed is for you to run RECONFIGURE maually. This is not a big problem but you will need to look for the offending party if you want to get rid of this message on the sql logs

Cheers,

* Noel

Joshua Jones-214598 SSChasing Mays Points: 637 More actions · Answer 2

The other thing that causes this is simply opening up the server properties dialog in Enterprise Manager and clicking OK to exit instead of Cancel (i.e. a DBA goes to look at the Startup Parameters, then after verifying clicks the OK button to close the dialog box).

Cheers,

Joshua Jones

Jpotucek SSCoach Points: 18583 More actions · Answer 3

Thank you. I did go into the Server Properties a couple of time through EM and then X'd out. maybe that caused the errors...

I seem to get them periodically and didn't know if it was a problem.

I have been having a problem yesterday and today with a monitering tool reporting a Cache Hit Ratio of over 60 % on this SQL Server .. I thought the errors might be related.. anyone know what the high cache hit ratio means??

sswords SSCrazy Eights Points: 8207 More actions · Answer 4

Generally speaking, a high buffer/cache hit ratio is an indication that your server is running optimally. An accepted rule of thumb is that you normally want this number to be 90% or higher but this may not be the case for all systems. If it's consistently lower than that, you can do things like adding RAM and/or tuning or adding indexes to improve the ratio.

Another thing to consider is that this counter is cumulative and will report an average hit ratio since the last time SQL Server was restarted. To get a good number on your current server state, you'll need to restart the server (or the SQL service anyway) and then let it run for a period of time and then re-check your hit ratio. Hope this helps.

My hovercraft is full of eels.