none
EDI Parsing Error (Load) BTS2k16 Virtual Server RRS feed

  • Question

  • I have an 837I Claim File with 5000 claims in it, if I try flowing through my BizTalk 2016 Single Server Installation (2vcpu and 12gb vram) I get parsing errors

    I reduced the number of Claims to 1750 to finally pass the parsing

    I was wondering how can I tweak settings to flow files with 5k claims in it esp in virtual env?

    Thanks


    SV


    • Edited by vai2000 Wednesday, April 3, 2019 7:44 PM
    Wednesday, April 3, 2019 7:43 PM

All replies

  • If you got parsing Errors, then you just removed the invalid Claim.  Nothing to do with the environment.
    Wednesday, April 3, 2019 8:08 PM
  • No Sir, I reduced the no of claims and it works; all are valid claims, If I make it 2000 it fails with message saying Incorrect Subscriber City Name which is correct in the EDI File as a matter of fact this is load test so all are valid records

    if MS can confirm a bloating bug or issue it will be great!

    Thanks


    SV


    • Edited by vai2000 Thursday, April 4, 2019 2:31 PM
    Thursday, April 4, 2019 2:29 PM
  • Well, no.  "Incorrect Subscriber City Name" is in no way a platform issue.

    If there was a platform problem there wold be something in the Event Log from BizTalk Server describing the failure.  Is there any such message?

    Thursday, April 4, 2019 3:03 PM
  • Error encountered during parsing. The X12 transaction set with id '0002' contained in functional group with id '0000002', in interchange with id '082000002', with sender id 'xxx         ', receiver id 'xxx  ' is being suspended with following errors:
    Error: 1 (Field level error)
    SegmentID: N4
    Position in TS: 32689
    Data Element ID: N401_SubscriberCityName
    Position in Segment: 1
    Data Value: B
    4: Data element too short

    Error: 2 (Field level error)
    SegmentID: N4
    Position in TS: 32706
    Data Element ID: N401_SubscriberCityName
    Position in Segment: 1
    Data Value: B
    4: Data element too short

    Error: 3 (Field level error)
    SegmentID: N4
    Position in TS: 32723
    Data Element ID: N401_SubscriberCityName
    Position in Segment: 1
    Data Value: B
    4: Data element too short

    Error: 4 (Field level error)
    SegmentID: N4
    Position in TS: 32740
    Data Element ID: N401_SubscriberCityName
    Position in Segment: 1
    Data Value: B
    4: Data element too short

    Error: 5 (Field level error)
    SegmentID: N4
    Position in TS: 32757
    Data Element ID: N401_SubscriberCityName
    Position in Segment: 1
    Data Value: B
    4: Data element too short

    Error: 6 (Field level error)
    SegmentID: N4
    Position in TS: 32774
    Data Element ID: N401_SubscriberCityName
    Position in Segment: 1
    Data Value: B
    4: Data element too short

    Error: 7 (Field level error)
    SegmentID: N4
    Position in TS: 32791
    Data Element ID: N401_SubscriberCityName
    Position in Segment: 1
    Data Value: B
    4: Data element too short

    Error: 8 (Field level error)
    SegmentID: N4
    Position in TS: 32808
    Data Element ID: N401_SubscriberCityName
    Position in Segment: 1
    Data Value: B
    4: Data element too short

    Its not reading the entire city name which is BOSTON in the file, no where in the file I can see B


    SV

    Thursday, April 4, 2019 5:18 PM