Re: Current info for problems start *ADMIN with SSL error?

We are on 7.1. I thought to look under /QIBM but nothing looked
interesting.
i need the *ADMIN server for the latest version of iAccess client, correct?

Thanks

Jack


On Tue, Sep 15, 2015 at 7:49 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

Its saying to check the error log. I can't recall exactly the path that
the ADMIN server stores it's access/error/etc logs in. So you may have

to

do some digging on that (or call IBM and explain the issue if you have
support still...)

The error logs should contain some more defined error codes as to why SSL
can't initialize.

Brad
www.bvstools.com

On Tue, Sep 15, 2015 at 6:15 PM, Jack Tucky <jacktucky@xxxxxxxxx> wrote:

Thanks Brad. This is what I see....

HTP8351 Diagnostic 10 09/15/15 19:14:03.080591

QZSRAPR

QHTTPSVR *STMT QZSRVSSL QHTTPSVR *S
From module . . . . . . . . :
QZSRSNDM
From procedure . . . . . . :
sendMessageToJobLog_CCSID
Statement . . . . . . . . . :

27

To module . . . . . . . . . :
MOD_SSL
To procedure . . . . . . . :
ssl_initializer
Statement . . . . . . . . . :

93

Message . . . . : Secure

Sockets

session failed to initialize successfully.
Cause . . . . . : Secure

Sockets

failed to initialize successfully. Recovery
. . . : Check the error log

to

determine the cause of the failure, and
start the server again.

Technical

description . . . . . . . . : Secure
Sockets failed to initialize
correctly.

There are several errors after that but I think this is the one.

Jack

On Tue, Sep 15, 2015 at 6:12 PM, Bradley Stone <bvstone@xxxxxxxxx>

wrote:

What does the error log and job log say?

Brad
www.bvstools.com

On Tue, Sep 15, 2015 at 4:33 PM, Jack Tucky <jacktucky@xxxxxxxxx>

wrote:

Hi I have several systems that the *ADMIN server won't start

because

of

the

SSL error.

My last google search took me back to 2004? IIIRC.

I'd appreciate some links, or, just do this help.

Thanks,

Frustrated Jack
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.