Skip to main content

SSL Enabled listener does not start when passphrase contains spaces

  • October 19, 2018
  • 0 replies
  • 0 views

Problem:

The HTTPS Echo listener used for SSL and certificates will start if a passphrase is entered manually but not when the same passphrase is used in the mf-server.dat file. 

These are the entries seen in log.html:

  • 2018-08-31 15:04:15.602 [1] GkAddEndpoint: Unable to start listener "HTTPS Echo": CCI returned 6 with error codes 0/183 (0I, 0S): "CCITC32-0075E SSL Configuration error, Password incorrect or Certificate and Keyfiles do not match"
  • 2018-08-31 15:04:15.603 [1] COMMS: communications component error when starting listener "HTTPS Echo"
  • 2018-08-31 15:04:15.603 [1] 3 application listeners started
  • 2018-08-31 15:04:44.648 [1] GkEZSockets: CICS EZ Sockets API emulation layer initialized

 

How can this be addressed?

 

Resolution:

Check for spaces in the passphrase in the mf-server.dat file.

The passphrase in the mf-server.dat file cannot contain spaces. Neither can it be spaces. Neither can this be worked around by enclosing the passphrase in quotation marks.

Currently a passphrase that does not contain spaces must be used.


#MFDS
#EnterpriseDeveloper

0 replies

Be the first to reply!