We're getting a "PGP Encryption failed. Exit code was 162." Error code 162 is "Complete failure during an encode." Our thinking is around user permissions since users with elevated privileges don't get this error and the encryption works fine. So what I'm really after is an explanation of what the error means and what precisely we should be looking at in order to resolve the issue.
Do the users who get the error have write permissions to in \\SQLSTAGE\MRIAPPS\BOA_PAYMODE\OUTBOX\PGP\? Have the permissions on the folder changed recently or has the group membership of the users changed?
Governments keep a lot of secrets from their people . . . Why aren't the people in return allowed to keep secrets from the government? --Philip Zimmerman, Der Spiegel
Yes, we noticed that, and the users do have permissions to that folder. However, we eventually figured out where the problem was. The issue was that the users needed read/write access to the working directory.
Let me explain. What was missing from my screenshots was:
That was the command that fired the PGP. The users needed read/write access to C:\Program Files\MRI Real Estate Solutions\ as well as the \\SQLSTAGE\...\PGP\ folder. For some reason, PGP 8.5 needs read/write access to the working directory. So we solved the problem by changing the working directory to one that the user had access to.
Comments 7 Comments • Jump to latest comment
This link may be of help:
http://stackoverflow.com/questions/1059723/php-exec-pgp-command
If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.
Search the Knowledge Base
Hi Tom,
It doesnt help. I now get 9000:invalid flag "--temp-dir". My PGP Command Line version is 8.5 and that flag is not supported in that version.
Any other ideas?
Do you have read and write access to the current working directory?
Can you re-run your command with the "--debug --verbose" options, and post the result?
Thanks.
--------
David Finkelstein
Symantec R&D
Hi David,
Here are the results:
Here's an example of what it looks like when it runs properly:
The successful run shows this:
While the unsuccessful one shows:
Do the users who get the error have write permissions to in \\SQLSTAGE\MRIAPPS\BOA_PAYMODE\OUTBOX\PGP\? Have the permissions on the folder changed recently or has the group membership of the users changed?
Governments keep a lot of secrets from their people . . . Why aren't the people in return allowed to keep secrets from the government? --Philip Zimmerman, Der Spiegel
Hi David,
Yes, we noticed that, and the users do have permissions to that folder. However, we eventually figured out where the problem was. The issue was that the users needed read/write access to the working directory.
Let me explain. What was missing from my screenshots was:
That was the command that fired the PGP. The users needed read/write access to C:\Program Files\MRI Real Estate Solutions\ as well as the \\SQLSTAGE\...\PGP\ folder. For some reason, PGP 8.5 needs read/write access to the working directory. So we solved the problem by changing the working directory to one that the user had access to.
I believe that PGP 8.5 wrote its temporary files to the current working directory.
I'm glad you found your solution.
--------
David Finkelstein
Symantec R&D
Would you like to reply?
Login or Register to post your comment.