From some of the newsgroup postings that we found, this error seems to be related to lack of proper rights or file corruption.
If this error occurs in conjunction with an IIS-based website, see this information from ASPFAQ.COM:
"This error is usually due to permissions problems or, in rare instances, corruption of the metabase. Here are some possible solutions:
- Try removing / re-creating the affected web site(s) / application(s) if your application is running in an isolated process
- Try disabling this feature also try running the application 'out of process'
- Try adding IWAM_MachineName to the web site operators, and giving this account full permissions (using regedt32.exe) to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\MachineKeys\MS IIS DCOM Client. Open regedit.exe, navigate to:
...and delete the subkey 'MS IIS DCOM Client', then open the MMC console for IIS (which will re-create the subkey)
If all else fails, try reinstalling IIS - this will rebuild your metabase, but will require you to configure your web site(s) from scratch
* * *
This error seems to affect many users of asp pages with CDONTS. Here are some suggestions for them:
From a newsgroup post: After backing up the key (select the registry key and save it), remove HKCU\software\Microsoft\cryptography\userkeys\MS_IIS_DCOM_CLIENT.
From a newsgroup post: To fix this, I had to click the properties of the site, go to home dir, click REMOVE in the configuration section and re-created it.
From a newsgroup post: The problem is that access to the IIS Admin Objects is made in the context of the process token. For Out of Process IIS applications that process is token is for the IWAM_machinename account. By default, the IWAM_machinename account is not a web site operator and does not have permissions to certain registry keys required for access to the IIS Admin Objects.
You can get around this problem by adding the IWAM_machinename account to
the web site operators and then you must also give the account full permissions
to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\MachineKeys\MS IIS
DCOM Client registry key. Permissions cannot be set with REGEDIT.EXE. You should use REGEDT32.EXE instead. You may not want to give the IWAM_machinename account these sorts of permissions to your metabase for security reasons. You can accomplish the same results by configuring the MTS package for your Out of Process application to run as a different user than the IWAM_machinename account. You would then need to give this different user the permissions mentioned above.
Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.
Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.