Re: Problem communicating with HTTP

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hi Leslie,

That message is also known as GSK_NO_KEYFILE_PASSWORD or CPDBCA4.  You 
can type the following command to get a bit more detail:

DSPMSGD CPDBCA4

It seems to imply that a part of your certificate store is missing. 
That would be the part that contains the encrypted password needed to 
access the certificate store.   Maybe it was accidentally deleted?  Or 
maybe you just don't have authority to the password file?

Not sure...  I've never run across this message before.  If you can't 
figure it out, you'll probably have to call IBM for help.



On 5/5/2011 9:29 AM, Goodale, Leslie wrote:
>
>     Here's the http log
>
>
>     HTTPAPI Ver 1.23 released 2008-04-24
>
>     OS/400 Ver V6R1M0
>
>
>     New iconv() objects set, PostRem=819. PostLoc=0. ProtRem=819.
>     ProtLoc=0
>
>     http_persist_open(): entered
>
>     http_long_ParseURL(): entered
>
>     DNS resolver retrans: 2
>
>     DNS resolver retry  : 2
>
>     DNS resolver options: x'00000136'
>
>     DNS default domain: CLAYTON.NET
>
>     DNS server found: 172.16.0.4
>
>     DNS server found: 172.16.0.13
>
>     https_init(): entered
>
>     (GSKit) Object containing the password for the certificate store file
>     not found.
>
>     ssl_error(201): (GSKit) Object containing the password for the
>     certificate store file not found.
>
>     SetError() #24: gsk_env_init: (GSKit) Object containing the password
>     for the certificate store f
>
>     ----------------------------------------------------------------------
>     ---------------
>
>     Dump of local-side certificate information:
>
>     ----------------------------------------------------------------------
>     ---------------
>
>     (GSKit) An operation which is not valid for the current SSL session
>     state was attempted.
>
>     ssl_error(5): (GSKit) An operation which is not valid for the current
>     SSL session state was attempted.
>
>     (GSKit) An operation which is not valid for the current SSL session
>     state was attempted.
>
>
>
>     We've checked the authority to the key database (certificate manager)
>     and everything's there (*PUBLIC Authority).  It works in our
>     development environment as well as our current production
>     environment.  We're testing a new system and that is where it's
>     failing.  Does anyone have any advise?
>
>
>     ____________________________________________________
>
>     Leslie A. Goodale
>
>     Clayton Homes
>
>     IS - Programmer/Analyst  INSURANCE
>
>     (865) 380-3000 ext 5010   Grid 206B
>
>
>
>
>       _________________________________________________________________
>
>     CONFIDENTIALITY NOTICE
>     This message and the accompanying documents contain information that
>     belongs to the sender and may contain information that is privileged,
>     confidential, or exempt from disclosure under applicable law. If the
>     reader of this e-mail is not the intended recipient, you are hereby
>     notified that you are strictly prohibited from reading, disseminating,
>     distributing, copying, or taking action in reliance on the content of
>     this communication. If you have received this e-mail in error, please
>     notify the sender immediately and destroy the original transmission.
>     Thank you.
>
>
>
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------