-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revoke-Certificate - Throwing exception Cannot find an appropriate constructor #210
Comments
Adding to my own report I've tried running the same script using module version 3.7.2 and it woks as intended. I have an interim fix and that is perfect but still I would like to troubleshoot this in 4.2.0 at least to isolate what is causing it. |
You can try this script if you like: https://github.com/hmiller10/PowerShell-Tidbits/blob/main/PKI/OperationsScripts/Revoke-APkiCertificate.ps1 |
Thanks but the logic to revoke cert is already in place it is just the cmdlet throwing the exception I've reported, I've now been able to fix the issue so I?m kind of set but still would like to go to the bottom of this to understamd |
I've tried to repro the issue by attempting to generate both, successful and unsuccessful responses and it works fine for me in 4.2.0:
|
I faced the same issue and found that when I ran the script on the certification authority without adminrights it will show this error. That totally makes sense, the resulting error is just quite confusing. |
Hello,
I've tried to find something but could not find anything close to what I'm experiencing when trying to use the Revoke-Certificate cmdlet the following exception is being thrown:
As it is stated in the exception message module version in use is 4.2.0, I did not have the time to properly debug the whole thing but exception is being thrown at line 49 of the Revoke-Certificate function where code reads:
I will try to find some time to further troubleshoot this but if someone experienced this issue or has any pointer I would really appreciate it.
The text was updated successfully, but these errors were encountered: