Invoke EXE from Orchestration

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Invoke EXE from Orchestration

Viewing 1 reply thread
  • Author
    Posts
    • #24807

      I am invoking an EXE via a referenced C# assembly that has some Process.Start code in it. The EXE is designed to pick up a file that the same orchestration put in a folder. I’m getting the error below – my guess is that the orchestration still has a handle on that file even though its done sending it  as the SEND is done within an atomic scope before moving on invoking of the EXE.

      ‘C:\Employee\Incoming\EmployeeData_20100525_080754.xml’ because it is being used by another process.

      Are there any ways to explicitly force the orchestration to let go of the file?

    • #24808

      Hi,

       

        Try checking off the Ordered Delivery checkbox in the Transport Advanced options tab of your Send port and see if that remedies the behavior.

       

        Daniel.

       

      • #24809

        Ordered Delivery checkbox is not checked. I tried checking it – either way I still run into the System.IO exception – file in use.

        • #24810

          The orchestration Send only publishes the message to the MessageBox and continues. The physical send port then subscribes to the message and writes the file. Chances are the file does not yet exist or is still in use when your exe is run.

          You need to use Delivery Notification on the Send so that the orchestration blocks until the file has been successfully written. Put the Send shape in a Synchronised Scope (you do not need a transaction) and set Delivery Notification to “Delivered” on the Send port. 

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.