| description | title | ms.date | ms.service | ms.topic |
|---|---|---|---|---|
Learn more about: Troubleshooting Acknowledgments |
Troubleshooting Acknowledgments |
06/08/2017 |
biztalk-server |
article |
Addresses issues related to [!INCLUDEbtaBTAHL71.3abbrevnonumber] acknowledgments.
There are several potential causes for acknowledgments (ACKs) not being generated or received. Review the following list of potential problems.
Acknowledgments are not generated when you update party information in [!INCLUDEbtaBTAHL71.3abbrevnonumber] Configuration Explorer to generate acknowledgments.
Possible cause : [!INCLUDEbtaBTAHL71.3abbrevnonumber] caches and refreshes party configuration information every 15 minutes.
Resolution : Wait for at least 15 minutes for the cache to refresh, or restart [!INCLUDEbtsBizTalkServerNoVersion] for changes to take effect immediately.
[!INCLUDEbtaBTAHL71.3abbrevnonumber] does not generate ACKs and event errors appear in the event log.
Possible cause : An ACK cannot be generated when a batch in/batch out message contains an empty FHS11 field.
Resolution : Ensure that your messages have a correctly formatted and populated FHS11 field.
Your application cannot generate or receive an ACK.
Possible cause : Incorrect information in the MSH3 field of your message prevents [!INCLUDEbtaBTAHL71.3abbrevnonumber] from sending the message ACKs.
Resolution : Ensure that your messages have a correctly formatted and populated MSH3 field.
[!INCLUDEbtaBTAHL71.3abbrevnonumber] sends messages to a two-way adapter without generating acknowledgments.
Possible cause : The message subscription is not configured correctly.
Resolution : Ensure that message subscriptions are present and configured correctly.
Acknowledgments are suspended with the error message "Delimiter found in the field" when you have configured the party to have encoding characters containing delimiter characters such as @-!$.
Possible cause : The message contains characters such as a period (.) or a hyphen (-). When generating the ACKs, [!INCLUDEbtaBTAHL71.3abbrevnonumber] includes "." and "-" for the timestamp value.
Resolution : Disable validation in the send pipeline to avoid these errors.
You get the following or similar error in the Event Log:
"Unable to receive ACK from network due to error "Exception from HRESULT: 0xC0C01662""
Possible cause : You are using 1-way receive and 2-way send port, so BizTalk does not have a corresponding Receive port to return the message received from the 2-way Send port.
Resolution : This is by design, and you can ignore the error message.