Quantcast
Channel: BizTalk Scheduled Task Adapter
Viewing all 138 articles
Browse latest View live
↧

Commented Unassigned: Trigger message sent twice at the same time [10897]

March 4, 2017, 4:42 am
$
0
0
Hello,

I'm using the scheduled task adapter to trigger orchestrations, using the XmlStringStreamProvider, and to create a singleton pattern in the orchestration.
The receive location is configured to trigger a message every minute and the orchestration is designed with a loop to ignore other trigger messages in case the duration exceed 1 min.
It's not perfect and I get Zombie messages.

The issue is that 2 messages are sent to my orchestration every minute ..

I did a test, triggering an orchestration without the singleton pattern loop, and two instances started at the same time, after 1 min.
And when I look at my zombie messages in the suspended instance, they are always by pair.

In the example attached:
- The orchestration started at 3:55:00 (triggered by 1 message from the adapter, and ignore the duplicate)
- At the end, there are 4 zombie messages, you can group them by 2: same message ID, same creation date.
- 2 messages created at 3:55:58 and 2 messages created at 3:55:59

So for a schedule set up every minute, something is wrong ...

Any help would be welcome :)

Thank you.
Comments: ** Comment from web user: sandro_asp **

Again difficult to debug this problem, but I am trying to emulate with 30m, 10m, 2H and even with 1s and everything is running fine with the new release I am working on - only one message is being triggered.

And again, if you have several BizTalk boxes, you can only run the host instance in one of the servers, otherwise, you need to cluster the host.

↧
Search

Edited Unassigned: Trigger message sent twice at the same time [10897]

March 4, 2017, 4:43 am
$
0
0
Hello,

I'm using the scheduled task adapter to trigger orchestrations, using the XmlStringStreamProvider, and to create a singleton pattern in the orchestration.
The receive location is configured to trigger a message every minute and the orchestration is designed with a loop to ignore other trigger messages in case the duration exceed 1 min.
It's not perfect and I get Zombie messages.

The issue is that 2 messages are sent to my orchestration every minute ..

I did a test, triggering an orchestration without the singleton pattern loop, and two instances started at the same time, after 1 min.
And when I look at my zombie messages in the suspended instance, they are always by pair.

In the example attached:
- The orchestration started at 3:55:00 (triggered by 1 message from the adapter, and ignore the duplicate)
- At the end, there are 4 zombie messages, you can group them by 2: same message ID, same creation date.
- 2 messages created at 3:55:58 and 2 messages created at 3:55:59

So for a schedule set up every minute, something is wrong ...

Any help would be welcome :)

Thank you.
↧
↧

Commented Unassigned: Disabled receive locations [10507]

March 4, 2017, 11:23 am
$
0
0
Hi all!

I have experiencing some strange behavior of scheduled task adapter.
My BizTalk application has 3 receive locations with different schedules.
Problem is that I cannot get to enable all three locations. Even if I try to enable locations they are still disabled after application refresh inside BizTalk console.

Exception stack is:

First exception

The receive location "xxx" with URL "schedule://Monthly/xxx" is shutting down. Details:"The Messaging Engine failed while notifying an adapter of its configuration. ".

Second exception:

The Messaging Engine failed to add a receive location "xxx" with URL "schedule://Monthly/xxx" to the adapter "ScheduleAdapter". Reason: "Time-out interval must be less than 2^32-2.
Parameter name: dueTime".


Any help would be appreciated.

Thanks
Comments: ** Comment from web user: sandro_asp **

Apparently, Microsoft.BizTalk.Scheduler.Runtime.dll (BizTalk DLL) doesn't accept schedule a task with more than 50 days.

↧

Commented Unassigned: Timeoutintervall must be smaller than 2^32-2 [10270]

March 4, 2017, 11:29 am
$
0
0
I want to make a Scheduled Task, which is started every 3 Month.
But when I'm, trying to start the Ports, I'm getting this Error " "Timeoutintervall musb be smaller than 2^32-2"

I've created the Port as a Monthly Sheduled Type and checked Jan, Apr, Jul, and Oct.
Is there some Fix or Workaround for this Issue?
Comments: ** Comment from web user: sandro_asp **

Apparently, Microsoft.BizTalk.Scheduler.Runtime.dll (BizTalk DLL) doesn't accept schedule a task with more than 50 days.

↧

Closed Issue: 4.0 version - deployment error - Could not load file or assembly 'Microsoft.BizTalk.Scheduler, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' [9780]

March 4, 2017, 11:29 am
$
0
0
Hello.

I installed the version 4.0 of the adapter and I successfully used it, but after making some modifications in my orchestration I tried to redeploy the application and I get the following error:

Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to update binding information. Could not validate TransportTypeData, Address or Public Address properties for Receive Location 'Receive Schedule Location'. Could not load file or assembly 'Microsoft.BizTalk.Scheduler, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

I checked the installed assemblies and the assembly Microsoft.Biztalk.Scheduler, version 3.0.1.0 is missing.

I tried to stop the application before deployment, but I am able to redeploy only if I delete the receive locations where I am currently using this transport type.
↧
↧

Closed Issue: Cannot Stop Application using BTDF - Could not load file or assembly 'Microsoft.BizTalk.Scheduler, Version=3.0.1.0 [9699]

March 4, 2017, 11:30 am
$
0
0
I have installed v4 of the Scheduled Task Adapter as per the instructions.

I have a BizTalk Application that has a Receive Location set up to use the Scheduled Task Adpater.

When I come to Deploy BizTalk Solution using the BTDF in Visual Studio when it tries and Stops the Application (StopApplication) I get this error in the Output window...

MSBUILD : warning : Could not validate TransportTypeData, Address or Public Address properties for Receive Location 'XXX'. Could not load file or assembly 'Microsoft.BizTalk.Scheduler, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. [XXX\Deployment\Deployment.btdfproj]

The work around is to manually stop my BizTalk Application before I Deploy BizTalk Solution.

I also note in Programs and Features the version for the BizTalk ScheduledTask Adapter is 3.0.0.
↧

Edited Issue: TaskScheduler receive location is triggered 1 hour before the scheduled time. [3301]

March 4, 2017, 11:32 am
$
0
0
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.
 
Thanks.
↧

Closed Issue: TaskScheduler receive location is triggered 1 hour before the scheduled time. [3301]

March 4, 2017, 11:33 am
$
0
0
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.
 
Thanks.
↧
Search

Edited Issue: Schedule Adapter seems to cause host to hang in Stopping State [9088]

March 4, 2017, 11:38 am
$
0
0
I am using the latest Version 3.0 Aug 10 2010, Beta schedule adapter on a BizTalk 2010 environment.
 
I've set up the adapter to run in its own 64 bit host called UtilityHost. I am having a problem where, once a schedule has run for the first time, the UtilityHost won’t stop cleanly and sits there in a Stopping state and never stops. I have to kill the process to make it stop.
 
This problem doesn't occur on a couple of development machines so could be environment related so I'm looking for pointers on where to look next. The problem happens on Windows 2008 R2 Enterprise but no Windows 2008 R2 Standard (so far).
 
I’ve tried a few things:
1. Changed Utility Host to 32 Bit from 64 bit– no change – indicates it’s not dependent on 64 or32 bit hosts
2. Set the Receive Pipeline to Pass Thru – no change – indicates it’s not related to the custom pipeline
3. Stopped the Schedule receive location before stopping the Utility Host – no change – indicates that there could be state in the host that is causing the problem
4. Reduce number of worker threads in the receive host– no change
 
Any further suggestions?
↧
↧

Closed Issue: Schedule Adapter seems to cause host to hang in Stopping State [9088]

March 4, 2017, 11:38 am
$
0
0
I am using the latest Version 3.0 Aug 10 2010, Beta schedule adapter on a BizTalk 2010 environment.
 
I've set up the adapter to run in its own 64 bit host called UtilityHost. I am having a problem where, once a schedule has run for the first time, the UtilityHost won’t stop cleanly and sits there in a Stopping state and never stops. I have to kill the process to make it stop.
 
This problem doesn't occur on a couple of development machines so could be environment related so I'm looking for pointers on where to look next. The problem happens on Windows 2008 R2 Enterprise but no Windows 2008 R2 Standard (so far).
 
I’ve tried a few things:
1. Changed Utility Host to 32 Bit from 64 bit– no change – indicates it’s not dependent on 64 or32 bit hosts
2. Set the Receive Pipeline to Pass Thru – no change – indicates it’s not related to the custom pipeline
3. Stopped the Schedule receive location before stopping the Utility Host – no change – indicates that there could be state in the host that is causing the problem
4. Reduce number of worker threads in the receive host– no change
 
Any further suggestions?
↧

Commented Issue: Schedule Task Adapter - location automatically gets disabled if schedule is greater 45 or more days ahead of the current date .. [9618]

March 4, 2017, 11:39 am
$
0
0
Requirement: I am creating schedule locations dynamically from the code on the basis of the user input from the screen and then calling biztalk orchestration .
Issue: If I create a schedule with starting date as 45 days ahead of the current date or greater than that , the corresponding receive location automatically gets disabled .I get the following error log in the event viewer – (The receive location "Receive Location2" with URL "schedule://TimeSpan/a" is shutting down. Details:"The Messaging Engine failed while notifying an adapter of its configuration. "). Any help would be appreciated .Thanks
Comments: ** Comment from web user: sandro_asp **

Apparently, Microsoft.BizTalk.Scheduler.Runtime.dll (BizTalk DLL) doesn't accept schedule a task with more than 50 days.

↧

Closed Issue: Schedule Task Adapter - location automatically gets disabled if schedule is greater 45 or more days ahead of the current date .. [9618]

March 4, 2017, 11:39 am
$
0
0
Requirement: I am creating schedule locations dynamically from the code on the basis of the user input from the screen and then calling biztalk orchestration .
Issue: If I create a schedule with starting date as 45 days ahead of the current date or greater than that , the corresponding receive location automatically gets disabled .I get the following error log in the event viewer – (The receive location "Receive Location2" with URL "schedule://TimeSpan/a" is shutting down. Details:"The Messaging Engine failed while notifying an adapter of its configuration. "). Any help would be appreciated .Thanks
↧

New Post: BizTalk 2016 Support

March 4, 2017, 11:40 am
↧
↧

New Post: BizTalk Server 2016

March 4, 2017, 11:41 am
↧

Released: Release 6.0.0 for BizTalk Server 2016 (Mar 04, 2017)

March 4, 2017, 12:09 pm
$
0
0
Requirements:
The Scheduled Task Adapter v6.0.6 is optimized and designed to be used with BizTalk Server 2016 (Compiled in .NET Framework 4.6).

V6.0.0 Changelog:
  • Compiled in Visual Studio 2015 and .NET Framework 4.6.
  • Optimized for BizTalk Server 2016.
  • Support for 32 and 64 bit Host Instances.
  • New features
    • New Schedule capabilities - Time Schedule running every day or on certain days (for example all days except weekends).
  • Bug fixes
    • Bug: 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
  • Improvements
    • Some improvements in Monthly schedules form
    • UTC support
↧
Search

Created Release: Release 6.0.0 for BizTalk Server 2016 (Mar 04, 2017)

March 4, 2017, 12:09 pm
$
0
0
Requirements:
The Scheduled Task Adapter v6.0.6 is optimized and designed to be used with BizTalk Server 2016 (Compiled in .NET Framework 4.6).

V6.0.0 Changelog:
  • Compiled in Visual Studio 2015 and .NET Framework 4.6.
  • Optimized for BizTalk Server 2016.
  • Support for 32 and 64 bit Host Instances.
  • New features
    • New Schedule capabilities - Time Schedule running every day or on certain days (for example all days except weekends).
  • Bug fixes
    • Bug: 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
  • Improvements
    • Some improvements in Monthly schedules form
    • UTC support
↧

Commented Unassigned: Trigger message sent twice at the same time [10897]

March 20, 2017, 10:47 am
$
0
0
Hello,

I'm using the scheduled task adapter to trigger orchestrations, using the XmlStringStreamProvider, and to create a singleton pattern in the orchestration.
The receive location is configured to trigger a message every minute and the orchestration is designed with a loop to ignore other trigger messages in case the duration exceed 1 min.
It's not perfect and I get Zombie messages.

The issue is that 2 messages are sent to my orchestration every minute ..

I did a test, triggering an orchestration without the singleton pattern loop, and two instances started at the same time, after 1 min.
And when I look at my zombie messages in the suspended instance, they are always by pair.

In the example attached:
- The orchestration started at 3:55:00 (triggered by 1 message from the adapter, and ignore the duplicate)
- At the end, there are 4 zombie messages, you can group them by 2: same message ID, same creation date.
- 2 messages created at 3:55:58 and 2 messages created at 3:55:59

So for a schedule set up every minute, something is wrong ...

Any help would be welcome :)

Thank you.
Comments: ** Comment from web user: nubpotato **

Hi Sandro,

We have always only had one host instance running the scheduler, so that is for sure not the issue here. In fact, I was able to reliably replicate the issue on an isolated Biztalk 2013 R2 Development VM running the scheduler over the weekend (single instance Biztalk + SQL on same server).

To mimic what we have in our production environment, I have setup 3 parallel receive ports/locations with scheduler adapter (XML String Provider) with parameters as follows:
RP_TEST_5MIN - Runs every 5 minutes from 0:00 of the hour
RP_TEST_10MIN_1 - Runs every 10 minutes from 0:05 of the hour
RP_TEST_10MIN_2 - Runs every 10 minutes from 0:00 of the hour

Each receive location has a simple logging pipeline to log the datetime and message into table on database, which is where these logs were pulled.

I have attached the resulting logs from this past weekend in 'SchedulerAdapterTest-Logs.xlsx'. As you will see, the duplicate calls occur a few times every 24hr period for each RP. Hopefully this is enough detail for us to reopen this issue.

↧
↧

Released: Release 6.0.0 for BizTalk Server 2016 (Mar 04, 2017)

March 21, 2017, 12:34 pm
$
0
0
Requirements:
The Scheduled Task Adapter v6.0.6 is optimized and designed to be used with BizTalk Server 2016 (Compiled in .NET Framework 4.6).

V6.0.0 Changelog:
  • Compiled in Visual Studio 2015 and .NET Framework 4.6.
  • Optimized for BizTalk Server 2016.
  • Support for 32 and 64 bit Host Instances.
  • New features
    • New Schedule capabilities - Time Schedule running every day or on certain days (for example all days except weekends).
  • Bug fixes
    • Bug: 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
  • Improvements
    • Some improvements in Monthly schedules form
    • UTC support
↧

Updated Release: Release 6.0.0 for BizTalk Server 2016 (Mar 04, 2017)

March 21, 2017, 12:34 pm
$
0
0
Requirements:
The Scheduled Task Adapter v6.0.6 is optimized and designed to be used with BizTalk Server 2016 (Compiled in .NET Framework 4.6).

V6.0.0 Changelog:
  • Compiled in Visual Studio 2015 and .NET Framework 4.6.
  • Optimized for BizTalk Server 2016.
  • Support for 32 and 64 bit Host Instances.
  • New features
    • New Schedule capabilities - Time Schedule running every day or on certain days (for example all days except weekends).
  • Bug fixes
    • Bug: 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
  • Improvements
    • Some improvements in Monthly schedules form
    • UTC support
↧

New Post: BizTalk Server 2016

March 21, 2017, 1:59 pm
$
0
0
Hi, I am not able to download v 6.0
↧
Viewing all 138 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>