gpg: write failed: ec=87 Error Message?
Marck D Pearlstone
Mon Jun 4 00:18:01 2001
-----BEGIN PGP SIGNED MESSAGE-----
On 03 June 2001 at 09:08:46 -0700 (which was 17:08 where I live)
Nick Andriash wrote to GnuPG Mailing List and made these points:
NA> I have a friend who is using 1.0.6 with Win 2K, and each time GPG
NA> attempts to access a KeyServer to find a Key, GPG returns these
NA> error messages:
NA> gpg: Signature made 06/02/01 08:43:41 using DSA key ID 8232434C
NA> gpg: requesting key 8232434C from keys.pgp.com ...
NA> gpg: write failed: ec=87
NA> gpg: can't get key from keyserver: No such file or directory
NA> gpg: Can't check signature: public key not found
NA> Does anyone know the significance of "ec=87"?
This seems to correspond to an "INVALID PARAMETER" standard Win32
error code. I don't know if that might help with the diagnosis of the
NA> From the above, does it appear the Key has been found, but GPG
NA> cannot write to the Key File, or is GPG having a problem with the
NA> Key Server itself?
>From my POV, this error is happening (in Win2k) without GPG ever going
anywhere near the keyserver. The ec=97 response is instantaneous.
NA> Thanks for your help. There are quite a few people using Win 2K
NA> that are having problems with GPG, despite using Front-End
NA> Programs or Plugins designed by MUA Developers. Would that have
NA> something to do with the fact Win 2K has no underlying DOS?
I would be interested to know. If there is anything I can do to help /
debug / look at ...?
Cheers -- .\\arck D. Pearlstone -- Consultant Software Engineer
\ BrainStorm - free thinking - www: http://www.brainstormsw.com /
\ PGP Key ID: 0x929DCDA0 | www: http://www.silverstones.com /
Don't make me use uppercase.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32)
Comment: GPG Sealed for freshness
-----END PGP SIGNATURE-----