Solution:
- Check if WCF support is installed for IIS:
- If you are using certificate, check if application pool have access permissions for private key. To provide access permissions do:
- Find IIS application pool identity
- Find private key file name for certificate (FindPrivateKey.exe):
- Add read permissions for IIS application pool identity (cacls.exe) or just open windows explorer and set permissions
2 comments:
Thanks, your pic of IIS and the application pools gave me the idea to change the Identity to "NetworkService", and I then went and gave the Network Service account permissions to access the keyset (in C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys), then this error went away. Thanks, saved me hours of pain! :)
Great! I spent a lot of time search this.
Post a Comment