Article ID: 823425 - Last Review: October 6, 2005 - Revision: 2.2
MSMQ-MQSeries Bridge Pipes Do Not Start When Using SSL
SYMPTOMS
The Microsoft Message Queue Server (MSMQ)-MQSeries Bridge pipes do not start when using Secure Sockets Layer (SSL) encryption. The following error might be logged in the event viewer application log on the MSMQ-MQSeries Bridge server:
Event Type: Error Event Source: MQBridge Event Category: (7) Event ID: 53 Date: 6/13/2003 Time: 3:03:16 AM User: N/A Computer: BRIDGESERVER Description: C:\Program Files\Host Integration Server\system\q2qgw.exe (thread 2116) -> F2QT_Thread: Error in c:\hisbrdg\falconmq\wing\q2q\q2qgw\gwinit.cpp (from Wed Dec 5 19:07:32 2001), line 98 (compiled 17:17:14 on Aug 6 2002) <<Passing it on>> CQ2QChannel::Run: Error in c:\hisbrdg\falconmq\wing\q2q\q2qgw\q2qchnls.cpp (from Wed Dec 5 19:07:33 2001), line 260 (compiled 17:17:16 on Aug 6 2002) <<Passing it on>> CQ2QChannel::PerformRequests: Error in c:\hisbrdg\falconmq\wing\q2q\q2qgw\q2qchnls.cpp (from Wed Dec 5 19:07:33 2001), line 228 (compiled 17:17:16 on Aug 6 2002) <<Passing it on>> CQ2QChannelF2QT::PerformRequest: Error in c:\hisbrdg\falconmq\wing\q2q\q2qgw\q2qchnls.cpp (from Wed Dec 5 19:07:33 2001), line 578 (compiled 17:17:16 on Aug 6 2002) <<Passing it on>> CQ2QMQSeries::CQ2QMQSeries: Error in c:\hisbrdg\falconmq\wing\q2q\q2qgw\q2qmqsr.cpp (from Wed Dec 5 19:07:34 2001), line 85 (compiled 17:17:25 on Aug 6 2002) <<Passing it on>> CQ2QMQSeries::Connect: Error in c:\hisbrdg\falconmq\wing\q2q\q2qgw\q2qmqsr.cpp (from Wed Dec 5 19:07:34 2001), line 124 (compiled 17:17:25 on Aug 6 2002) <<Passing it on>> CQ2QMQSeries::Connect: Error in c:\hisbrdg\falconmq\wing\q2q\q2qgw\q2qmqsr.cpp (from Wed Dec 5 19:07:34 2001), line 124 (compiled 17:17:25 on Aug 6 2002) <<MQSeries call MQCONN failed - error = (1) MQCC_WARNING reason = (957) UNKNOWN.>>
CAUSE
This is a limitation of MSMQ-MQSeries Bridge when it is configured to use SSL encryption.
When multiple threads call the MQCONN function to connect to MQSeries Queue Manager, all the calls except the first call fail with a warning that SSL is already initialized.
RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Host Integration Server Service Pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
--------------------------------------------------------------
23-Jun-2003 12:26 5.64.0.856 37,136 Bcluster.exe
23-Jun-2003 12:26 5.64.0.856 340,240 Explres.dll
30-Apr-1999 15:16 1.28.0.0 144,197 Hotfix.exe
23-Jun-2003 19:13 1,405 Hotfix.ini
23-Jun-2003 12:26 5.64.0.856 65,808 Mqbinst.dll
01-Jan-2003 11:49 4,608 Mqfrgnky.dll
23-Jun-2003 12:26 5.64.0.856 274,704 Q2qcldll.dll
23-Jun-2003 12:26 5.64.0.856 819,472 Q2qexpl.exe
23-Jun-2003 12:26 5.64.0.856 889,104 Q2qgw.exe
23-Jun-2003 12:26 5.64.0.856 33,040 Q2qmsg.dll
01-Jan-2003 11:49 3,817 Q2qperf.ini
23-Jun-2003 12:26 5.64.0.856 348,432 Q2qprfdl.dll
01-Jan-2003 11:49 686 Q2qprfsm.def
23-Jun-2003 12:26 5.64.0.856 327,952 Q2qshdll.dll
23-Jun-2003 12:26 5.64.0.856 41,232 Shdllres.dll
23-Jun-2003 12:26 5.64.0.856 90,384 Wmimqbridge.dll
01-Jan-2003 11:46 6,403 Wmimqbridge.mof
STATUS
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
MORE INFORMATION
If Systems Network Architecture (SNA) Tracing is enabled, you receive the following error in the SNA Trace:
To install the MSMQ-MQSeries Bridge with SSL, follow these steps:
With SSL, do not run the client definition file and remove the define channel command from the server file before you run it on MQSeries.
When you have successfully defined and tested the channel, you can configure the bridge. To configure the bridge, use the channel name that you created. The bridge creates two command files for MQSeries. These definition files are used to create the queues and the channels on MQSeries server. With SSL, do not run the client definition file and do not remove define channel command from the server file before you run it on MQSeries.
06/13/2003 08:04:49:368 _MQCONN(): pszName = QMSERVER, hConn = 9, lCompCode = 1, lReason = 957
Error 957 is MQRC_SSL_ALREADY_INITIALIZED.
Error 957 is MQRC_SSL_ALREADY_INITIALIZED.
To install the MSMQ-MQSeries Bridge with SSL, follow these steps:
- Install the MSMQ-MQSeries Bridge.
Do not configure the MSMQ-MQSeries Bridge. - Apply the hotfix mentioned in this article.
- When you configure the MQSeries channel and configure the certificates store on the bridge computer, log on by using the user account that also run the bridge service. You should also test by using the same user account. Use the MQSeries tools to create the MQI channel that the MQSeries client will use.
- Use the MQSeries samples to test the channel over SSL.
You already have the MQSeries channel name for the bridge. - Configure the MSMQ-MQSeries Bridge by using the channel name that you created in step 3.
Do not export the client definition file. - Export the server definition file.
- Edit the server definition file, and then remove the define channel command.
You created this channel in step 3. - Run the server definition file on the MQSeries server.
- Start the bridge and the pipes.
With SSL, do not run the client definition file and remove the define channel command from the server file before you run it on MQSeries.
When you have successfully defined and tested the channel, you can configure the bridge. To configure the bridge, use the channel name that you created. The bridge creates two command files for MQSeries. These definition files are used to create the queues and the channels on MQSeries server. With SSL, do not run the client definition file and do not remove define channel command from the server file before you run it on MQSeries.
Note: This article is from Microsoft Knowledage Base
How we have helped PC users like you
In the News: Read More In ...
Related problems posted by other users | |
| more... |