Recently, we ran into some issues in which the MQSC adapter was not displayed as an option in the BizTalk Administration console, even after the adapter was properly installed on a BizTalk 2009 / Windows 2008 SP1 server. Before outlining the problem and the solution, let’s discuss the MQSC adapter basics first.
MQSC Adapter Basics
The MQSC adapter is only supported running in 32-bit mode on BizTalk 2006 R2, regardless of the operating system being used. On BizTalk 2009 and 2010, the MQSC adapter is supported on Windows 32-bit and Windows 64-bit configurations. In BizTalk 2009, the ability to run in a 64-bit host depends on the version of the IBM Websphere client installed, specifically MQ Client (7.x) or greater. If the goal is to run 64-bit hosts then the 64-bit version of the IBM Websphere client must be installed onto a supported Windows operating system running on a 64-bit processor. For
more information, please follow the installation documentation for the IBM Websphere client and/or the installation documentation for the version of Biztalk being installed.
939202 Update
This update forces the MQSC adapter to run in 32-bit hosts in BizTalk 2006 R2 regardless if the operating system is 32-bit or 64-bit. When 939202 is installed onto any other version of BizTalk (except BizTalk 2006 R2), you may get the “Exception: is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)” exception when running the adapter in 64-bit hosts. Uninstall the 939202 update. If a problems persists, call Microsoft customer support.
MQSC Adapter WMI Installation May Fail
When the MQSC adapter is installed onto BizTalk 2009 / Windows 2008 SP1 (or later SP) or BizTalk 2010 / Windows 2008 R2, it is possible that the WMI install will fail to write the proper registry entries when loading the “Microsoft.BizTalk.Adapter.MQSCAdmin.dll”. The BizTalk MMC console runs as 32-bit MMC.exe process. When the MQSC adapter installation fails, it does not write the correct information to the registry keys used by the MQSC adapter.
To resolve this, add the “MQSC Adapter Class” class information manually into the Wow6432Node node in the registry and then do a repair of the MQSC adapter (again, it is part of the HIS installation). The outline for correcting this problem is as follows:
- Install MQ 7.x or greater and all of the appropriate updates (64-bit version).
- Install BizTalk Host Adapters 2.0 from the HIS 2009/2010 Server media onto the target BizTalk 2009/2010 server.
- Copy the registry information below into a registry file (.reg file) and import it into the HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID key.
- Run the repair for the BizTalk Host Adapters 2.0 from the HIS 2009/2010 Server media (do not skip this step).
- The MQSC adapter should show up in the BizTalk Administration console.
NOTE: Please refer to the appropriate HIS and IBM Websphere client documentation for the most current installation procedures.
REGISTRY ENTRY
“Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to re-install Windows to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.”
|
REGISTRY ENTRY ============= Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{CF8B4D15-5D2B-4c62-90DB-16804D2454B9}] @=”MQSC Adapter Class” “AppID”=”{401D2C40-DAA9-4a63-8D42-9BF98B04F616}” [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{CF8B4D15-5D2B-4c62-90DB-16804D2454B9}\BizTalk] @=”BizTalk” “TransportType”=”MQSC” “Constraints”=dword:00003d0b “ReceiveLocation_PageProv”=”{2DE93EE6-CB01-4007-93E9-C3D71689A280}” “TransmitLocation_PageProv”=”{2DE93EE6-CB01-4007-93E9-C3D71689A282}” “OutboundProtocol_PageProv”=”{2DE93EE6-CB01-4007-93E9-C3D71689A283}” “OutboundEngineCLSID”=”{6811E17F-A4C2-44BB-B4D5-D69962E58E87}” “InboundEngineCLSID”=”{538F8B3D-EE7B-4459-A123-45CD5C3B671B}” “InboundTypeName”=”Microsoft.BizTalk.Adapter.Mqsc.MqscReceiver, Microsoft.BizTalk.Adapter.MQSC, Version=7.0.2300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Custom=null” “InboundAssemblyPath”=”” “OutboundTypeName”=”Microsoft.BizTalk.Adapter.Mqsc.MqscTransmitter, Microsoft.BizTalk.Adapter.MQSC, Version=7.0.2300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Custom=null” “OutboundAssemblyPath”=”” “PropertyNameSpace”=”http://schemas.microsoft.com/BizTalk/2003/mqs-properties“ “ProtocolAlias”=”mqsc://” “ReceiveHandlerPropertiesXML”=”<CustomProps><AdapterConfig vt=\”8\”/></CustomProps>” “SendHandlerPropertiesXML”=”<CustomProps><AdapterConfig vt=\”8\”/></CustomProps>” “ReceiveLocationPropertiesXML”=”<CustomProps><AdapterConfig vt=\”8\”/></CustomProps>” “SendLocationPropertiesXML”=”<CustomProps><AdapterConfig vt=\”8\”/></CustomProps>” “AliasesXML”=”<AdapterAliasList><AdapterAlias>mqsc://</AdapterAlias></AdapterAliasList>” “AdapterMgmtTypeName”=”Microsoft.BizTalk.Adapter.Mqsc.MqscAdapterManagement” “AdapterMgmtAssemblyPath”=”C:\\Program Files (x86)\\Microsoft BizTalk Adapters for Host Systems 2.0\\system\\Microsoft.BizTalk.Adapter.MQSCAdmin.dll” [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{CF8B4D15-5D2B-4c62-90DB-16804D2454B9}\Implemented Categories] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{CF8B4D15-5D2B-4c62-90DB-16804D2454B9}\Implemented Categories\{80D39129-B68D-4f85-98EF- 151A4E1627F7}] @=”” |
NOTE: Confirm that the “AdapterMgmtAssemblyPath” is proper for your installation.
Blog Post by: Dwaine D Gilmer