So the -v -k doesn’t do anything but give me information I already know. The version of GPG is the same between old server and new server. The keyring has the same exact keys between the two.
The only odd thing I’ve noticed is that on the old server it was popping the same error but it didn’t disrupt the automated process.
I’m using a SQL Server SSIS package with a VB script task for decryption. On SQL Server 2019 / Windows Server 2012 R2, the package works fine and the file gets decrypted despite the error. On SQL 2019 / Windows Server 2019, the error causes the package to log the file as failed. No matter what I do, I can’t get the package to pop back the error to prove it’s exactly the same one as what I’m seeing in a command prompt.
Still not sure why the old one worked and the new one won’t. This is driving me nuts.