none
BizTalk 2010: The Messaging Engine failed to create the receive adapter "MQSC". RRS feed

  • Question

  • Hi all,

    We're trying to configure an MQSC adapter in a new BizTalk 2010 environment on Windows 2k8R2

    We have installed the Microsoft BizTalk Adapters for Host Systems 2.0 to get the adapter and first we try with MQ series Client v7.0.1 and now we're trying with 7.5

    Every minute we receive an error msg:

    The Messaging Engine failed to create the receive adapter "MQSC".
      The Adapter's CLSID is: "{538F8B3D-EE7B-4459-A123-45CD5C3B671B}"
      Reason: "80040154".

    If we try to send an operation

    A message sent to adapter "BiztalkMessagingEngine" on send port "SendXXXTest" with URI "mqsc://SERVERNAME.FROM.XXXXX/tcp/servername.domainname.xx(1416)/XXXXX03/XXX.XXX.FROM_XXX" is suspended.
     Error details: The Messaging Engine failed to create the transport adapter "MQSC".
      The Adapter's CLSID is:"{6811E17F-A4C2-44BB-B4D5-D69962E58E87}"
      Reason:"80040154". 
     MessageId:  {17367EE9-FCC5-45C3-BF39-D4B368AE5C73}

    Can somebody help us?

    Thanx

    Monday, July 30, 2012 10:43 AM

Answers

All replies

  • Do you have the MQ series client installed?
    Monday, July 30, 2012 10:48 AM
  • Hi,

    Yes first we tryed with versión 7.0.1 and now we have installed the MQ series client 7.5 version

    thanks!

    Monday, July 30, 2012 10:53 AM
  • I am unable to get hold of the documentation but I would check for these things

    1)Is the client install version correct, does it need any fix pack etc

    2)Is this a 64 bit instance, if yes I am not sure if they have 64 bit support added in 2010. Couldnt verify becos couldnt find documentation. may be you can try with a 32bit instance also and see unless you know for sure that it has 64 bit support now.

    3)check out transactional property also, that needs some additional dlls.

    Monday, July 30, 2012 11:30 AM
  • One other question that may be relevant; are you using a channel definition file?

    David Downing... If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.

    Tuesday, July 31, 2012 3:56 AM
  • Hi,

    Thanks for reply :)

    No, we don't use the definition file.

    We have specified the Channel name and our transaction Supported is set to NO.

    Must we use the file?

    Regards

    Tuesday, July 31, 2012 6:53 AM
  • Hi, thanks for reply too :)

    On point 3, which transactional property? on MSDTC? or in the adapter properties?

    Regards

    Tuesday, July 31, 2012 6:55 AM
  • In our systems we use a .TAB channel definition file that is created by our WebSphere-MQ administrators.  I've never connected to MQSC without the file.  According to the documentation, it seems it is not required (see the following): http://msdn.microsoft.com/en-us/library/aa772116(v=bts.10).aspx.

    I did notice that the Channel Name, Queue Name and Queue Manager name are case sensitive... did you confirm the cases match?  http://msdn.microsoft.com/en-us/library/aa770469(v=bts.10).aspx and http://msdn.microsoft.com/en-us/library/aa705592(v=bts.10).aspx


    David Downing... If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.

    Tuesday, July 31, 2012 1:06 PM
  • Hello, I've had some issues with WebSphere-MQ client version 7.5 myself, I would recommend 7.1 (never had any issues) however be carefull when Installing it, you do not need everything, I wrote a blog post on how to install it, hope it might help you out.

    Best regards

    Tord Glad Nordahl
    Bouvet ASA, Norway
    http://www.BizTalkAdmin.com |@tordeman

    Please indicate ”Mark as Answer” if this post has answered the question.

    Thursday, August 2, 2012 6:02 AM