If you’ve worked with MOSS long enough, I’m sure you’ve seen this error. The reasons that it occurs are numerous, and may even be blamed on poor error handling / reporting by the programmers.
If you’ve come across this error, and turned <customErrors /> off in your MOSS site’s web.config and it still occurs, you may have run into the issue that I did.
This can occur right after MOSS installation, or on a farm that has been up and running for some time, and this is something quick that you can check to make sure it’s not the reason, especially if your server is managed through AD or an admin that is really tight on server security.
My instance of this error was on a completely locked down Windows Server 2008 installation. The cause was one setting that was applied through Active Directory (AD) Group Policy Objects (GPO), Use FIPS compliant algorithms for encryption, hashing, and signing.