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:
- Changed Utility Host to 32 Bit from 64 bit– no change – indicates it’s not dependent on 64 or32 bit hosts
- Set the Receive Pipeline to Pass Thru – no change – indicates it’s not related to the custom pipeline
- 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
- Reduce number of worker threads in the receive host– no change
Any further suggestions?