1 of 1 people found this helpful
Can you please clarify how your job is set up? It seems like the error is pretty specific. Are you trying to transfer a wildcard input to a specific filename at the destination?
It’s a single file being transferred. I’ve noticed in AFT 8.2 it automatically adds double quotes around the recipient variable. I’ve removed the double quotes in the PGP Template, but I’m still seeing the double quotes in the output log. I’m wondering if an agent recycle is required for the updates to take effect?
+********** Starting transfer #1 out of 1**********
Connection to Local server on host Local was established
Connection to SFTP server on host sftp.chronusmentor.com was established
Transfer type: BINARY
Open data connection to retrieve file
Source host 'Local': Using PGP encryption, with Template Name: Chronus_PGP
Execute PGP command: "C:\Program Files\PGP Corporation\PGP Command Line\pgp.exe" --encrypt "
ronus\CoBank_Chronos_Extract.csv" --recipient ""Chronus (Chronus)"" --output "F:\Apps\BMC Software\Control-M Agent\Default\cm\AFT\p\
pgp:encrypt (3028:multiple inputs cannot be sent to a single output file)
Command Exit code '162' doesn't match requested Exit Code '0'
Failed to copy file '
dnntapa\Middleware\Prod\Processing\Chronus\CoBank_Chronos_Extract.csv'. Failed to execute PGP command!
Failed in job IAM_Chronus_FTP in file transfer #1
Can you share a screenshot of the job set up and the pgp template you're using? I'd like to verify a few things. It seems the error you're seeing is from PGP and it looks like the command is thinking you have multiple input files.
What's the encryption parameters for your PGP template?
Should be something similar to this?:
-e --batch -r $$PGP_RECIPIENT$$ -o $$PGP_OUTPUT_FILE$$ $$PGP_INPUT_FILE$$
--encrypt $$PGP_INPUT_FILE$$ --recipient "$$PGP_RECIPIENT$$" --output $$PGP_OUTPUT_FILE$$ --private-keyring
I notice you have double quotes around your $$PGP_RECIPIENT$$ which most likely results in ""Chronus (Chronus)"", also the private-keyring and public-keyring are on a network share correct? is it not recognizing the first two \\ in your UNC?
I was able to figure out the issue, and you’re right the double quotes was the issue. I upgraded my AFT plugin from 8.0 to 8.2.300 and come to find out 8.2 automatically adds double quotes. I removed the double quotes wrapped around the recipient name in the pgp template, reran the job successfully.
Thanks for looking into this for me…much appreciated.
Glad it worked out!