Because it's Thanksgiving, it seemed like a good day to break the SA web site for a short time to install some security patches and update Microsoft Content Management Server. As I had previously mentioned, Content Management Server SP2 is out. This includes ASP.NET 2.0 support. So, I figured, this was a good chance to get our site to ASP.NET 2.0, clean up some minor HTML problems in our template pages, and so on.
Well, I did the .NET Framework 2.0 Redistributable x86 installation on our web server, then switched the CMS web site to ASP.NET 2.0 via the IIS Manager.
I next updated the site to be a VS 2005 project, removed the old application project directory from the production server, and brought it over from the devel0ment server.
I then had to run the CMS Site Manager to manage some resources, and this is when the big problem came up. I tried to run the Site Manager, and when I tried to log in to the application, this came up:
The Microsoft Content Management Server proxy component is not correctly installed.
Luckily, after some misfires, the Usenet archive at groups.google.com gave me the answer, courtesy of Stefan, who I linked to in the SP2 post:
One additional hint: check if J# redistributable is installed for all .NET framework versions installed on your box.
This was in fact the problem. CMS originally had Java components which were ported to .NET via J#, so the J# runtime is needed. Thus, when I added 2.0 to the machine, I had to add the J# Redistributable 2.0 as well. I did that, and the problem was solved. In retrospect, this was a clear requirement, and it may even be a documented one, but for whatever reason it hadn't clicked for me.