none
MessageEnrichment Sample not working! RRS feed

  • Question

  •  

    Running into this error, after I successfully ran the setup.bat for Msg Enrichment sample in the SDK

     

    TITLE: BizTalk Server 2006 Administration Console
    ------------------------------
    Could not enlist orchestration 'Microsoft.Samples.BizTalk.MessageEnrichment.MessageEnrichmentOrchestration,MessageEnrichment, Version=1.0.0.0, Culture=neutral, PublicKeyToken=2720f9c291c03aa9'. Could not enlist orchestration 'Microsoft.Samples.BizTalk.MessageEnrichment.MessageEnrichmentOrchestration,MessageEnrichment, Version=1.0.0.0, Culture=neutral, PublicKeyToken=2720f9c291c03aa9'. Object reference not set to an instance of an object. (Microsoft.BizTalk.SnapIn.Framework)


     

    Monday, August 6, 2007 1:09 PM

Answers

  • Hello!

     

    It seems that something went wrong during the setup phase.

     

    In order to track the issue do the following:

     

    1. Run CleanUp.bat to remove all the artifacts deployed.

    2. From command line, run Setup.bat again.

    3. After setup.bat is finished running scan through the console output to see if there are any warnings or errors.

     

    The expected result of running setup.bat is:

    1. Orchestration is deployed and enlisted.

    2. Send and receive port are created and started.

     

    So, if your ouput is different, it means something went wrong during setup.

     

    In this particular case it seems that Message Enrichment library cannot initialize some classes it needs. The only 2 references it uses are:

    - Microsoft.BizTalk.Edi.BaseArtifacts

    - Microsoft.XLANGSs.BaseTypes

     

    Make sure that they are accessible. You can try to gac them and see if that helps. If it does, that can help you to isolate the problem.

     

    Thank you,

    Yury

    Wednesday, August 8, 2007 5:33 PM

All replies

  • Hello!

     

    It seems that something went wrong during the setup phase.

     

    In order to track the issue do the following:

     

    1. Run CleanUp.bat to remove all the artifacts deployed.

    2. From command line, run Setup.bat again.

    3. After setup.bat is finished running scan through the console output to see if there are any warnings or errors.

     

    The expected result of running setup.bat is:

    1. Orchestration is deployed and enlisted.

    2. Send and receive port are created and started.

     

    So, if your ouput is different, it means something went wrong during setup.

     

    In this particular case it seems that Message Enrichment library cannot initialize some classes it needs. The only 2 references it uses are:

    - Microsoft.BizTalk.Edi.BaseArtifacts

    - Microsoft.XLANGSs.BaseTypes

     

    Make sure that they are accessible. You can try to gac them and see if that helps. If it does, that can help you to isolate the problem.

     

    Thank you,

    Yury

    Wednesday, August 8, 2007 5:33 PM
  • Dear friends,

    when i fill application Name is null (in tab deployment) and run setup.bat file, have errors, can you help me:

    binding.log file

    Microsoft (R) BizTalk Application Deployment Utility Version 3.9.469.0
    Copyright (c) 2010 Microsoft Corporation. All rights reserved.

    Information: Importing bindings "MessageEnrichment\MessageEnrichmentBindings.xml" into application "BizTalk Application 1" in BizTalk configuration database (server="WIN-V9S3C8VDSQ7\SQL2008", database="BizTalkMgmtDb")...
    Error: Failed to update binding information.
    Cannot update send port "MessageEnrichmentSendPort".
    Cannot update transport information (address "C:\Program Files (x86)\Microsoft BizTalk Server 2010\SDK\Samples\EDI\MessageEnrichment\Out\%MessageID%.xml").
    The following items could not be matched up to hosts due to name and/or trust level mismatches:
    Item: 'FILE' Host: 'BizTalkServerApplication' Trust level: 'Trusted'
    You must do one of the following:
    1) Create hosts with these names and trust levels and try again
    2) Re-export the MSI without the binding files and have a post import script apply a suitable binding file.


    Command failed with 1 errors, 0 warnings.


    emanifest

    Saturday, September 21, 2013 11:40 AM
  • Keep these point in your mind before enlist orchestration in BizTalk messaging.

    The orchestration must be bound before you can enlist it.
    Subscriptions are automatically created.
    You must install the application containing the orchestration on all of computers where it runs.
    A calling orchestration must be bound to the same host as the called orchestration.
    You should also enlist dependent orchestrations.

    http://www.athenainfotech.co.uk/managed-b2b-services


    • Edited by Olivia Jones Thursday, October 3, 2013 11:43 AM Add more content for much clarification
    Thursday, October 3, 2013 11:40 AM