- This topic has 2 replies, 1 voice, and was last updated 9 years, 3 months ago by
.
-
Posts
-
-
Hi Friends ,
I have deployed my application in production environment but i got following error.
There was a failure executing the receive pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “XML disassembler” Receive Port: “ReceiveNistevoXML” URI: “D:\TestingFolders\ProdData\*.xml” Reason: Could not find file ‘C:\WINDOWS\system32\Shipment.dtd’
After I have pasted my shipment.dtd file in System32 folder but still i m facing same problme.
but If i remove <!DOCTYPE ShipmentTransaction PUBLIC “Shipment” “c:\Shipment.dtd”>
above tag then every thing works fine. but i need to transfer this XML with this tag on FTP.
Can you please guide me to figure out this solution.
Regards,
– Dhaval M
-
Its obviously weird that the BizTalk engine is thinking of looking in c:\Windows\System32 for the DTD file. There must be some executable in the System32 folder that will be used for processing the DTD.
You might try having a send port outbound map be used for adding the DTD DocType line back in.
Thanks,
-
Dhaval,
Repeat with me: DTD’s in BizTalk are bad, waaaaay bad.
I would remove any evidence of DTD’s from messages that are traversing through BizTalk as Xml; if you need to include this tag for delivery to an end system, I would suggest using a simple encoding pipeline component to do the work for you, just before BizTalk passes the message to the FTP Adapter.
Funnily enough, I encountered exactly the same problem on BizTalk 2004 some years ago and wrote a component to do this – see Add DOCTYPE Declaration Encoding Pipeline Component (version 1.0) on the downloads page of my blog.
Bear in mind that this component was written for the .Net 1.1 runtime, so will need to be recompiled for BizTalk 2006.
Rgds, Nick.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.