We are using gpg4win on Windows servers for enterprise batch processing. We have problems after the server has been rebooted where the batch jobs, which normally run without issue, start failing with the following error:
gpg: can’t connect to the gpg-agent: IPC connect call failed
If I run gpg-connect-agent -v at the command line it usually starts the agent and things are fine after that. However, sometimes I have to run gpg-connect-agent -v twice to get the agent to start.
Is there some way (creating a Windows service for the agent?) to ensure the agent is up and running after a reboot?