Roger Martin;8097 wrote:There are three things I would check:
1. Verify the ComponentArt handlers and modules in web.config are present. Refer to the web.config in the download for a reference.
2. Verify the application pool is running in Integrated Mode (applies only to IIS7+).
3. Investigate whether other handlers or modules might be interfering with ComponentArt. Temporarily disable any 3rd party items in web.config to see if it makes a difference.
Thank you very much for responding.
I tried a few of the things you suggested, but I haven't yet found the original web.config to ensure everything is correct. The web.config that I'm using is the same as the one that works perfectly on the old host, so I'm fairly confident the problem is not specifically in web.config. If I were to guess, I would imagine that some file did not get transfered or was corrupted on transfer. I did change the server settings to show complete details for a 500 error (which is what I was getting when trying to reach ComponentArtScript.axd). The error is:
Handler "ComponentArtScriptHandler" has a bad module "ManagedPipelineHandler" in its module list
Does that suggest anything useful to you? I don't see any mention of "ManagedPipelineHandler" in web.config.
Also, I did try commenting out all other handlers and modules to no avail.