Posted: Thu Aug 23, 2007 1:08 am Post subject: SSL between windows and Solaris using MQ5.3
Apprentice
Joined: 15 Jul 2007 Posts: 31
Hello
we are getting the below error while trying to start sender channel on windows after ssl implementation.
All the keydatabase files have been created (.sto on windows and .kdb on solaris) and able to import certificates successfully.
Please see the error below:
************************************************************
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 204.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 671 --------------------------------------------------------
23-8-2007 08:55:59
AMQ9699: An unknown error occurred during an SSL security call during SSL handshaking.
EXPLANATION:
An unknown error occurred during an SSPI call to the Secure Channel (Schannel) SSL provider during SSL handshaking. The error may be due to a Windows SSL problem or to a general Windows problem or to invalid WebSphere MQ data being used in the call. The WebSphere MQ error recording routine has been called. The error has caused WebSphere MQ channel name '????' to be closed. If the name is '????' then the name is unknown.
ACTION:
Consult the Windows Schannel reference manual to determine the meaning of status 0x80090327 (An unknown error occurred while processing the certificate. ) for SSPI call AcceptSecurityContext. If the problem can be resolved using the manual, correct the failure and if necessary re-start the channel. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved. ******************************************************
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
Have you investigated the status code as suggested? What problem does it indicate?
Have you investigated the FDC file which probably accompanies this error? What information does this give you? _________________ Honesty is the best policy.
Insanity is the best defence.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum