This project is read-only.


TaskScheduler receive location is triggered 1 hour before the scheduled time.


We have a receive location configured using BizTalk Scheduled Task Adapter, which is set to generate an XML message everyday at 10:30AM. It's been runing okay till recently we found the receive location got triggered at 9:30AM --- 1 hour before the scheduled time. (We have 1 biztalk server and 1 SQL server).
The attached is a screenshot from HAT showing 2 instances of receive location.

file attachments

Closed Mar 4 at 7:33 PM by sandro_asp


dbuckjr wrote May 20, 2011 at 2:05 PM

We were seeing this issue as well. However, we determined that the events were actually firing twice at the nearly the same time. In our case, it was HAT that incorrectly reported the time as an hour earlier. When I ran a query directly against the database without HAT, the times showed that they were actually within milliseconds of each other. It appears to be an error related to the UTC time difference as calculated by HAT. Why it is different between the two rows I have not been able to figure out.

I know this is an old post, but are you still seeing this issue? We have not yet updated to the new version.

wrote Feb 14, 2013 at 8:13 PM

wrote Mar 4 at 7:32 PM

wrote Mar 4 at 7:33 PM