Cryptographic Failure While Signing Assembly While Building BizTalk Solution
I encountered a peculiar error while building an existing BizTalk 2010 Visual Studio solution in a new BizTalk 2010 development environment.
Cryptographic failure while signing assembly ‘assembly name here’ — ‘Access is denied. ‘
This error appeared while trying to sign a .NET assembly with a strong name key file. The cause for this error is pretty obvious as being a permissions error, however, permission error where? In this case, the error is caused by the current user not having ‘full control’ to the following folder “C:\ProgramData\Microsoft\Crypto\RSA\MachineKey”. This will grant Visual Studio with permission to sign with the strong key. For good measure, I would also suggest assigning the same rights to the BizTalk Server Administrators group, as any developer should also be part of that group.