We were unable to load Disqus. If you are a moderator please see our troubleshooting guide.

Jim Barr • 5 years ago

Thank you! This "fix" is a LIFESAVER!

The only glitch I found is that in our BT 2016 Standard install, the "result" variable returns UTC time, not Local time. This causes the schedule to reschedule at the correct minute, but 5 hours ahead. 5 hours later, it runs, then reschedules again for 5 hours ahead--obviously not what we want. So as a quick fix, I just appended ".AddHours(-5)" to "result" and it now schedules properly. Long term, I'll tweak the code to convert "return" from UTC to Local time to account for DST.

Warren Kinley • 5 years ago

When I restart the Host Instance the schedule time reverts to the time the host instance was started. Is this a known issue?

Pekka Huuskonen • 5 years ago

It's that exact behavior with original Scheduled Task Adapter, that I discussed in the first post https://www.pekkahuuskonen....
If you can implement the fix described in this post, the adapter shoud work fine.

Warren Kinley • 5 years ago

Thank you, fixed now after I placed the code in the correct place!

Maik Lange • 6 years ago

Hi, i have a similar problem. When i set the timly schedule to 5 minutes, the biztalk appilation starts twice. I suppose theres a problem with the scedular. The problem also occurs when i stop the host instances. After 10 Minitis when i start the host instance die appliation starts three times.

I hope you can help me an have an idea where the Problem is to find.

thanks

Pekka Huuskonen • 6 years ago

I'm not familiar with the exact problem that you have, but I've seen similar problems discussed in Sandro Pereiras original blog post comments. If I recall correct the newest version has some bug fixes, or you can try to reinstall Scheduled Task Adapters dll's to gac.
If you like I can supply my version of the Calendar.Schedules.dll to you.