First part of this post is available at SQL Server Agent failing to start because "The EventLog service has not been started".
I've just confirmed an improvement has been already checked-in into SQL Server 2008's code which keeps up calling EnumServiceStatus when it returns FALSE and GLE returns ERROR_MORE_DATA. It retries up to 10 times and sleeps 100 milliseconds between every attempt. If after all that retry logic, EnumServiceStatus continues failing due to the same error, we will continue seeing the same behavior which was explained in my first part of this story.
By the way, neither the amount of time elapsed between calls, nor the number of retries can be parameterized. They are both hardcoded.
See you in a next post.
PingBack from http://blogs.msdn.com/ialonso/archive/2007/12/13/sql-server-agent-failing-to-start-because-the-eventlog-service-has-not-been-started.aspx
SQL Server Agent が起動に失敗する : 「サービス EventLog は開始されていません」
Thanks you for excellent information.
This problem happen at My friends' SQL Server 2000.
So, SQL Server 2000 have this problem,
SQL Server 2008 may be fixed.
How about SQL Server 2005 ?
Are there this problem yet in 2005 ?
and, I cannot found any information about this in Microsoft support site (KB).
Any chance of this bug being incorporated into a MS KB article?