Forum Replies Created
-
AuthorPosts
-
July 22, 2008 at 6:13 AM in reply to: A way to determine the failing node during routing error #20206
Hey, I found something interesting: The routable NAck Message is way more descriptive than I remembered ! This should make our customer happy. Now I just need to find a trick to synchronise the names of the original file and my NAck. I’ll try routing the messages through an orchestration tomorrow.
Any better ideas ?
Thanks Greg,
I saw that MSDN article before, I think I was just over-complicating my code. For those of you who don’t know, there is a way to check if a Promoted Property exists or not, which is extremely useful in this case:
if(ErrorReport.SendPortName exists msgFailedMessage)
{
emlBody = msgFailedMessage(ErrorReport.SendPortName);
}
else if(ErrorReport.ReceivePortName exists msgFailedMessage)
{
emlBody = msgFailedMessage(ErrorReport.ReceivePortName);
}
Here is an MSDN article, which lists the rest of these awesome operators: http://msdn2.microsoft.com/en-us/library/aa561847.aspx
Hi Nick,
I appreciate your suggestion. but i have one EXE which ll create XML validate against one DTD.
Even when i try create xsd file using Add Generated Item -> Document type -> DTD Schema
It gives me following error.
Error parsing DTD:Value cannot be null.
Parameter name: nameNow I have created that XSD using well-formed XML. Using Add Generated Item
Now when i deployed my project in production. i put one xml file in to receive folder 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’
I have put shipment.dtd in system32 folder but the error is same. problem is in my XML following tag create error
<!DOCTYPE ShipmentTransaction PUBLIC “Shipment” “Shipment.dtd”>.
If i remove this line everything works fine but i cant remove this line as this line as i upload that file on FTP other system need this file with the same formate.
I am not sure. but Is there any poslibility to create one custome pipeline and get xml from there.
Please suggest me any good solution for this problem.
Regards,
– Dhaval M.
July 22, 2008 at 4:13 AM in reply to: A way to determine the failing node during routing error #20203Nick,
thank you very much for your quick reply. It’s what I suspected, but it’s good to be sure. The idea of using a service hits the spot – we have to stay fast as long as no error occurs.
Regards, Michael
July 22, 2008 at 3:36 AM in reply to: SQL Adapter – returning only the first response….not returning all responses #20201Jerry,
Its not often we get Shakespearean language on here!!! (“even though the procedure was called thrice“)
I think you need to provide the SQL that you are executing for us to be able to help further as you appear to have the BizTalk bits working (i.e. you are sending a request message and are receiving a response, only the response is incorrect).
Also, you state that multiple customer Id’s are sent in the request file, but later say that you call the procedure three times – can you clarify how the request is being made and send a copy of the Xml request message so we can see how the Stored Proc is being called.
Cheers, Nick.
July 22, 2008 at 3:26 AM in reply to: A way to determine the failing node during routing error #20200Michael,
I don’t believe there is any way to get this kind of information out of the box with BizTalk because of the way that the disassembler works. However, you could write your own Receive Pipeline component to validate the message against the same schema and use that to provide further information for debugging purposes.
Bear in mind though that you will need to write this in a streaming manner to ensure maximum efficiency (given that you will be processing large files) and you will be duplicating the work (and therefore overhead) of the standard XmlDisassembler.
An easier approach may be to route the failed message to an external directory and write a Windows Service (or exe that is invoked by a scheduled task) that collects ‘failed’ messages and produces a more accurate overview of where the failure is – this will ensure that you have the most efficient BizTalk pipeline and also a detailed error for debug purposes, working on only those messages that have failed validation.
HTH, Nick.
Dhaval,
I would just suggest that you ignore the DTD and get rid of the declaration from the Xml message. IMHO, DTD’s are old technology (super-seeded by XSD’s) and are not used in BizTalk.By all-means create an XSD from the DTD, but then use your XSD exclusively.
Rgds, Nick.
Biztalk does not change the content when it produces the failed message. It is only the message context that is changed.
All the information is in the message context properties:
http://msdn.microsoft.com/en-us/library/aa578516.aspxHi, can you share your trailer schema to me too.
I’m having a similar problem and I want to test if your solution works for me.
Thanks.
HiI Greg…thanks for the response.
My main challenge is that *most* times, the source document will have these values, including valid dates and integers. My map has all points covered as far as providing a link from the source doc to the destination doc. So, I guess I’m looking for a way to make this a little more “dynamic” as in, if there is a value, provide it..otherwise, don’t include the parm and I was hoping I could do this without to many more changes.
Thoughts?
-RichJuly 18, 2008 at 7:19 AM in reply to: how can i configure biztalk on cluster sql server 2005. #20187From the error message (The SQL Server <‘sql01’> cannot be used with the SSO Administrator account ‘SSO Administrators’), it sounds like it is trying to use “SSO Administrators” as the account, whereas “SSO Administrators” sounds like a local group. Are you sure you have entered the correct SSO service account? This service account should be a member of SSO Administrators, but for security reasons, should NOT be a local administrator on any of the servers. However, your logon account to configure BizTalk SHOULD be a local administrator on all of the servers.
Thanks for the reply.
A blog post why not. I think many people would like to know how this is done.
When you map into the SQL message you need to omit the attributes/elements that you wish to be null
i.e.
Assuming a table with 9 columns string1,2,3 date1,2,3 and int1,2,3 and this Xml
<record string1=”data” string3=”” date1=”2008-07-18″ date3=”” int1=”1″ int3=””>the resulting row will be
data, null, ”, 18/7/2008, null, 1/1/1900, 1, null, 0
Hi Toneli, i read that DTC test tool use for making connection testing with remote Microsoft SQL server.
i’m having problem with remote IBM websphere MQ server. So don’t think this tool is suitable.
just to add on, before the password change exercise, both biztalk server had no problem communicating with the IBM websphere MQ server.
When the password change exercise failed, we revert back the old password. And this “A security package specific error occurred.” error disappear. both biztalk server went back to healthy state.
Any idea what else we had miss out?
We did this same password change exercise in our development environment, where there is only 1 server having biztalk host instance and DCOM MQAgent2 service, and remote IBM websphere MQ on another machine.
we had no problem changing these the password for this development environment.
any suggestion is deeply appreciated. Thanks.
You can download and run a DTC test tool from Microsoft to see if that is the cause. We occasionally have this problem when servers are recycled and aren’t powered back up in the right order.
-
AuthorPosts