locked
BizTalk - IBM MQ RRS feed

  • Question

  • Hi,

    After installing BizTalk Server 2013 CU3 on our BizTalk server, we are experiencing intermittent connection failure. MQ Series adapter is polling intermittently.

    Any leads?

    Monday, May 23, 2016 7:24 PM

Answers

  • Hi Aditi,

    The receive part of the MQSeries adapter polls the MQSAgent to see if there are messages. When there is a message, the MQSAgent performs an MQGet to retrieve the message. MQSAgent includes a hard-coded three-second wait for retrieving the message from the Queue Manager.

    If you use MQSeries adapter, MQSAgent.dll must be updated on the IBM WebSphere MQ server to the same Cumulative Update level as on BizTalk Server. 

    Make sure that you run the same CU setup on IBM WebSphere MQ Server as well.

    Refer: https://support.microsoft.com/en-gb/kb/3088676


    Rachit Sikroria (Microsoft Azure MVP)

    • Marked as answer by AditiBiz Thursday, May 26, 2016 2:41 PM
    Monday, May 23, 2016 7:32 PM
    Moderator

All replies

  • You need to post the exact error message you're getting.

    Monday, May 23, 2016 7:28 PM
    Moderator
  • Hi John,

    On BizTalk server:

    The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server ..... The target name used was ...... This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain  is different from the client domain check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

    Monday, May 23, 2016 7:31 PM
  • Hi Aditi,

    The receive part of the MQSeries adapter polls the MQSAgent to see if there are messages. When there is a message, the MQSAgent performs an MQGet to retrieve the message. MQSAgent includes a hard-coded three-second wait for retrieving the message from the Queue Manager.

    If you use MQSeries adapter, MQSAgent.dll must be updated on the IBM WebSphere MQ server to the same Cumulative Update level as on BizTalk Server. 

    Make sure that you run the same CU setup on IBM WebSphere MQ Server as well.

    Refer: https://support.microsoft.com/en-gb/kb/3088676


    Rachit Sikroria (Microsoft Azure MVP)

    • Marked as answer by AditiBiz Thursday, May 26, 2016 2:41 PM
    Monday, May 23, 2016 7:32 PM
    Moderator