none
Reason: Could not load type 'Microsoft.BizTalk.Edi.MessageCore.ReceiverRoleX12Settings' from assembly RRS feed

  • Question

  • A message sent to adapter "FILE" on send port "OMH.Finance.EDI.UB92to837_5010.OPMCARE.snd_EDI_FILE" with URI "C:\BizTalk\Finance\OMH.Finance.EDI.UB92to837_5010.OPMCARE\Ports\Output\OPMCARE.%datetime_bts2000%.edi" is suspended. 
     Error details: There was a failure executing the send pipeline: "Microsoft.BizTalk.Edi.DefaultPipelines.EdiSend, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "EDI Assembler" Send Port: "OMH.Finance.EDI.UB92to837_5010.OPMCARE.snd_EDI_FILE" URI: "C:\BizTalk\Finance\OMH.Finance.EDI.UB92to837_5010.OPMCARE\Ports\Output\OPMCARE.%datetime_bts2000%.edi" Reason: Could not load type 'Microsoft.BizTalk.Edi.MessageCore.ReceiverRoleX12Settings' from assembly 'Microsoft.BizTalk.Edi.MessageCore, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.  
     MessageId:  {E03D16FE-5D37-4CF3-87E8-1539B7D58A72}
     InstanceID: {3C8F7687-1438-40BD-84C1-F1E24D65F5D5}

    Racha Rams
    Thursday, September 22, 2011 7:48 PM

Answers

  • Hi

    Solved the issue. The windows registry settings for biztalk and Core EDI Assemblies were messy. 

    So, I copied the registry settings and core EDI assembly values form the working VM into mine.


    Racha Rams
    • Marked as answer by Racha Rams Monday, October 3, 2011 12:59 PM
    Monday, October 3, 2011 12:59 PM
  • I recommend never modifying the registry like this - you can break your supportability. For others reading this thread, I would contact MS Support first.

    Thanks,


    If this answers your question, please use the "Answer" button to say so | Ben Cline
    • Marked as answer by Racha Rams Tuesday, October 4, 2011 3:23 PM
    Monday, October 3, 2011 4:26 PM
    Moderator

All replies

  • Try adding a BizTalk application reference to the BizTalk application with this assembly. If you cannot find a BizTalk application with this assembly, try looking for the assembly on disk and adding it to the resources in the administration console for your BizTalk application.

    Using the all artifacts view in the admin console can be helpful for this.

    Thanks,


    If this answers your question, please use the "Answer" button to say so | Ben Cline
    Friday, September 23, 2011 2:31 AM
    Moderator
  • Hi Ben

    I tried the same, but he results are vain...

    Thanks


    Racha Rams
    Friday, September 23, 2011 3:56 PM
  • Maybe try repairing your BizTalk install? I am wondering if this may be an internal dependency of one of the components of the EdiSend pipeline - used for reading the X12 party settings.

    Thanks,

     


    If this answers your question, please use the "Answer" button to say so | Ben Cline
    Tuesday, September 27, 2011 2:43 AM
    Moderator
  • Hi

    Solved the issue. The windows registry settings for biztalk and Core EDI Assemblies were messy. 

    So, I copied the registry settings and core EDI assembly values form the working VM into mine.


    Racha Rams
    • Marked as answer by Racha Rams Monday, October 3, 2011 12:59 PM
    Monday, October 3, 2011 12:59 PM
  • I recommend never modifying the registry like this - you can break your supportability. For others reading this thread, I would contact MS Support first.

    Thanks,


    If this answers your question, please use the "Answer" button to say so | Ben Cline
    • Marked as answer by Racha Rams Tuesday, October 4, 2011 3:23 PM
    Monday, October 3, 2011 4:26 PM
    Moderator