What is the definitive situation with BizTalk 2002 and different
document encodings?

We are starting to use BizTalk 2004 and our first outbound document to
a BizTalk 2002 partner failed with:

[0x1439] No parser component recognizes the data. This might be caused
by an interchange specification that is missing or not valid, or it
might be caused by data that is not valid. Verify that both the
interchange specification (if one is specified) and the data match.

The outbound document uses the default XML pipeline and appears to be
UTF-16 with a byte order mark.

I tried configuring a custom pipeline with ASCII as the target charset
but that didn't work.  After removing the XML declaration BizTalk 2002
can read the document.

Is there a way to configure BizTalk 2002 so that it can receive a
document from BizTalk 2004 without writing a pipeline?  Does BizTalk
2002 read the XML declaration header and / or the byte order mark to
determine the document encoding?

Thanks for an enlightenment.

Michael

[ Post a follow-up to this message ]

Hi

All I can say is that I have had the same problem, and removing the
"encoding="-tag solved the problem. You BizTalk 2004 mapper can be set
to not put the xml decleration-tag in the output.

Jan Eliasen

On Tue, 29 Jun 2004 16:32:02 -0400, Michael <Michael@xyzzy.com> wrote:

>What is the definitive situation with BizTalk 2002 and different
>document encodings?
>
>We are starting to use BizTalk 2004 and our first outbound document to
>a BizTalk 2002 partner failed with:
>
>[0x1439] No parser component recognizes the data. This might be caused
>by an interchange specification that is missing or not valid, or it
>might be caused by data that is not valid. Verify that both the
>interchange specification (if one is specified) and the data match.
>
>The outbound document uses the default XML pipeline and appears to be
>UTF-16 with a byte order mark.
>
>I tried configuring a custom pipeline with ASCII as the target charset
>but that didn't work.  After removing the XML declaration BizTalk 2002
>can read the document.
>
>Is there a way to configure BizTalk 2002 so that it can receive a
>document from BizTalk 2004 without writing a pipeline?  Does BizTalk
>2002 read the XML declaration header and / or the byte order mark to
>determine the document encoding?
>
>Thanks for an enlightenment.
>
>Michael

--
Jan Eliasen, representing himself and not the company he works for.

[ Post a follow-up to this message ]

I haven't ran into this myself so-far but I'll check and see what
information I can find on this.

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| From: Michael <Michael@xyzzy.com>
| Subject: BizTalk 2002 - XML Declaration - Unicode
| Date: Tue, 29 Jun 2004 16:32:02 -0400
| Reply-To: Michael@xyzzy.com
| Message-ID: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
| X-Newsreader: Forte Agent 1.93/32.576 English (American)
| MIME-Version: 1.0
| Content-Type: text/plain; charset=us-ascii
| Content-Transfer-Encoding: 7bit
| Newsgroups: microsoft.public.biztalk.general
| NNTP-Posting-Host: pow229159.columbus.rr.com 204.210.229.159
| Lines: 1
| Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP0
8.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16593
| X-Tomcat-NG: microsoft.public.biztalk.general
|
| What is the definitive situation with BizTalk 2002 and different
| document encodings?
|
| We are starting to use BizTalk 2004 and our first outbound document to
| a BizTalk 2002 partner failed with:
|
| [0x1439] No parser component recognizes the data. This might be caused
| by an interchange specification that is missing or not valid, or it
| might be caused by data that is not valid. Verify that both the
| interchange specification (if one is specified) and the data match.
|
| The outbound document uses the default XML pipeline and appears to be
| UTF-16 with a byte order mark.
|
| I tried configuring a custom pipeline with ASCII as the target charset
| but that didn't work.  After removing the XML declaration BizTalk 2002
| can read the document.
|
| Is there a way to configure BizTalk 2002 so that it can receive a
| document from BizTalk 2004 without writing a pipeline?  Does BizTalk
| 2002 read the XML declaration header and / or the byte order mark to
| determine the document encoding?
|
| Thanks for an enlightenment.
|
| Michael
|

[ Post a follow-up to this message ]

In looking at the map I have the Omit XML Declaration property set to
Yes, and the map test does not show a declaration.

However, when I save the transmitted document (it was transmitted
using the default XML pipeline) from Health and Activity Tracking I
see it has a byte order mark and an XML declaration of <?xml
version="1.0" encoding="utf-16"?>

Also, the help says that there is an Encoding property.  I can see an
XSLT Encoding property but it doesn't have an option for ASCII.

On Thu, 01 Jul 2004 12:45:11 +0200, Jan Eliasen <spam@eliasen.dk>
wrote:
[vbcol=seagreen]
>Hi
>
>All I can say is that I have had the same problem, and removing the
>"encoding="-tag solved the problem. You BizTalk 2004 mapper can be set
>to not put the xml decleration-tag in the output.
>
>Jan Eliasen
>
>On Tue, 29 Jun 2004 16:32:02 -0400, Michael <Michael@xyzzy.com> wrote:
> 

[ Post a follow-up to this message ]

Ok, I've reproduced this.  I'll look into it and see what I can find.

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| From: Michael <Michael@xyzzy.com>
| Subject: BizTalk 2002 - XML Declaration - Unicode
| Date: Tue, 29 Jun 2004 16:32:02 -0400
| Reply-To: Michael@xyzzy.com
| Message-ID: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
| X-Newsreader: Forte Agent 1.93/32.576 English (American)
| MIME-Version: 1.0
| Content-Type: text/plain; charset=us-ascii
| Content-Transfer-Encoding: 7bit
| Newsgroups: microsoft.public.biztalk.general
| NNTP-Posting-Host: pow229159.columbus.rr.com 204.210.229.159
| Lines: 1
| Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP0
8.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16593
| X-Tomcat-NG: microsoft.public.biztalk.general
|
| What is the definitive situation with BizTalk 2002 and different
| document encodings?
|
| We are starting to use BizTalk 2004 and our first outbound document to
| a BizTalk 2002 partner failed with:
|
| [0x1439] No parser component recognizes the data. This might be caused
| by an interchange specification that is missing or not valid, or it
| might be caused by data that is not valid. Verify that both the
| interchange specification (if one is specified) and the data match.
|
| The outbound document uses the default XML pipeline and appears to be
| UTF-16 with a byte order mark.
|
| I tried configuring a custom pipeline with ASCII as the target charset
| but that didn't work.  After removing the XML declaration BizTalk 2002
| can read the document.
|
| Is there a way to configure BizTalk 2002 so that it can receive a
| document from BizTalk 2004 without writing a pipeline?  Does BizTalk
| 2002 read the XML declaration header and / or the byte order mark to
| determine the document encoding?
|
| Thanks for an enlightenment.
|
| Michael
|

[ Post a follow-up to this message ]

Followup posting.

From my testing, if I save to file from BizTalk 2004 and then use a file
receive function to read in this data this appears to work fine.  However
if I try to submit this data as a string it fails.
I'm assuming that you are sending over HTTP?  On my machine the data is
sent in UTF-8 encoding with byte order mark and the XML declaration set to
UTF-8.  I was able to get BizTalk 2004 to send the data as ASCII by
creating a pipeline and setting the target charset to ASCII.  This appears
to be received fine on the BizTalk 2002 side.  I also disabled XML
declaration generation in the XML assembler component in my pipeline.

On the BizTalk 2002 side you could possibly resolve this by receiving the
data in an .asp page and modifying the data format before submitting to
BizTalk 2002.

I'm still investigating this as it is often desirable to send the document
in UTF-8 since this allows encoding of non-english character sets.
Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| X-Tomcat-ID: 620745903
| References: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: larryfr@online.microsoft.com ("larry franks")
| Organization: Microsoft
| Date: Thu, 01 Jul 2004 21:16:55 GMT
| Subject: RE: BizTalk 2002 - XML Declaration - Unicode
| X-Tomcat-NG: microsoft.public.biztalk.general
| Message-ID: <7p28SJ7XEHA.3316@cpmsftngxa06.phx.gbl>
| Newsgroups: microsoft.public.biztalk.general
| Lines: 54
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16718
| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
|
| Ok, I've reproduced this.  I'll look into it and see what I can find.
|
| Larry Franks
|
| This posting is provided "AS IS" with no warranties,and confers no
rights.
| Subscribe at
|
http://support.microsoft.com/defaul...msdn/nospam.asp
| &SD=msdn
| --------------------
| | From: Michael <Michael@xyzzy.com>
| | Subject: BizTalk 2002 - XML Declaration - Unicode
| | Date: Tue, 29 Jun 2004 16:32:02 -0400
| | Reply-To: Michael@xyzzy.com
| | Message-ID: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
| | X-Newsreader: Forte Agent 1.93/32.576 English (American)
| | MIME-Version: 1.0
| | Content-Type: text/plain; charset=us-ascii
| | Content-Transfer-Encoding: 7bit
| | Newsgroups: microsoft.public.biztalk.general
| | NNTP-Posting-Host: pow229159.columbus.rr.com 204.210.229.159
| | Lines: 1
| | Path:
|
cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP0
| 8.phx.gbl!TK2MSFTNGP09.phx.gbl
| | Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16593
| | X-Tomcat-NG: microsoft.public.biztalk.general
| |
| | What is the definitive situation with BizTalk 2002 and different
| | document encodings?
| |
| | We are starting to use BizTalk 2004 and our first outbound document to
| | a BizTalk 2002 partner failed with:
| |
| | [0x1439] No parser component recognizes the data. This might be caus
ed
| | by an interchange specification that is missing or not valid, or it
| | might be caused by data that is not valid. Verify that both the
| | interchange specification (if one is specified) and the data match.
| |
| | The outbound document uses the default XML pipeline and appears to be
| | UTF-16 with a byte order mark.
| |
| | I tried configuring a custom pipeline with ASCII as the target charset
| | but that didn't work.  After removing the XML declaration BizTalk 2002
| | can read the document.
| |
| | Is there a way to configure BizTalk 2002 so that it can receive a
| | document from BizTalk 2004 without writing a pipeline?  Does BizTalk
| | 2002 read the XML declaration header and / or the byte order mark to
| | determine the document encoding?
| |
| | Thanks for an enlightenment.
| |
| | Michael
| |
|
|

[ Post a follow-up to this message ]

Larry,

Yes, we are using HTTP - but ours was coming out UTF-16.  We captured
the raw data from an ASP page.

The only way we have been able to get this to work is to use a
pipeline with the charset to ASCII and disabling the XML declaration
as you have done.

The only thing we tried on the ASP side was to properly detect the
content type and use an ADO Stream object to convert the data from
binary to the appropriate text type.  We then submit it to MSMQ.

In my mind the big deal here is that you have to know to create a
pipeline and make these changes just to get BizTalk 2004 to talk to
BizTalk 2002 out of the box.  It seems it is not very backward
compatible.

Michael

On Wed, 07 Jul 2004 17:11:04 GMT, larryfr@online.microsoft.com ("larry
franks") wrote:

>Followup posting.
>
>From my testing, if I save to file from BizTalk 2004 and then use a file
>receive function to read in this data this appears to work fine.  However
>if I try to submit this data as a string it fails.
>I'm assuming that you are sending over HTTP?  On my machine the data is
>sent in UTF-8 encoding with byte order mark and the XML declaration set to
>UTF-8.  I was able to get BizTalk 2004 to send the data as ASCII by
>creating a pipeline and setting the target charset to ASCII.  This appears
>to be received fine on the BizTalk 2002 side.  I also disabled XML
>declaration generation in the XML assembler component in my pipeline.
>
>On the BizTalk 2002 side you could possibly resolve this by receiving the
>data in an .asp page and modifying the data format before submitting to
>BizTalk 2002.
>
>I'm still investigating this as it is often desirable to send the document
>in UTF-8 since this allows encoding of non-english character sets.
>Larry Franks
>
>This posting is provided "AS IS" with no warranties,and confers no rights.
>Subscribe at
>[url]http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp[/url
]
>&SD=msdn
>--------------------
>| X-Tomcat-ID: 620745903
>| References: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
>| MIME-Version: 1.0
>| Content-Type: text/plain
>| Content-Transfer-Encoding: 7bit
>| From: larryfr@online.microsoft.com ("larry franks")
>| Organization: Microsoft
>| Date: Thu, 01 Jul 2004 21:16:55 GMT
>| Subject: RE: BizTalk 2002 - XML Declaration - Unicode
>| X-Tomcat-NG: microsoft.public.biztalk.general
>| Message-ID: <7p28SJ7XEHA.3316@cpmsftngxa06.phx.gbl>
>| Newsgroups: microsoft.public.biztalk.general
>| Lines: 54
>| Path: cpmsftngxa06.phx.gbl
>| Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16718
>| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
>|
>| Ok, I've reproduced this.  I'll look into it and see what I can find.
>|
>| Larry Franks
>|
>| This posting is provided "AS IS" with no warranties,and confers no
>rights.
>| Subscribe at
>|
>[url]http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp[/url
]
>| &SD=msdn
>| --------------------
>| | From: Michael <Michael@xyzzy.com>
>| | Subject: BizTalk 2002 - XML Declaration - Unicode
>| | Date: Tue, 29 Jun 2004 16:32:02 -0400
>| | Reply-To: Michael@xyzzy.com
>| | Message-ID: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
>| | X-Newsreader: Forte Agent 1.93/32.576 English (American)
>| | MIME-Version: 1.0
>| | Content-Type: text/plain; charset=us-ascii
>| | Content-Transfer-Encoding: 7bit
>| | Newsgroups: microsoft.public.biztalk.general
>| | NNTP-Posting-Host: pow229159.columbus.rr.com 204.210.229.159
>| | Lines: 1
>| | Path:
>|
>cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP
0
>| 8.phx.gbl!TK2MSFTNGP09.phx.gbl
>| | Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16593
>| | X-Tomcat-NG: microsoft.public.biztalk.general
>| |
>| | What is the definitive situation with BizTalk 2002 and different
>| | document encodings?
>| |
>| | We are starting to use BizTalk 2004 and our first outbound document to
>| | a BizTalk 2002 partner failed with:
>| |
>| | [0x1439] No parser component recognizes the data. This might be cau
sed
>| | by an interchange specification that is missing or not valid, or it
>| | might be caused by data that is not valid. Verify that both the
>| | interchange specification (if one is specified) and the data match.
>| |
>| | The outbound document uses the default XML pipeline and appears to be
>| | UTF-16 with a byte order mark.
>| |
>| | I tried configuring a custom pipeline with ASCII as the target charset
>| | but that didn't work.  After removing the XML declaration BizTalk 2002
>| | can read the document.
>| |
>| | Is there a way to configure BizTalk 2002 so that it can receive a
>| | document from BizTalk 2004 without writing a pipeline?  Does BizTalk
>| | 2002 read the XML declaration header and / or the byte order mark to
>| | determine the document encoding?
>| |
>| | Thanks for an enlightenment.
>| |
>| | Michael
>| |
>|
>|

[ Post a follow-up to this message ]

Hi Michael, in my case I did a netmon sniff of the traffic to see the utf-8
format, but I may have some other settings that are causing this.

While it would be nice for us to have out of the box compatibility with
sending to prior versions of BizTalk, at that point we'd run into the
reverse of your issue.  There would then be postings with issues where 3rd
party systems were having problems accepting posts from BizTalk 2004 since
they were expecting them in UTF-16 format.  Either way we go we run into a
situation where someone has to create a pipeline to have it work with thier
particular scenario.

I'll continue investigating this and work with our content group to
document the steps needed to get this working with prior versions of
BizTalk.

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| From: Michael <Michael@xyzzy.com>
| Subject: Re: BizTalk 2002 - XML Declaration - Unicode
| Date: Wed, 07 Jul 2004 23:01:09 -0400
| Reply-To: Michael@xyzzy.com
| Message-ID: <uidpe0d71qrpu51p4h42suku58fvcek36u@4ax.com>
| References: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
<7p28SJ7XEHA.3316@cpmsftngxa06.phx.gbl>
<yBqa9bEZEHA.2924@cpmsftngxa06.phx.gbl>
| X-Newsreader: Forte Agent 1.93/32.576 English (American)
| MIME-Version: 1.0
| Content-Type: text/plain; charset=us-ascii
| Content-Transfer-Encoding: 7bit
| Newsgroups: microsoft.public.biztalk.general
| NNTP-Posting-Host: pow229159.columbus.rr.com 204.210.229.159
| Lines: 1
| Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP0
8.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16982
| X-Tomcat-NG: microsoft.public.biztalk.general
|
| Larry,
|
| Yes, we are using HTTP - but ours was coming out UTF-16.  We captured
| the raw data from an ASP page.
|
| The only way we have been able to get this to work is to use a
| pipeline with the charset to ASCII and disabling the XML declaration
| as you have done.
|
| The only thing we tried on the ASP side was to properly detect the
| content type and use an ADO Stream object to convert the data from
| binary to the appropriate text type.  We then submit it to MSMQ.
|
| In my mind the big deal here is that you have to know to create a
| pipeline and make these changes just to get BizTalk 2004 to talk to
| BizTalk 2002 out of the box.  It seems it is not very backward
| compatible.
|
| Michael
|
| On Wed, 07 Jul 2004 17:11:04 GMT, larryfr@online.microsoft.com ("larry
| franks") wrote:
|
| >Followup posting.
| >
| >From my testing, if I save to file from BizTalk 2004 and then use a file
| >receive function to read in this data this appears to work fine.
However
| >if I try to submit this data as a string it fails.
| >I'm assuming that you are sending over HTTP?  On my machine the data is
| >sent in UTF-8 encoding with byte order mark and the XML declaration set
to
| >UTF-8.  I was able to get BizTalk 2004 to send the data as ASCII by
| >creating a pipeline and setting the target charset to ASCII.  This
appears
| >to be received fine on the BizTalk 2002 side.  I also disabled XML
| >declaration generation in the XML assembler component in my pipeline.
| >
| >On the BizTalk 2002 side you could possibly resolve this by receiving
the
| >data in an .asp page and modifying the data format before submitting to
| >BizTalk 2002.
| >
| >I'm still investigating this as it is often desirable to send the
document
| >in UTF-8 since this allows encoding of non-english character sets.
| >Larry Franks
| >
| >This posting is provided "AS IS" with no warranties,and confers no
rights.
| >Subscribe at
|
>http://support.microsoft.com/defaul.../msdn/nospam.as
p
| >&SD=msdn
| >--------------------
| >| X-Tomcat-ID: 620745903
| >| References: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
| >| MIME-Version: 1.0
| >| Content-Type: text/plain
| >| Content-Transfer-Encoding: 7bit
| >| From: larryfr@online.microsoft.com ("larry franks")
| >| Organization: Microsoft
| >| Date: Thu, 01 Jul 2004 21:16:55 GMT
| >| Subject: RE: BizTalk 2002 - XML Declaration - Unicode
| >| X-Tomcat-NG: microsoft.public.biztalk.general
| >| Message-ID: <7p28SJ7XEHA.3316@cpmsftngxa06.phx.gbl>
| >| Newsgroups: microsoft.public.biztalk.general
| >| Lines: 54
| >| Path: cpmsftngxa06.phx.gbl
| >| Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16718
| >| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
| >|
| >| Ok, I've reproduced this.  I'll look into it and see what I can find.
| >|
| >| Larry Franks
| >|
| >| This posting is provided "AS IS" with no warranties,and confers no
| >rights.
| >| Subscribe at
| >|
|
>http://support.microsoft.com/defaul.../msdn/nospam.as
p
| >| &SD=msdn
| >| --------------------
| >| | From: Michael <Michael@xyzzy.com>
| >| | Subject: BizTalk 2002 - XML Declaration - Unicode
| >| | Date: Tue, 29 Jun 2004 16:32:02 -0400
| >| | Reply-To: Michael@xyzzy.com
| >| | Message-ID: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
| >| | X-Newsreader: Forte Agent 1.93/32.576 English (American)
| >| | MIME-Version: 1.0
| >| | Content-Type: text/plain; charset=us-ascii
| >| | Content-Transfer-Encoding: 7bit
| >| | Newsgroups: microsoft.public.biztalk.general
| >| | NNTP-Posting-Host: pow229159.columbus.rr.com 204.210.229.159
| >| | Lines: 1
| >| | Path:
| >|
|
>cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP
0
| >| 8.phx.gbl!TK2MSFTNGP09.phx.gbl
| >| | Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16593
| >| | X-Tomcat-NG: microsoft.public.biztalk.general
| >| |
| >| | What is the definitive situation with BizTalk 2002 and different
| >| | document encodings?
| >| |
| >| | We are starting to use BizTalk 2004 and our first outbound document
to
| >| | a BizTalk 2002 partner failed with:
| >| |
| >| | [0x1439] No parser component recognizes the data. This might be
caused
| >| | by an interchange specification that is missing or not valid, or it
| >| | might be caused by data that is not valid. Verify that both the
| >| | interchange specification (if one is specified) and the data match.
| >| |
| >| | The outbound document uses the default XML pipeline and appears to be
| >| | UTF-16 with a byte order mark.
| >| |
| >| | I tried configuring a custom pipeline with ASCII as the target
charset
| >| | but that didn't work.  After removing the XML declaration BizTalk
2002
| >| | can read the document.
| >| |
| >| | Is there a way to configure BizTalk 2002 so that it can receive a
| >| | document from BizTalk 2004 without writing a pipeline?  Does BizTalk
| >| | 2002 read the XML declaration header and / or the byte order mark to
| >| | determine the document encoding?
| >| |
| >| | Thanks for an enlightenment.
| >| |
| >| | Michael
| >| |
| >|
| >|
|
|

[ Post a follow-up to this message ]

Larry,

It sounds like BizTalk 2002 has problems accepting UTF-8 or UTF-16 or
things with a byte order mark.  To me it is a BizTalk 2002 problem
that should be fixed with a hotfix or service pack.

Thanks for working through the issue.  A KB article for the next guy
would be great.

Michael

On Thu, 08 Jul 2004 14:59:56 GMT, larryfr@online.microsoft.com ("larry
franks") wrote:

>Hi Michael, in my case I did a netmon sniff of the traffic to see the utf-8
>format, but I may have some other settings that are causing this.
>
>While it would be nice for us to have out of the box compatibility with
>sending to prior versions of BizTalk, at that point we'd run into the
>reverse of your issue.  There would then be postings with issues where 3rd
>party systems were having problems accepting posts from BizTalk 2004 since
>they were expecting them in UTF-16 format.  Either way we go we run into a
>situation where someone has to create a pipeline to have it work with thier
>particular scenario.
>
>I'll continue investigating this and work with our content group to
>document the steps needed to get this working with prior versions of
>BizTalk.
>
>Larry Franks
>
>This posting is provided "AS IS" with no warranties,and confers no rights.
>Subscribe at
>[url]http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp[/url
]
>&SD=msdn
>--------------------
>| From: Michael <Michael@xyzzy.com>
>| Subject: Re: BizTalk 2002 - XML Declaration - Unicode
>| Date: Wed, 07 Jul 2004 23:01:09 -0400
>| Reply-To: Michael@xyzzy.com
>| Message-ID: <uidpe0d71qrpu51p4h42suku58fvcek36u@4ax.com>
>| References: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
><7p28SJ7XEHA.3316@cpmsftngxa06.phx.gbl>
><yBqa9bEZEHA.2924@cpmsftngxa06.phx.gbl>
>| X-Newsreader: Forte Agent 1.93/32.576 English (American)
>| MIME-Version: 1.0
>| Content-Type: text/plain; charset=us-ascii
>| Content-Transfer-Encoding: 7bit
>| Newsgroups: microsoft.public.biztalk.general
>| NNTP-Posting-Host: pow229159.columbus.rr.com 204.210.229.159
>| Lines: 1
>| Path:
>cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP
0
>8.phx.gbl!TK2MSFTNGP12.phx.gbl
>| Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16982
>| X-Tomcat-NG: microsoft.public.biztalk.general
>|
>| Larry,
>|
>| Yes, we are using HTTP - but ours was coming out UTF-16.  We captured
>| the raw data from an ASP page.
>|
>| The only way we have been able to get this to work is to use a
>| pipeline with the charset to ASCII and disabling the XML declaration
>| as you have done.
>|
>| The only thing we tried on the ASP side was to properly detect the
>| content type and use an ADO Stream object to convert the data from
>| binary to the appropriate text type.  We then submit it to MSMQ.
>|
>| In my mind the big deal here is that you have to know to create a
>| pipeline and make these changes just to get BizTalk 2004 to talk to
>| BizTalk 2002 out of the box.  It seems it is not very backward
>| compatible.
>|
>| Michael
>|
>| On Wed, 07 Jul 2004 17:11:04 GMT, larryfr@online.microsoft.com ("larry
>| franks") wrote:
>|
>| >Followup posting.
>| >
>| >From my testing, if I save to file from BizTalk 2004 and then use a file
>| >receive function to read in this data this appears to work fine.
>However
>| >if I try to submit this data as a string it fails.
>| >I'm assuming that you are sending over HTTP?  On my machine the data is
>| >sent in UTF-8 encoding with byte order mark and the XML declaration set
>to
>| >UTF-8.  I was able to get BizTalk 2004 to send the data as ASCII by
>| >creating a pipeline and setting the target charset to ASCII.  This
>appears
>| >to be received fine on the BizTalk 2002 side.  I also disabled XML
>| >declaration generation in the XML assembler component in my pipeline.
>| >
>| >On the BizTalk 2002 side you could possibly resolve this by receiving
>the
>| >data in an .asp page and modifying the data format before submitting to
>| >BizTalk 2002.
>| >
>| >I'm still investigating this as it is often desirable to send the
>document
>| >in UTF-8 since this allows encoding of non-english character sets.
>| >Larry Franks
>| >
>| >This posting is provided "AS IS" with no warranties,and confers no
>rights.
>| >Subscribe at
>| 
>p
>| >&SD=msdn
>| >--------------------
>| >| X-Tomcat-ID: 620745903
>| >| References: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
>| >| MIME-Version: 1.0
>| >| Content-Type: text/plain
>| >| Content-Transfer-Encoding: 7bit
>| >| From: larryfr@online.microsoft.com ("larry franks")
>| >| Organization: Microsoft
>| >| Date: Thu, 01 Jul 2004 21:16:55 GMT
>| >| Subject: RE: BizTalk 2002 - XML Declaration - Unicode
>| >| X-Tomcat-NG: microsoft.public.biztalk.general
>| >| Message-ID: <7p28SJ7XEHA.3316@cpmsftngxa06.phx.gbl>
>| >| Newsgroups: microsoft.public.biztalk.general
>| >| Lines: 54
>| >| Path: cpmsftngxa06.phx.gbl
>| >| Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16718
>| >| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
>| >|
>| >| Ok, I've reproduced this.  I'll look into it and see what I can find.
>| >|
>| >| Larry Franks
>| >|
>| >| This posting is provided "AS IS" with no warranties,and confers no
>| >rights.
>| >| Subscribe at
>| >|
>| 
>p
>| >| &SD=msdn
>| >| --------------------
>| >| | From: Michael <Michael@xyzzy.com>
>| >| | Subject: BizTalk 2002 - XML Declaration - Unicode
>| >| | Date: Tue, 29 Jun 2004 16:32:02 -0400
>| >| | Reply-To: Michael@xyzzy.com
>| >| | Message-ID: <euj3e0d9m6nm9cle2jgn49n2ahjelp5n0t@4ax.com>
>| >| | X-Newsreader: Forte Agent 1.93/32.576 English (American)
>| >| | MIME-Version: 1.0
>| >| | Content-Type: text/plain; charset=us-ascii
>| >| | Content-Transfer-Encoding: 7bit
>| >| | Newsgroups: microsoft.public.biztalk.general
>| >| | NNTP-Posting-Host: pow229159.columbus.rr.com 204.210.229.159
>| >| | Lines: 1
>| >| | Path:
>| >|
>| 
>0
>| >| 8.phx.gbl!TK2MSFTNGP09.phx.gbl
>| >| | Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:16593
>| >| | X-Tomcat-NG: microsoft.public.biztalk.general
>| >| |
>| >| | What is the definitive situation with BizTalk 2002 and different
>| >| | document encodings?
>| >| |
>| >| | We are starting to use BizTalk 2004 and our first outbound document
>to
>| >| | a BizTalk 2002 partner failed with:
>| >| |
>| >| | [0x1439] No parser component recognizes the data. This might be
>caused
>| >| | by an interchange specification that is missing or not valid, or it
>| >| | might be caused by data that is not valid. Verify that both the
>| >| | interchange specification (if one is specified) and the data match.
>| >| |
>| >| | The outbound document uses the default XML pipeline and appears to b
e
>| >| | UTF-16 with a byte order mark.
>| >| |
>| >| | I tried configuring a custom pipeline with ASCII as the target
>charset
>| >| | but that didn't work.  After removing the XML declaration BizTalk
>2002
>| >| | can read the document.
>| >| |
>| >| | Is there a way to configure BizTalk 2002 so that it can receive a
>| >| | document from BizTalk 2004 without writing a pipeline?  Does BizTalk
>| >| | 2002 read the XML declaration header and / or the byte order mark to
>| >| | determine the document encoding?
>| >| |
>| >| | Thanks for an enlightenment.
>| >| |
>| >| | Michael
>| >| |
>| >|
>| >|
>|
>|

[ Post a follow-up to this message ]