- This topic has 6 replies, 1 voice, and was last updated 8 years, 3 months ago by
.
-
Posts
-
-
I am trying to develop a receive port using the SQL adaptor and a procedure call. I have gone through the steps to import the result schema and generate the port. When I run it I get a suspended message due to no subscribers found.
The actual suspended message looks correct except it has <?xml version="1.0" encoding="utf-16" ?> as the first element.
Running the message via a FILE adapter gives the same error, but if the utf-16 is removed or changed to utf-8 it works. Likewise the original message does not pass validation due to unicode errors. There seems to be some compatibility setting between BTS and SQL2005 that I am missing. Does anyone know what is forcing the utf-16 encoding? or why BTS does not like it?
thanks.
Doug
-
-
I was copying the message into Notepad and saving it. This changes the format from unicode to ascii.
-
Not exactly sure why SQL2005 is pulling out UTF-16 but BizTalk defaults everything XML into UTF-8. Here's a post about how to change the encoding. We use a pipeline comp to change encoding all the time.
http://geekswithblogs.net/cyoung/archive/2004/07/04/7584.aspx
-
-
-
how do you have solved to create single messages out ouf the multipart document to send them to the sql server?
Regards Roberto
-
I would write a small .NET class that takes in an XLangMessage type and loops thru the message and extracts out the specific message parts that you wish to use. Something like:
(This was done off the top of my head so its probably not 100% correct.)
XmlDocument docPart = XLangMessage.Item("PartName").RetrieveAs(typeof(XmlDocument));
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.