none
Fatal error encountered in 2XDasm. Exception information is Object reference not set to an instance of an object. RRS feed

  • Question

  • Note: I have had to custom some of the HL7 elements (add extra elements to some NTE's etc).

    It seems that all of a sudden I can no longer import any hl7's from this file location, it continually sends this message.

    My problem is that I have done a ton of orchestration changes, but only to one orch. And I changed some of the 2.2/2.3 segments to conform with the non standard messages, however it was working after I had done this a few times.

    Fatal error encountered in 2XDasm. Exception information is Object reference not set to an instance of an object.

    Any suggestions?  I havent changed any party information.

     


    Mark Rowe \n Admin IrTech.Net
    Monday, January 26, 2009 3:32 PM

All replies

  • Is this an error encountered at compile-time in Visual Studio or at run-time? If it is in Visual Studio you may just need to implement your changes more incrementally and be sure to compile after one or more changes. Sometimes Visual Studio's orchestration generator gets out of sync and needs to be refreshed in pieces.

    Thanks,


    If this answers your question, please use the "Answer" button to say so | Ben Cline
    Monday, January 26, 2009 3:42 PM
    Moderator
  • This happens at runtime only.

    After its been deployed, but the weird thing is.   I only worked on 1 orchestration. and now none of the HL7 messages can be inported even if its a different type like adt or dft etc.

     


    Mark Rowe \n Admin IrTech.Net
    Monday, January 26, 2009 3:46 PM
  • I know that this is not the first choice, but what if you undeployed all of the schemas (and orchestrations) and redeploy the schemas and the orchestraitons again?
    Friday, February 6, 2009 5:25 PM