community-content

Forum Replies Created

Viewing 15 posts - 3,346 through 3,360 (of 9,648 total)
  • Author
    Posts
  • in reply to: Error in Receive port using EDI #21491

    [quote user="xman71"]

    Hi gurus,

        Here’s a good problem for anyone out there to solve. I have configured a receive port with a location that uses default EDI receive pipeline to process a 271 message (X12). I drop the file in the folder and it gets picked up, I check the event log and it shows two error entries:

    First error:

    Error encountered during parsing. The X12 transaction set with id ” contained in functional group with id ‘1’, in interchange with id ‘000195946’, with sender id ‘PC-WEB         ‘, receiver id ‘1803484        ‘ is being suspended with following errors:

    Error: 1 (Miscellaneous error)
     6: Missing or invalid or duplicate Transaction set identifier ‘http://schemas.microsoft.com/BizTalk/EDI/X12/2006/Revs#X12_00401_271’

     

    Second error:

    A message received by adapter “FILE” on receive location “Revs_Rcv271File.FILE” with URI “C:\Depository\Revs_Check\In\inquiry.rcv” is suspended.
     Error details: An output message of the component “Unknown ” in receive pipeline “Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” is suspended due to the following error:
         Unknown .
     The sequence number of the suspended message is 1. 
     MessageId:  {1763948C-F1C8-4765-9730-DEBF351B30DC}
     InstanceID: {67B33E55-7A5F-4FC1-B161-07AA779E73F3}

    Now, in the BizTalk Administration Console, I check the message details associated with the suspended service instance and see the following message body:

    <UnrecognizedSchema><UnrecognizedSegment>ST*271*000195946</UnrecognizedSegment><UnrecognizedSegment>BHT*0022*11*REPW*20081103*105819</UnrecognizedSegment><UnrecognizedSegment>HL*1**20*1</UnrecognizedSegment><UnrecognizedSegment>NM1*PR*2*MASSACHUSETTS MEDICAID*****PI*MASS XIX DMA</UnrecognizedSegment><UnrecognizedSegment>PER*IC*HELP DESK*TE*8004627738</UnrecognizedSegment><UnrecognizedSegment>HL*2*1*21*1</UnrecognizedSegment><UnrecognizedSegment>NM1*1P*2******SV*1803484</UnrecognizedSegment><UnrecognizedSegment>REF*JD*EZELLIS</UnrecognizedSegment><UnrecognizedSegment>REF*EL*PCX020120022P</UnrecognizedSegment><UnrecognizedSegment>HL*3*2*22*0</UnrecognizedSegment><UnrecognizedSegment>NM1*IL*1*FRANKLIN*TANYA****MI*0016819549</UnrecognizedSegment><UnrecognizedSegment>REF*GH*662506109902</UnrecognizedSegment><UnrecognizedSegment>REF*SY*001681954</UnrecognizedSegment><UnrecognizedSegment>N3*15 KANE STREET</UnrecognizedSegment><UnrecognizedSegment>N4*FAIRHAVEN*MA*02719</UnrecognizedSegment><UnrecognizedSegment>DMG*D8*19821006*F</UnrecognizedSegment><UnrecognizedSegment>DTP*307*D8*20081016</UnrecognizedSegment><UnrecognizedSegment>EB*1**30*MC*STANDARD</UnrecognizedSegment><UnrecognizedSegment>EB*U</UnrecognizedSegment><UnrecognizedSegment>LS*2120</UnrecognizedSegment><UnrecognizedSegment>NM1*FA*2*LWO/MEC*****FA*570</UnrecognizedSegment><UnrecognizedSegment>LE*2120</UnrecognizedSegment><UnrecognizedSegment>EB*L</UnrecognizedSegment><UnrecognizedSegment>LS*2120</UnrecognizedSegment><UnrecognizedSegment>NM1*P3*1*DARTMOUTH PRIMARY MEDICINE*DARTMOUTH PRIMARY MEDICIN</UnrecognizedSegment><UnrecognizedSegment>N3*49 STATE RD. WATUPPA BL*SUITE 101-A</UnrecognizedSegment><UnrecognizedSegment>N4*DARTMOUTH*MA*02747</UnrecognizedSegment><UnrecognizedSegment>PER*IC**TE*5089945300</UnrecognizedSegment><UnrecognizedSegment>LE*2120</UnrecognizedSegment><UnrecognizedSegment>EB*F</UnrecognizedSegment><UnrecognizedSegment>MSG*PCC MEMBER. CALL DARTMOUTH PRIMARY MEDICIN-DARTMOUTH PRIMARY MEDICI 5089945300 FOR APPROVAL. FOR EXCEPTIONS SEE 130 CMR 450.118(J)</UnrecognizedSegment><UnrecognizedSegment>EB*F</UnrecognizedSegment><UnrecognizedSegment>MSG*NEW MMIS MEMBER ID – 100030507402</UnrecognizedSegment><UnrecognizedSegment>EB*F</UnrecognizedSegment><UnrecognizedSegment>MSG*FOR MENTAL HEALTH OR SUBSTANCE ABUSE SERVICE AUTHORIZATION CALL THE PARTNERSHIP AT 1-800-495-0086.</UnrecognizedSegment><UnrecognizedSegment>SE*36*000195946</UnrecognizedSegment></UnrecognizedSchema>

    Here are a few notes:

    1) I have deployed a separate X12_00401_271 schema to the application instance, with different namespace and root node name, so there is not conflict in schemas with the default  271 schema.

    2) I have configured the EDI Properties settings for a Global Party so that the Party as Interchange Sender property (under the X12 Properties area) is modified with the X12 Interchange Processing Properties having the Check for Duplicates checkboxes unchecked for all levels (Interchange, Group, Transaction).

    3) I have tried using a custom Receive pipeline for the Receive location, but I still get the same errors.

    4) The 271 message that I use to drop into the folder has the following contents:

    ISA*03*          *01*          *ZZ*PC-WEB         *ZZ*1803484        *081103*1058*U*00401*000195946*0*P*:~GS*HB*MASS XIX DMA*EZELLIS*20081103*1058*1*X*004010X092A1~ST*271*000195946~BHT*0022*11*REPW*20081103*105819~HL*1**20*1~NM1*PR*2*MASSACHUSETTS MEDICAID*****PI*MASS XIX DMA~PER*IC*HELP DESK*TE*8004627738~HL*2*1*21*1~NM1*1P*2******SV*1803484~REF*JD*EZELLIS~REF*EL*PCX020120022P~HL*3*2*22*0~NM1*IL*1*FRANKLIN*TANYA****MI*0016819549~REF*GH*662506109902~REF*SY*001681954~N3*15 KANE STREET~N4*FAIRHAVEN*MA*02719~DMG*D8*19821006*F~DTP*307*D8*20081016~EB*1**30*MC*STANDARD~EB*U~LS*2120~NM1*FA*2*LWO/MEC*****FA*570~LE*2120~EB*L~LS*2120~NM1*P3*1*DARTMOUTH PRIMARY MEDICINE*DARTMOUTH PRIMARY MEDICIN~N3*49 STATE RD. WATUPPA BL*SUITE 101-A~N4*DARTMOUTH*MA*02747~PER*IC**TE*5089945300~LE*2120~EB*F~MSG*PCC MEMBER. CALL DARTMOUTH PRIMARY MEDICIN-DARTMOUTH PRIMARY MEDICI 5089945300 FOR APPROVAL. FOR EXCEPTIONS SEE 130 CMR 450.118(J)~EB*F~MSG*NEW MMIS MEMBER ID – 100030507402~EB*F~MSG*FOR MENTAL HEALTH OR SUBSTANCE ABUSE SERVICE AUTHORIZATION CALL THE PARTNERSHIP AT 1-800-495-0086.~SE*36*000195946~GE*1*1~IEA*1*000195946~

    If anyone can help me resolve this issue (and I’ve been at it for a few days now), I will make sure you get extra brownie points and will advertise your troubleshooting skills up and down this forum and site! 🙂

    Thanks,

    Daniel.

     

    [/quote]

     

    Here’s an update on this issue: I ended up modifying the X12_00401_271 schema to change the target namespace property and redeploying it from my VS project, and it worked like a charm this time. I made sure that the new target namespace is selected in the Interchange Sender property area of my global party.

    Thanks for viewing this post, and I hope my answer will help anyone out there dealing with this issue.

     

    in reply to: Parsing XML and Mapping issue #21488

    I got the Amswer….I got  PO-tripped value using Xpath such as xpath(Msg,”string(Xpath)”);

    Second Using .net component I formed <tripped>9876000000000008374:PART NUMBER BBB:3000;;</tripped>

    <tripped>9876000000000008374:PART NUMBER CCC:4000</tripped> these values.

    in reply to: mapping problem #21486

    Hey guys

    Kindly reply if some one knows that…..[:(]

    in reply to: Long Running Orchestrations and Receive Ports #21484

    Surely this is a common design issue with BizTalk applications right? Does anyone have an example of how they process records in a database?

    in reply to: Long Running Orchestrations and Receive Ports #21482

    I have to control the amount of traffic being sent to third party. I would also have to deal with locking issues in the database so that each process does not grab the same data.

    I appreciate the suggestion but this is not something that I can do.

    in reply to: Long Running Orchestrations and Receive Ports #21481

    How are you getting batches of records, is there any identifier for each batch, if so you can promote that batch number and correlate on it.  In this way you will have an orchestration instance for every batch and each of them run independently.  You need not worry of the 5 min scheduling issue.  Also you guarantee that the same record is not fetched twice by the receive location.

    in reply to: BIZTALK Server 2006 Install Issues #21480

    Did you create the groups?ANd what kind of configuration are you selecting?Basic????

    Please read the document at this URL for further assistance

    https://www.microsoft.com/downloads/details.aspx?familyid=DF2E8A88-FB23-49A4-9AC7-D17F72517D12&displaylang=en

    Cheers

    Sridhar

    in reply to: Long Running Orchestrations and Receive Ports #21479

    In order to create a singleton orchestration use a coorelation set on a property that always has the same value (like the recieve port name).  

     

    in reply to: Question regarding setting up trading partners #21476

    I am not sure I understand how to configure the same AS2 on different partners or how to give different EDI qualifiers. In my understanding that each partner account must have its own AS2 identifier for process the AS2 package, and if you can briefly point out how to configure the alias for EDI qualifiers that will should be able to solve my problem. Basically right now I am thinking if there is a way to create a separate partner account that contains AS2 and other partner accounts for EDI qualifiers, but I am not sure how this is going to work. We have different merchants settings like this:

    PartnerB

    EDI Qualifier: 12: 1234567890E
    AS2 Identifier: PARTNERAS2

    Partner B

    EDI Qualifier: 12: 9876543210E
    AS2 Identifier: PARTNERAS2

    We will need to receive 850 from the merchants and return MDN. Also we will need to send out the 856 to the merchants, but this can be done in the future.

    Any help will be appreciated.

    Thanks,
    Art

    in reply to: SQL adapter #21475

    Hi,

    it could be much more easier to create a copy of sp, with a different name, with the required for xml tags.

    Laszlo

     

    in reply to: SQL Nvarchar(max) #21474

    data is there – its simply hidden by the GUI (I had the same issue with a ~250.000 char long string). Either copy it directly or save the output as a file or report.

    in reply to: SQL adapter #21473

    The FOR XML clause is to generate the schema needed by BizTalk to call the procedure. All the schema has in it is, what to call, what type it is, what to send and what to expect back. After that, it literally makes a TSQL call to the DB.

    if you cant (or dont want to) write the schema up yourself, go to that stored proc and generate a script for it that will allow you to replicate it on a dev server. Add the FOR XML and XMLAUTO clauses and run your wizard against that. Finally, when you are ready to run it against production, change the connection string in the runtime properties on your admin tools and let er rip.

    in reply to: Biztalk capability – New to the product #21472

    Absoultely! as a matter of fact, thats pretty much what BizTalk was designed to do. Now, you can do this is a variety of ways depending on whats on the other end. One way can be to trigger all these events based on files being dropped to certain locations that Biztalk is watching. Another is to use messages, and yet another is to listen to events. Basically, anything you can get data to will work in the adapter stage.

    Think of BizTalk as an Exchange server that has been supercharged and has very few limitations. You can then either route the message as is, send it to several recipients, change the data entirely and send it back, even get a message, trigger a workflow, wait for human intervension then resume from there.

     

    The short answer is “yep”, the suggestion is to read up on BizTalk and decide how deep you want to get into it and how thorough you need your solution to be within it.

     

    in reply to: HAT Problem #21471

    Thats definately a curious scenario, but I will tell you one thing, something must have changed on that day. If you are running SQL 2005, check your logs, schema changes etc for whatever may have been modified. Perhaps a job was turned on that purges the tracking database from that date onwards.

    Also, check your HAT settings and make sure there are no saved queries that filter by that date.

     

    let us know what you find out

    in reply to: Question regarding setting up trading partners #21470

    I think that depends on the particular business scenario; you can set up several alias based on your different IDs in the file. Another solutions would be to create a custom pipeline that does party resolution based on any criteria you need. Now, you may be limited to what is determining your party, in other words, if youre using something like the Covast pipeline components, you have to physically manipulate your files in order to change the parties, etc.

Viewing 15 posts - 3,346 through 3,360 (of 9,648 total)