BizTalk Scheduled Task Adapter is now stable and officially available for BizTalk Server 2016

Almost 20 days since I release the beta version of BizTalk Scheduled Task Adapter and still no issues reported. I also have been testing intensely the adapter so it is fair to say that this version it is stable, so, I officially remove the “beta label” from this version. BizTalk Scheduled Task Adapter is finally officially available (version 6.0) and optimized for BizTalk Server 2016!

The BizTalk Scheduled Task Adapter is an in-process receive adapter that executes a prescribed task on a daily, weekly or monthly schedule. The adapter is configured entirely within BizTalk, all configurations are stored within the SSODB and can be exported and imported via binding files.

The schedule capabilities are similar to those available with the Windows Scheduled Task Service.

BizTalk Scheduled Task Adapter for BizTalk Server 2016

What is new?

New schedule capabilities:

  • You can now schedule for a message to be a trigger in a time period, for example, each hour, minutes or seconds, every day or on certain days (for example all days except weekends).

BizTalk Scheduled Task Adapter new schedule capability

What was improved or fixed?

Several reported issues were from previous BizTalk Scheduled Task Adapter versions were solved, for example:

  • In some scenarios, trigger message sent twice at the same time – Solved
  • Bug: Time change (DST) bug – Solved
  • Bug: BizTalk Scheduled Task Adapter SQL Timeout issue – Solved

You can download this new version of the Scheduled adapter in the adapter CodePlex project page:

Please fill free to try and use the adapter and If you find any problems or bugs please open issue on the adapter Codeplex site: https://biztalkscheduledtask.codeplex.com/workitem/list/basic and help evolve this community adapter You can also suggest new features, I am also open to new ideas.

You can also find the Installation process documented here: BizTalk Scheduled Task Adapter 6.0: Installation process

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

  • Mahesh

    Hello, new adapter 6.0 is not working, schedule is not triggering at all. tried with 32 and 64 bits and all types of schedules like timespan/daily/weekly.

    • Sandro Pereira

      Very strange… I already installed in several machines and i didn’t find any kind of problems… do you see any error message in event viewer or somekind of error message?

      • Mahesh

        Thanks for your response. no errors, and schedules are not running. we installed on 3 different servers. as per the document it should create HKEY_CLASSES_ROOTCLSID{7A4BDD2A-3063-4f57-A108-DEA05DEB417E}

        . but its not, the same ID is in 5.0 version, so might have missed to update GUID.

        • Sandro Pereira

          need to check the key but I think is different now something like HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeClassesCLSID{F2FAA6A3-45E2-4C09-8024-425E768CC8EF}

          • Mahesh

            any update on this? anybody has luck? is 6.0 working?

          • Mahesh

            If any body using 6.0, can you please help me in resolving the issue? schedule adapter is not triggering at all

    • Nathan Dykman

      I have seen the same problem with a project that I am (very desperately) trying to update to BizTalk 2016. An instance of a custom task is made, but it is never called.

      • Nathan Dykman

        After downloading the source and building a local version, I can confirm that the release does seem to have some issues. I confirmed that tasks were never called. When I changed all usages of DateTime.UtcNow to DateTime.Now in the code, scheduled tasks fired as expected.

        • Mahesh

          Thanks Nathan, what do you mean by When I changed all usages of DateTime.UtcNow to DateTime.Now in the code, scheduled tasks fired as expected.? I dont have source code, pls let me know where you changed? DB?

          • André Silva

            I have the same issue. Trying to use it on an Azure Virtual Machine but the task is schedule 3 hours later than the current time. So the task is not fired. I’ve downloaded the source code to see if Nathan’s idea works.

          • Mahesh

            download source code and replace DateTime.UtcNow with DateTime.Now as Nathan suggested, it should work. its working for me

  • eva

    Hello,

    Im having trouble with the
    BizTalk ScheduledTask Adapter 6.0 for BizTalk 2016. The .dlls are in the GAC,
    and everything looks fine. But my receive Method gives me the following ERROR:

    “The receive location “Receive_Currency_loc” with URL “schedule://Daily/NorgesBanksDailyCurrencyFile”
    is shutting down. Details:”Unable to cast object of type
    ‘ScheduledTaskAdapter.TaskComponents.HttpDownload’ to type
    ‘ScheduledTaskAdapter.TaskComponents.IScheduledTaskStreamProvider’.”.

    I have searched, but cannot
    find anything about this ERROR. Do you have any suggestions?

    Brg

    Eva

  • Manjunath Hireholi

    HTTP Download is not generating the xml from the website xml feed

  • Mahesh

    Thanks Nathan, I have done the same, downloaded code then DateTime.UtcNow to DateTime.Now. now its working fine. not sure how it was working ? Sandro?

  • Nota Registrada

    Dear Mr. Pereira,

    We use the schedule adapter in an Azure VM but as much as we tried to configure it to read the VM time, the adapter read the Azure host time (3 hours more than VM). We use BTS2016 with Feature Pack 1 (and set the time zone to GMT -3, our scenario). Would you kindly guide us as we find out where the adapter is looking for the time to run? Grateful. Carlos Santos / eCorp / Brazil

One Platform Operations, Monitoring and Analytics Software
BizTalk360

microsoft biztalk

Learn more

Over 500 customers across 30+ countries depend on BizTalk360

ServiceBus360

Azure service bus

Learn more

Start managing your Azure Service Bus namespaces in minutes

One Platform - Operations, Monitoring and Analytics Software
BizTalk360

microsoft biztalk

Learn more

Over 500 customers across 30+ countries depend on BizTalk360

One Platform - Operations, Monitoring and Analytics Software
ServiceBus360

Azure service bus

Learn more

Start managing your Azure Service Bus namespaces in minutes

Back to Top