BizTalk Scheduled Task Adapter for BizTalk Server 2020 (Error & Workaround) (EN)

BizTalk Scheduled Task Adapter - the challenge

In BizTalk 2020 projects, many users of the BizTalk Scheduled Task Adapter are currently faced with the problem that it throws errors during reconfiguration under BizTalk 2020 and cannot be configured.

We have been implementing BizTalk Server 2020 upgrade & migration projects in the DACH region for a year. Together with our customers, we evaluate the current possibilities of maintaining a BizTalk implementation and "only" modernizing it or completely replacing it with new Microsoft-based integration technologies.

If our customer decides to keep the BizTalk Server and thus only to modernize his environment, it is mostly BizTalk 2010 or BizTalk 2013 implementations that we migrate to the current version of BizTalk Server 2020 and then optimize.

In the further course of this article, we are happy to share our experiences from the BizTalk migration projects with you. 

BizTalk Scheduled Task Adapter - the solution

We have therefore found a very simple workaround for the challenge of how the current version 6.0 of the Scheduled Task Adapter from Sandro Pereire can be run under BizTalk 2020 as part of customer projects.

After a successful installation and the first attempt to configure the adapter, we see the following error message. In our opinion, this is not a serious error in the adapter, but an error on the UI surface that simply prevents us from informing the adapter of the correct provider in the usual way.

Our workaround is to set the adapter of the respective provider via the corresponding input mask by entering the following text for the XmlStringProvider and confirming with OK or Apply.

ScheduledTaskAdapter.TaskComponents.XmlStringStreamProvider, ScheduledTaskAdapter.TaskComponents, Version =, Culture = neutral, PublicKeyToken = aa9f2dd0f13442dc

The entry can also be derived for the other providers:

ScheduledTaskAdapter.TaskComponents. [PROVIDERNAME], ScheduledTaskAdapter.TaskComponents, Version =, Culture = neutral, PublicKeyToken = aa9f2dd0f13442dc

Afterwards, the adapter works as usual and the migration of the existing solution can continue.

BizTalk Scheduled Task Adapter - summary

As described above, we made the migration of the BizTalk Scheduled Task Adapter possible. This makes developing the BizTalk 2020 interfaces considerably more convenient and faster!