Issues caused by MCMS2002 SP1 to SP1a ISAPI filter upgrade

Upgrading a Virtual PC from MCMS2002 SP1 to SP1a added two new ISAPI filters, but didnt unregister old ones, causing issues.

I recently upgraded one of my Virtual PC’s from MCMS2002 SP1 to SP1a. After some flakyness, and a little input from Stefan Goßner, I realized that the SP1a upgrade added two new ISAPI filters, but didn’t unregister the old MCMS 2002 ISAPI filters. This doesn’t happen all the time, it’s just a fluke thing.

It wasn’t documented anywhere that I could find (MS Support, Spencer’s MCMS KB list, Stefan’s FAQ, a Google search of the web & the MCMS newsgroup, or an MSN search of my Outlook where NewsGator stores all my blog feeds), so I’m documenting it here for those other souls who hit it.

After my upgrade, I checked the ISAPI filters registered at the root IIS website node and had the following listed:

  • Resolution HTML Packager
  • MCMS ISAPI Filter
  • MCMS HTML Packager
  • Resolution Filter

I needed to remove the two Resolution IFilters.

Andrew Connell
Developer & Chief Course Artisan, Voitanos LLC. | Microsoft MVP
Written by Andrew Connell

Andrew Connell is a full stack developer who focuses on Microsoft Azure & Microsoft 365. He’s a 20+ year recipient of Microsoft’s MVP award and has helped thousands of developers through the various courses he’s authored & taught. Andrew’s mission is to help web developers become experts in the Microsoft 365 ecosystem, so they can become irreplaceable in their organization.

Share & Comment