I am sure a lot of people have had this error, especially seeing as Macromedia released the following technote. http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_17834 But this technote does not solve the problem, it just provides a workaround and a pretty lame one at that. We had this problem ourselves yesterday after transplanting a hard disk into a new server, but I certainly did not want to set all sites to use LOW application protection, as this would result in a very unstable web server that would probably fall over a lot as it doesn't just host CF. And I knew there had to be a proper solution as all these sites worked fine previously on the old server. So I started looking further into the problem and discovered that ASP was having the exact same issue, so it was in fact nothing to do with ColdFusion at all, but rather a problem with IIS. In the system Event Logs, the following type of error was occurring repeatedly. The server failed to load application '/LM/W3SVC/4676/ROOT'. The error was 'No such interface supported A bit of Googling and I worked out this was related to a problem with component services. And low and behold when I tried to open component services I couldn't, getting the following error. Catalog error - An error occurred while processing the last operation: 80040154, Class not registered. So it seemed I needed to re-install component services. Instructions on how to do that can be found here :- http://support.microsoft.com/?id=301919 But still this did not solve my problem, it seemed the IIS packages were not installed. The following are required for IIS to operate properly.

• IIS In-Process Applications
• IIS Out-of-Process Pooled Applications
• IIS Utilities

After a bit more Googling, I found out how to add these packages. Perform the following steps.

1. Open command prompt, navigate to %windir%\system32\inetsrv folder, and enter rundll32 wamreg.dll, CreateIISPackage
2. then regsvr32 asptxn.dll
3. Now type IISRESET at command prompt to restart IIS services, then re-open Component Services MMC to verify the IIS packages are recreated.
4. Reboot server.
I now have everything working again as normal, and no sites had to be set to "LOW" application protection. This solution may not work for you as your problem may be slightly different, but hopefully it will give you an idea where to start Googling. But for god sake don't resort to the Macromedia workaround though.
Views: 348