WACS scheduled task fails return code 2147516570

Help
1

The Let's Encrypt-made scheduled task on a Windows 2016 Essentials box did not renew an SSL. Task Scheduler's "Last Run Result" says:

0x8000809A

And its history ends with:

Task Scheduler successfully completed task ... \2.1.14 x64 pluggable\wacs.exe" with return code 2147516570.

If I run the scheduled task manually I get the same result.

I tried some different things and ended up deleting the certificate and canceling renewals and starting over. wacs.exe did everything normally and I have a new certificate but if I run the (new) scheduled task manually I get the same result.

Additionally if I run a renewal by relaunching wacs.exe manually it works fine, though one line warns me:

Using cached certificate for [IIS] (any site), (any host). To force issue of a new certificate within 1 days, delete the .pfx file from the CertificatePath or run with the --force switch. Be ware that you might run into rate limits doing so.

It runs through the rest of its stuff and ends with

 Next renewal scheduled at 2025/10/14 8:32:00
 Renewal for [IIS] (any site), (any host) succeeded

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

What can that be?

Thanks

2

My only suggestion is to review the credentials for that task. Perhaps some other volunteer with better knowledge of wacs / Windows will offer more help. I am not expert at that.

The primary maintainer of wacs no longer works on that project and instead offers simple-acme: https://simple-acme.com/

You didn't mention what version of wacs you were using. But, you may want to consider switching to simple-acme which is a drop-in replacement.

If no one else offers help here try posting an issue on the wacs (or simple-acme) github.

4 Likes
3

Thank you, that was it of course (or close anyway). The folder was the name of what I had "2.1.14 x64 pluggable", but when I went to download your suggested version I noticed that our software archive had "win-acme.v2.2.9.1701.x64.pluggable", and a note that this one is in use on those boxes. Switching to that worked fine.

Thanks for the clue.

2 Likes
4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.