Re: BTS 2004 Map Error - No Byte Order Mark. Cannot Switch to Unic

Tech-Archive recommends: Fix windows errors by optimizing your registry



I understand the BOM, what I do not understand is why the source document
runs successfully through the orchestration and map in the assembly, but when
I try to use the 'Test Map' feature in Visual Studio with the same source
document I get the error. Each time I 'Test Map', it creates 3 files in
c:\documents and settings\...\local settings\Temp

xsd2edi807.tmp - a message indicating the instance is valid
xsd2edi806.tmp - an intermediate XML representation of the x12 document
(containing all segements, elements, and values) in a unicode format (I know
because it is twice as large as inputfile.xml
inputfile.xml - Contents are the same as xsd2edi806.tmp, but the file is a
regular ascii file.

The XML declaration in both inputfile.xml and xsd2edi806.tmp is
<?xml version="1.0" encoding="UTF-16"?>

"Saravana Kumar" wrote:

> Hello Bill,
>
> This is the general background behind Byte order Mark (aka BOM Character)
>
> In XML, an optional encoding attribute on the XML declaration defines the
> character encoding. The following algorithm determines the default
> encodings:
> If the file starts with a Unicode byte-order mark [0xFF 0xFE] or [0xFE
> 0xFF], the document is considered to be in UTF-16 encoding. Otherwise, it is
> in UTF-8.
>
> You can check the messages coming from Covast EDI adapter to see whether you
> have this BOM character in the beginning.
>
> You won't be able to see it in the file directly, you need to put a TCP
> Trace utility in between and see how this message is different from the
> other working ones.
>
>
> --
> Cheers
> Saravana [MCP - Biztalk Server 2004]
> http://saravanakumarmv.blogspot.com
>
>
> "Bill B" <Bill B@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:712A56B4-A79A-4E7F-9C24-41839247B244@xxxxxxxxxxxxxxxx
> > When I test my map in Visual Studio, I get a BTM1044 Input Validation
> > Error:
> > There is no Unicode Byte Order Mark. Cannot Switch to Unicode. I have
> > successfully validated the source document schema and the instance of the
> > source document I am attempting to test. The source file is a standard
> > x12
> > document and I have tried several different instances of the document -
> > all
> > generate the same error. The schema was generated by the Covast EDI
> > Accelerator, and specifies
> > <?xml version="1.0" encoding="utf-16" ?> (as do all the generated Covast
> > schemas, none of the others are causing a problem, maps test
> > successfully).
> >
> >
> > What am I missing?
> >
> > Thanks,
> >
>
>
>
.



Relevant Pages

  • Re: BTS 2004 Map Error - No Byte Order Mark. Cannot Switch to Unic
    ... I understand what the BOM is - what I do not understand is why I am getting ... I run the source document through my orchestration/assembly ... same version of the map in Visual Studio using 'Test Map' it gets the error. ... an optional encoding attribute on the XML declaration defines the ...
    (microsoft.public.biztalk.general)
  • Re: BTS 2004 Map Error - No Byte Order Mark. Cannot Switch to Unic
    ... I run the source document through my ... > same version of the map in Visual Studio using 'Test Map' it gets the ... > ascii format (not unicode). ... >> This is the general background behind Byte order Mark (aka BOM Character) ...
    (microsoft.public.biztalk.general)
  • BTS 2004 Map Error - No Byte Order Mark. Cannot Switch to Unicode
    ... When I test my map in Visual Studio, I get a BTM1044 Input Validation Error: ... There is no Unicode Byte Order Mark. ... successfully validated the source document schema and the instance of the ...
    (microsoft.public.biztalk.general)
  • Global variable %SourceFileName% to Map?
    ... I think you cannot access the context properties in a Map ... custom receive pipeline and stick it to a field in the ... source document and do a simple mapping it to the dest ... >the file adapter for both the receive and send port. ...
    (microsoft.public.biztalk.general)