sql server notification services: I keep getting these messages. Not sure what to do!



Event Type: Error
Event Source: NotificationServices
Event Category: None
Event ID: 4020
Date: 10/29/2004
Time: 12:35:48 AM
User: N/A
Computer: NTF
Description:
<NotificationServicesEvent>
<Description>
The generator failed to schedule a quantum.
</Description>
<Context>
<EventParameters>
<ApplicationName>NTF_Global</ApplicationName>
</EventParameters>

<SqlServerError>
Source: .Net SqlClient Data Provider
Number: 50000
State: 1
Class: 16
Server:
Message: 4012: There is a completed quantum which includes the current real
time.
Procedure: NSScheduleQuantum1
Line Number: 52
</SqlServerError>

</Context>
<Description>
4012: There is a completed quantum which includes the current real time.
</Description>
<Instance>NTF_Global_AutoBatchInstance</Instance>
<ApplicationName>NTF_Global</ApplicationName>
<Component>Generator</Component>
<Thread>10</Thread>
</NotificationServicesEvent>

Hi Chad,

This error occurs when there is an inconsistency in the state of the NS
application: a quantum is marked as completed, but according to the system
clock time, that quantum's end time is greater than or equal to "now". This
can happen in a few scenarios:

- The server's clock time is being synced to an external server, resulting
in minute adjustments to the system time. In these cases, the error message
is normally benign -- the next time the scheduler runs, the state of the
application looks fine.

- On some servers, the time between the end of one quantum and the start of
the next is short enough to fall within the granularity of the internal
clock. In these cases, the error message is a false positive and is normally
benign.

- The server's clock has been set to some time in the distant future for
testing reasons. In this case, there is a more serious problem with the
internal state: the service will not begin to schedule quanta until real
time catches up, and any events arriving in the interim would be orphaned.
In such cases, the only safe recommendation I can think of is rebuilding the
instance and restarting.

If you are encountering the last case, please contact me!

-Colin Meek [MSFT]

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
--

[quoted text, click to view]