more fields in XML structure error in Adapter Monitor

[Former Member]

Hi all

I am getting the following error in the adapter monitor

Error: Message processing failed: Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value ' ')', probably configuration error in file adapter (XML parser error)'

I am using FCC in the rx adapter. I have also checked the fields for any extra fields but there isnt any.

kindly suggest what could be throwing the error

regards

krishna

[bhavesh_kantilal · Accepted solution]

Krishna,

Can you let us know the Content Conversion Parameters and the Inout Source File?

Regards

Bhavesh

[Former Member · Accepted solution]

Bhavesh

It is too big to display. there are so many records and fields

Any takes on the error without those info?

Any guesses?

regards

krishna

[justin_santhanam · Accepted solution]

Krishna,

Thtz fine then, is it possible for u to give the content conversion parameters u used ?

Best regards,

raj.

[bhavesh_kantilal · Accepted solution]

The only issue would be as the error message clearly tells, the number of fields in the File is more than the parameters defined in the Content Conversion in the sender file adapter

Regards

Bhavesh

[Former Member · Accepted solution]

Hi raj

here are the CC parameters.

BEGIN.addHeaderLine 0

BEGIN.fieldFixedLengths 2,1,3,2,4,1,8,12,8,2,307,12,8,12,18

BEGIN.fixedLengthTooShortHandling Ignore

BEGIN.endSeparator '0x0D''0x0A'

CLIENT_RECORD.addHeaderLine 0

CLIENT_RECORD.fieldFixedLengths 2,12,9,4,15,15,4,20,12,9,8,1,1,25,10,1,25,10,1,6,1,1,1,1,1,10,8,1,25,2,1,1,1,106,12,38

CLIENT_RECORD.fixedLengthTooShortHandling Ignore

CLIENT_RECORD.endSeparator '0x0D''0x0A'

RELATION_RECORD.addHeaderLine 0

RELATION_RECORD.fieldFixedLengths 2,12,9,4,20,20,2,2,9,8,1,25,10,1,25,10,1,6,1,1,181,12,38

RELATION_RECORD.fixedLengthTooShortHandling Ignore

RELATION_RECORD.endSeparator '0x0D''0x0A'

ADDRESS_RECORD.addHeaderLine 0

ADDRESS_RECORD.fieldFixedLengths 2,12,9,4,20,20,2,2,5,6,8,24,24,2,35,15,4,15,4,70,8,8,1,50,12,38

ADDRESS_RECORD.fixedLengthTooShortHandling Ignore

ADDRESS_RECORD.endSeparator '0x0D''0x0A'

GIVING_REC.addHeaderLine 0

GIVING_REC.fieldFixedLengths 2,12,9,4,20,9,1,1,1,1,1,1,1,1,1,1,1,1,1,281,12,38

GIVING_REC.fixedLengthTooShortHandling Ignore

GIVING_REC.endSeparator '0x0D''0x0A'

ZIKT_REC.addHeaderLine 0

ZIKT_REC.fieldFixedLengths 2,12,9,4,20,9,2,3,2,8,1,1,277,12,38

ZIKT_REC.fixedLengthTooShortHandling Ignore

ZIKT_REC.endSeparator '0x0D''0x0A'

BEPER_REC.addHeaderLine 0

BEPER_REC.fieldFixedLengths 2,12,9,4,20,9,1,1,1,291,12,38

BEPER_REC.fixedLengthTooShortHandling Cut

BEPER_REC.endSeparator '0x0D''0x0A'

SCORE_BEPER_REC.addHeaderLine 0

SCORE_BEPER_REC.fieldFixedLengths 2,12,9,4,20,9,1,3,4,1,1,284,12,38

SCORE_BEPER_REC.fixedLengthTooShortHandling Ignore

SCORE_BEPER_REC.endSeparator '0x0D''0x0A'

INDBES_REC.addHeaderLine 0

INDBES_REC.fieldFixedLengths 2,12,9,4,20,9,9,2,2,8,8,8,1,256,12,38

INDBES_REC.fixedLengthTooShortHandling Ignore

INDBES_REC.endSeparator '0x0D''0x0A'

FUNCTIONAL_REC.addHeaderLine 0

FUNCTIONAL_REC.fieldFixedLengths 2,12,9,4,20,9,9,3,2,8,8,8,1,4,2,2,1,1,1,1,8,1,1,233,12,38

FUNCTIONAL_REC.fixedLengthTooShortHandling Ignore

FUNCTIONAL_REC.endSeparator '0x0D''0x0A'

ACT_REC.addHeaderLine 0

ACT_REC.fieldFixedLengths 2,12,9,4,20,9,9,3,2,8,3,5,1,263,12,38

ACT_REC.fixedLengthTooShortHandling Ignore

ACT_REC.endSeparator '0x0D''0x0A'

SCORE_REC.addHeaderLine 0

SCORE_REC.fieldFixedLengths 2,12,9,4,20,9,3,4,1,1,285,12,38

SCORE_REC.fixedLengthTooShortHandling Ignore

SCORE_REC.endSeparator '0x0D''0x0A'

ZFUNCTIONAL_REC.addHeaderLine 0

ZFUNCTIONAL_REC.fieldFixedLengths 2,12,9,4,20,9,9,12,3,2,8,8,5,1,8,8,8,4,2,2,1,1,1,1,210,12,38

ZFUNCTIONAL_REC.fixedLengthTooShortHandling Ignore

ZFUNCTIONAL_REC.endSeparator '0x0D''0x0A'

ZACT_REC.addHeaderLine 0

ZACT_REC.fieldFixedLengths 2,12,9,4,20,9,9,3,2,3,5,8,8,5,8,1,242,12,38

ZACT_REC.fixedLengthTooShortHandling Ignore

ZACT_REC.endSeparator '0x0D''0x0A'

COMMENT.addHeaderLine 0

COMMENT.fieldFixedLengths 2,12,4,140,1,191,12,38

COMMENT.fixedLengthTooShortHandling Ignore

COMMENT.endSeparator '0x0D''0x0A'

END_REC.addHeaderLine 0

END_REC.fieldFixedLengths 2,6,6,6,6,6,6,6,6,6,6,6,6,6,6,6,1,257,50

END_REC.fixedLengthTooShortHandling Ignore

END_REC.endSeparator '0x0D''0x0A'

REgards

krishna

[prabhu_s2 · Accepted solution]

had faced a similar issue earlier.....check for the following:

1. no empty nodes in the xml strucutre

2. check with the length specification and see if it is in sync with the field length

[Former Member · Accepted solution]

HI prabhu

Hope you are doing fine

>>>1. no empty nodes in the xml strucutre

Earlier , the CC worked even if there were some empty nodes .

>>2. check with the length specification and see if it is in sync with the field length

should i check each and every field. Given the size of the data, it would be quite cumbersome is there any alternative?:)

regards

krishna

[prabhu_s2 · Accepted solution]

hi krishna....

doing gr8 and am not sure if there are other ways to do it but just check for the fields in all the nodes and compare with the definiton in FCC. may u can also check with the first point.

[Former Member]

any suggestions on the above mentioned issue?

I have check the FCC with the version of FCC that was working. there are no differences. Even the possibilities of error in the input XML to the FCC is very low.

what could be causing the above problem?

any clues ?

Regards

krishna