Runtime Server Not Receiving Notifications

Topics: Technical Questions
Jan 19, 2010 at 8:39 PM

I'm receiving the following error in the catalog server log whenever a change occurs that should be received by the runtime server.  The runtime server is not receiving any notifications at all.  I'm running the December release, no problems with the May release.  Host name, notification address, everything seems like it's configured correctly.

mseTraceSrc Information: 0 : Removing expired repository change record. Created[01/19/2010 12:34:43] Message:[<DBEventContext xmlns:d1p1="" xmlns:i="" xmlns=""><d1p1:ChangeType>Update</d1p1:ChangeType><d1p1:Event>OperationsUpdated</d1p1:Event><d1p1:EventData><d1p1:DBEventDataItem><d1p1:EndpointId>a9000ceb-599e-41f9-a916-4fb598e85dc9</d1p1:EndpointId><d1p1:OperationId>acaa4744-90f3-4cda-8bdd-80cf8a738197</d1p1:OperationId><d1p1:RuntimeServerId>a66702e6-4116-4986-8e5f-535be2fc66d8</d1p1:RuntimeServerId></d1p1:DBEventDataItem></d1p1:EventData></DBEventContext>]




Jan 19, 2010 at 9:58 PM
Edited Jan 19, 2010 at 9:58 PM

What errors preceeded the one you included in the post?  The change records will be kept and retried for a period of time before "expiring" and being removed.  The HostName for the runtime server will need to be a DNS resolvable name.  Second, verify that the Runtime server's log indicates the notification endpoint has started.  You should see a couple events. StartCallbackNotification, and then "Notification endpoint started [<notificationURI>]".




Jan 19, 2010 at 10:59 PM

I scanned all the logs and there were no other errors, host name seems good and the log shows the Notification Endpoint started.  There's no message in the catalog showing that a notification was received from the DB, just the message about the expired record.

I am using a new SQL Server 2008 database instance.  Could there be something there that I'm missing?  Also, the server is Windows Enterprise 2008.  Everything works fine on my local box, and I've deployed to another server successfully with the May release.




Jan 20, 2010 at 10:04 PM

I found the solution.  The time on the SQL Server machine was off by two hours, so the timestamps on the change records were off by two hours, causing the repository to discard them as expired.

So, no problem with the MSE.