A Cryptographic Function Has Failed in ASP.Net

There are two solutions to the problem. The first solution is, naturally, to run your ASP.NET page with the credentials of a domain user. A domain user will have a cryptographic certificate available in Active Directory for the runtime to use for signing. You could do this, for example, using impersonation.

Another solution, as long as you are in a secure environment, is to disable authentication for queued components. Set the COM+ queued component application to have an authentication level of “None”.