I am getting the exception MQRC_SSL_INITIALIZATION_ERROR
while
connecting to MQ
in
asp.net with c#. I am
using
IBM MQ Client (
9
.
1
.
3
) I am
using
amqmdnet dll (
9
.
1
.
3
)
for
the MQ connectivity. I am connecting on Windows Server
2019
.
Below are the MQ configuration details
<add key=
"
MQ_MANAGER"
value
=
"
HBAX013D"
/>
<add key=
"
MQ_CHANNEL"
value
=
"
DDS.SVR.CONN.SSL.CHL"
/>
<add key=
"
MQ_CONNECTION"
value
=
"
10.10.182.37(1514)"
/>
<add key=
"
MQ_REPLY"
value
=
"
DDS.REPLY"
/>
<add key=
"
MQ_REQUEST"
value
=
"
GEN.DISPATCHER.REQ"
/>
<add key=
"
SSL_ALGORITHM"
value
=
"
RC4_SHA_US"
/>
<add key=
"
SSL_KEYLOCATION"
value
=
"
C:\WMQClient\SSL\key12\key"
/>
What I have tried:
if
(chkSSLEnbled.Checked ==
true
)
MQEnvironment.SSLCipherSpec = txtCipherSpec.Text;
MQEnvironment.SSLKeyRepository = txtKeyRepository.Text;
objMQQueueManager =
new
IBM.WMQ.MQQueueManager(txtMqManager.Text, txtMQChannel.Text, txtMqConnection.Text);
objMQQueue = objMQQueueManager.AccessQueue(txtMQName.Text, MQC.MQOO_INQUIRE | MQC.MQOO_OUTPUT | MQC.MQOO_FAIL_IF_QUIESCING | MQC.MQOO_SET_IDENTITY_CONTEXT);
catch
(Exception ex)
txtLog.Text +=
"
btnConnect_Click()-MQ Connectivity Process Failed with Exception: "
+ ex.Message
+ Environment.NewLine +
"
with Inner Exception:"
+ ex.InnerException
+ Environment.NewLine +
"
at Stack Trace: "
+ ex.StackTrace + Environment.NewLine;
We can't tell - we have no access to your systems to check what might be going on - or any idea what the error details are.
So, it's going to be up to you.
Fortunately, you have a tool available to you which will help you find out what is going on: the debugger. If you don't know how to use it then a quick Google for "Visual Studio debugger" should give you the info you need.
Put a breakpoint on the first line in the function, and run your code through the debugger. Then look at your code, and at your data and work out what should happen manually. Then single step each line checking that what you expected to happen is exactly what did. When it isn't, that's when you have a problem, and you can back-track (or run it again and look more closely) to find out why.
Sorry, but we can't do that for you - time for you to learn a new (and very, very useful) skill: debugging!
Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad
spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or
edit the question
and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it.
Provide an answer or move on to the next question.
Let's work to help developers, not make them feel stupid.
Add code to write to a logfile, and check the file immediately after a crash. Narrow down exactly where the error is happening by focussing your logging info, then start adding variables to it so you can check exactly what you are passing to where.
Sorry, but we can't do any of that for you - you are the only person with access to your server and without that you can't even guess what might be happening.