- This topic has 8 replies, 1 voice, and was last updated 9 years ago by
.
-
Posts
-
-
Hi All,
I am facing some problem in a solution i developed where i get employee vouchers from SQL ..then in Pipeline i do debatching of Messages..as to segregate individual employee messages.Now i send these voucher messages to two way SAP port to park ..in response SAP gives voucher number which i again store in SQL table..Now sometimes i get error at SAP port asThe Messaging Engine received an error from transport adapter “SAP” when notifying the adapter with the BatchComplete event. Reason “Value does not fall within the expected range”or as Time Out ErrorDue to this the messages i got when SQL adapter polled SQL table ..all of these messages gets into Dehydrated State..Now to come out of this i suspend messages and then terminate Orchestration and messages.But as i noticed some of the vouchers gets parked in SAP and there where no response XML ..Only i see all messages go in dehydrated state..Otherwise i do get Response XML..which i store in SQL table..So as i don’t know which vouchers has been parked …i try again resetting status in SQL table so that it can again ready for parking..Could anyone pls help me what would have caused SAP port Error..Pls Advise..
— Regards Sandeep -
Hi Sandeep,
The errors you are getting on your Send port suggest there are issues with the configuration settings on the SAP adapter. Check the following MSDN article on bindings configuration for the BizTalk adapter for SAP:
http://msdn.microsoft.com/en-us/library/dd788572(BTS.10).aspx
Daniel.
-
Hi Daniel,
Thanks for your reply..
A strange behaviour i noticed that when i get above mentioned error at SAP port the request message gets into dehydrated..i guess while sending messages to SAP there could be some problem..
And when i terminate message and reset it in sql table to again send to SAP it parks sucessfully..
Could you pls advise…
-
Hi,
My suggestion would be to have a SAP administrator (if you have one) troubleshoot this issue on the SAP side of things when the message is trying to get through the SAP adapter in BizTalk. Also, you should play around with the settings in the SAP adapter in BizTalk to see if any changes you make would allow the messages to be consumed successfully instead of being dehydrated.
This is my advice to you, and I can’t think of anything else, short of hiring me to help you with the project you are doing (no pun intended).
Daniel.
-
Hi Daniel,
thanks for your reply..
Just a quick question..is when i get above mentioned error and i check BizTalk Admin console i see dehydrated orchestration and Request messages to SAP.. will that mean that messages has not been send due to this error..or messages has been send..
I am little confused as normally when we get error ,we see in event log that description of error with MessageID and InstanceID..
But in this case i only see error and when i check BizTalk Admin Console i see only orchestration and messages in dehydrated state.
Pls Advise its urgent…
Regards
Sandeep
-
Hi Sandeep,
A dehydrated orchestration or message means that it is temporarily stopped until a condition is triggered to allow it to resume processing, so this does not mean that an error occurred (hence the absence of entries in the Application log when you checked the Event Viewer). Dehydration is different from Suspended status, which will indicate an error has occurred and will require manual intervention to either resume or discard the transaction.
In your SAP port, in the Transport Advanced Options tab, you most likely have the Retry Count set to a number above 0, so if your message did not get sent successfully the first time, it will be in a dehydrated state and wait to be resent.
You should investigate the reason why your message(s) are not getting through the SAP port. Does this have something to do with the way you configured your SAP port or the way things are set up on the SAP side that are not in sync with BizTalk? A SAP administrator can also help you troubleshoot this issue…
Daniel.
-
Hi Daniel,
Thanks for your reply..
Just the last question to bother you..
Today again same error came and 5 Orchestration went to dehydrated stage with 5 messages. These messages are SAP request messages..I checked with SAP team they said out of 5 voucher messages 4 got successfully parked and one of them is with error something like “Posting key 31 does not permit specification of a special G/L indicator” which could be specific to application..Now there is no response XML for the successful vouchers so that l can send them to SQL port to execute Stored Procedure to store voucher number..Could you please advise ..how SAP adapter had send messages to SAP with no response XML..This happens only to those vouchers in batches in which one or more vouchers are having error mentioned above as“Posting key 31 does not permit specification of a special G/L indicator”otherwise the application is running smoothly..I read in msdn that BizTalk SAP adapter works in a batch fashion ..it means it groups messages in batch and this batch is related to one transaction ..so if suppose there are 5 messages in batch and one of the message has some problem then ..whole lot of message transaction will fail and we need to retry..Could you please advise when the transaction fails do there is any chance that other messages might have posted request XML to SAP..Pls Advise..RegardsSandeep-
Hi Sandeep,
First of all, check the schema of your messages (that was generated using the Add Generated Items wizard in Visual Studio) to make sure that it contains both a request and response nodes.
Secondly, I am not sure if you can configure the SAP Send port or the SAP adapter to not batch your messages, but you can check out the following MSDN forum thread for clues (see in particular the last post by Rohit Singh):
Finally, consult this MSDN article to implement a Reliable Message Delivery scenario:
http://technet.microsoft.com/en-us/library/cc948789(BTS.10).aspx
I apologize if I am not able to give your more insight or implementation details, since I have not worked with SAP adapters.
Daniel.
-
-
-
-
-
-
-
The new adapter(BizTalk Adapter Pack) enforces a validation check on the message. It looks like you are trying to send a value that does not conform to the schema that you used. I have seen a situation where Sap was expecting 8 characters, BizTalk sent 10 due a upstream system provide 10 characters and the Adapter suspended the message. I think you have a similar situation.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.