Forum Discussion
BizTalk 2020 CU1 Weekly and monthly schedules broken?
Hi.
I'm trying to schedule a receive location to only run during the weekends. Unfortunately as soon as I enable weekly recurrence on the schedule, BizTalk starts the receiver endpoint immediately (outside of the defined service window), disposes it after 30 seconds and starts it again in another 30 seconds ad infinitum.
Here is a sample trace from my custom adapter:
15:28:13 My.BizTalk.Adapter.ReceiverEndpoint.Open()
15:28:13 My.BizTalk.IntervalSchedule.GetNextActivationTime(): 00:10:00
15:28:43 My.BizTalk.Adapter.ReceiverEndpoint.Dispose()
15:29:13 My.BizTalk.Adapter.ReceiverEndpoint.Open()
15:29:13 My.BizTalk.IntervalSchedule.GetNextActivationTime(): 00:10:00
15:29:43 My.BizTalk.Adapter.ReceiverEndpoint.Dispose()
Please note that the problem is not limited to my custom adapter, the same happens with the built-in File adapter.
Was anyone able to successfully use weekly schedules?
jaydeepahuja, you have written a blog post about this functionality, can you please comment?
Best regards, Igor
- IgorMilavec thank you for your feedback!
We are unable to reproduce the issue. Can you please update your environment to BizTalk Server 2020 CU3 (https://support.microsoft.com/topic/5007969)?
If you still have problems, please open a support case with BizTalk (Integration) support team at https://support.microsoft.com/contactus.
3 Replies
- jaydeepahuja
Microsoft
File adapter works fine with built-in Scheduling Feature in BizTalk Server 2020.
We were able to setup File receive locations with weekend/weekday or any kind of weekly schedules.
A cause of non working schedule as per expectation might be not setting up Time Zone appropriately.
If you still observe any issues with scheduling, please provide more details about your scenario and schedule settings or file a ticket with customer support.
- IgorMilavecCopper Contributor
jaydeepahuja strange, it does not seem to work for me. I'm attaching bindings for the simplest scenario ever: file receive location bound to a file send port. The receive location is set to only run on Wednesdays (today is Saturday) to account for any one-of errors, time zone differences etc.
If I drop a file in C:\Temp\Test\In, it is not processed immediately (consistent with my observations about handlers being disposed every 30 seconds), but it is processed with at most 30 seconds delay.
I'm running BizTalk Standard 2020 CU1 on Windows 2019, default BizTalkServerApplication host instance, so mostly as vanilla as it gets.
I also tested this on BizTalk Enterprise 2020 CU1 running on Windows 2016. Same result.
Both servers are English with Slovenian regional settings and CET time zone.
- NehaGupta
Microsoft
IgorMilavec thank you for your feedback!
We are unable to reproduce the issue. Can you please update your environment to BizTalk Server 2020 CU3 (https://support.microsoft.com/topic/5007969)?
If you still have problems, please open a support case with BizTalk (Integration) support team at https://support.microsoft.com/contactus.