IIS7 - Classic ASP

Re: Problems with ASPNET 2.0 Applications with Validation Controls

GabeNodland — Thu, 10 Sep 2009 14:46:57 GMT

Brentil, thanks for the quick reply. I guess that is what I will do for now too. I will let you know if I find anything. Thanks, Gabe

Re: Problems with ASPNET 2.0 Applications with Validation Controls

brentil — Thu, 10 Sep 2009 14:37:07 GMT

I haven't done any support for it yet since I haven't had time to. I fixed it in our case by removing the CF wildcard and all other CF references from the virtual directory we were running .NET code from. The main site is CF but just a sub app was .NET so it allowed us to do this.

Re: Problems with ASPNET 2.0 Applications with Validation Controls

GabeNodland — Thu, 10 Sep 2009 14:32:58 GMT

Hello, I also have all the latest service packs for .net and i still have this exact issue. Brentil did you find anything further on this? Do I need to request the QFE. I guess for now i will just have to go into every .net app and remove jrun_iis6_wildcard.dll handler. Thanks, Gabe

Re: Problems with ASPNET 2.0 Applications with Validation Controls

brentil — Wed, 02 Sep 2009 12:58:45 GMT

Thank you very much for the information, I will do just that.

Re: Problems with ASPNET 2.0 Applications with Validation Controls

tmarq — Wed, 02 Sep 2009 01:19:45 GMT

The page at http://support.microsoft.com/contactus/?ws=support explains how to contact product support. You can contact them and request a QFE. As mentioned earlier, it is fixed in v2.0 SP2 and v3.5 SP1.

Thanks,
Thomas

Re: Problems with ASPNET 2.0 Applications with Validation Controls

brentil — Tue, 01 Sep 2009 18:22:21 GMT

Well we're still getting this issue with a fully patched Win 2008 Server running IIS, CFMX 8.0.1 fully patched, with .NET 2.0 and 3.5 both fully patched. I had to go in and remove the CF wildcard mapping from the ASP.NET application that runs as a virtual folder of the CF website. Until I did that we continually got the error message others have reported that lead me to here.

Re: Problems with ASPNET 2.0 Applications with Validation Controls

tmarq — Tue, 01 Sep 2009 17:50:19 GMT

It is fixed in v2.0 SP2, which is included with v3.5 SP1. The fix was to make ASP.NET ignore the wildcard mapping installed by ColdFusion8.

Re: Problems with ASPNET 2.0 Applications with Validation Controls

brentil — Mon, 31 Aug 2009 17:53:51 GMT

Was there ever a fix created for this? We're running into the same issue with CFMX8 and IIS7 and its been 1.5 years since the last post in this thread.

Re: Problems with ASPNET 2.0 Applications with Validation Controls

ajk-eis — Sun, 20 Jan 2008 16:30:02 GMT

UPDATE -

MS has contacted me, and indicates that they feel this is in fact an error in ASPNET (and not Cold Fusion). Wildcard mappings are allowed and CF correctly redirects as it should. My apologies to Adobe.

MS will be working on a hotfix for this problem. When it is available I will let you know here.

Cheers
Alle

Re: Problems with ASPNET 2.0 Applications with Validation Controls

ajk-eis — Sat, 19 Jan 2008 10:12:10 GMT

Hi Randy (and all other interested persons),

sorry I didn't continue the thread yesterday, but I was shot after having spent the better part of three days (and nights) trying to figure this out. Add to that that tmarq (Thomas thanks again) and I are a oposite ends of the world (Thomas in Redmond with a cup of coffee fresh in the morning and I hungry at the end of a long Friday in Germany) I was glad to just shoot off the short success post and go home and to bed!

Anyway I still have thoughts on this -

1. UPDATE Jan. 20, 2008 - see my next post in this thread.

2. Randy - I see no disadvantage with a VISTA developement box. I have one myself and have no quarrel with it. What you will have to do is go to your applicationHost.config and -

Make a back up copy
Delete the ColdFusion handler mapping that I listed above.
If you don't use CF anymore then delete all of the mappings that reference CF paths and you are done.
Subsite the CF App if you have one and make a "location" section for that subsite with a handlers section including the mapping that you deleted above. In fact you should be able to do that in the web.config using the syntax that Anil posted above. If you have an integrated ASPNET App as I do you will have to change the AppPool to compatible mode.
If you can subsite the ASPNET App, run it in a separate App Pool (better anyway)
For the ASPNET Subsite you can run integrated mode.

3. Optionally, if you can subsite the ASPNET App you should be able to use "remove" tags in the web.config for that subsite to delete all of the Cold Fusion Mappings in the applicationHost.config for that subsite. That's the nice thing about IIS 7 configuration.

Many, many thanks to Thomas and the other folks at MS for the prompt and "exclusive" handling of this problem.

HTH
Alle

Re: Problems with ASPNET 2.0 Applications with Validation Controls

steve schofield — Sat, 19 Jan 2008 06:33:54 GMT

Thank you for posting the solution. This will be helpful for future people!

Re: Problems with ASPNET 2.0 Applications with Validation Controls

tmarq — Fri, 18 Jan 2008 22:20:11 GMT

Sorry for the delay. I understand the problem now. Unfortunately, there is an incompatibility between ASP.NET integrated mode and ColdFusion8.

So what exactly is the problem? In some scenarios, ASP.NET emits HTML with <script src=”WebResource.axd?blah”>. For example, the Validation Controls use this. To ensure that the page will work, ASP.NET verifies that WebResource.axd is mapped to the AssemblyResourceLoader handler. ASP.NET in integrated mode and ColdFusion8 are incompatible because ColdFusion8 has a wildcard mapping (*mapping) that overrides the WebResource.axd mapping in the system.webServer/handlers section, and so the check fails.

ASP.NET can alter this check to ignore the wildcard mapping and use the real handler mapping for WebResource.axd. As long as the wildcard mapped handler eventually calls HSE_REQ_EXEC_URL and invokes the ASP.NET AssemblyResourceLoader handler, things will work as expected. But this change to ASP.NET will probably have to be done in a hotfix after Windows Server 2008 releases.

WORK AROUND:

To work around this, you could run ASP.NET in classic mode. On the other hand, if you need to use ASP.NET integrated mode, I recommend putting ASP.NET and ColdFusion8 in separate applications and setting up the handler mappings so that ColdFusion8 is not mapped in the ASP.NET application and ASP.NET is not mapped in the ColdFusion8 application. You can do this in the UI, or by editing applicationHost.config by hand and encapsulating the system.webServer/handlers section in a <location path="blahblah"> </location> section.

Re: Problems with ASPNET 2.0 Applications with Validation Controls

mmleinen — Fri, 18 Jan 2008 19:36:11 GMT

Alle,

Great info, thanks! Sorry if I sounded a little frustrated, but this has turned my world upside down - not be able to get my two most important web apps to run in a vista dev environment. I just bought a $6,000 dev machine from dell that only supports vista (go figure). So I have been feeling a little stressed about moving to vista. But you are right, I have coldfusion installed. I guess it is still a problem even if it is uninstalled, which I think I did.

Thanks so much for being on top of this and including me in the loop.

Sincerely,

Randy

Re: Problems with ASPNET 2.0 Applications with Validation Controls

ajk-eis — Fri, 18 Jan 2008 18:33:26 GMT

Hello Randy,

>>I would hope that someone in the IIS7 team would take this one seriously.<<

They are, believe me.

We've been working this one offline since there is a 10 Hour time difference and there were alot of messages back and forth.

My problem has just now (5 Minutes ago) been found with alot of help from Thomas from MS. It's an entry the Cold Fusion 8 makes in the default configuration of the applicationHost.config.

If you see it, then you say my God why didn't I see that -

Basically, Cold Fusion can't run without it and ASP can't run with it in integrated mode.

They are still working on it to see if there is a way that both CF and ASP are happy.

The section of the applicationHost.config concerned (for me) was-

That is the default configuration for all sites.

HTH
Alle

Re: Problems with ASPNET 2.0 Applications with Validation Controls

mmleinen — Fri, 18 Jan 2008 18:26:18 GMT

I would hope that someone in the IIS7 team would take this one seriously. These are showstopper issues for IIS7. Is there anyone who has a web.config file that actually works with these validation controls in VS 2008 on IIS7? None of the suggestions have worked.

Please someone respond.