Installing CF 9 kills IIS 7.5 - Why??

[cf8_user]

First let me say thanks to anyone who can help me as I am now 1 week into this and getting no where...

System info:

Windows 7 Home Premuim

Service Pack 1

IIS 7.5

Prior to installing (attempting) CF9 I had a site configured and working as part of some .NET work I am working on.  The pages displayed and all was good.  I decided to go ahead and install CF9 for some dev work.  As soon as I use the Web Server Configuration Tool it knocks out everything

I can't even get http://localhost to display.  My .NET pages no longer display and the CF admin does not display - NOTHING works.  But as soon as I go back into the Web Server Configuration Tool and delete the server info everything work again but I am back to not having CF9 working.

Can anyone tell me what I am missing and/or doing wrong???

Thanks!!

[ilssac]

ColdFusion 9 (and earlier) where designed to work with IIS 6.  They predated IIS 7+.  To work on IIS 7+, you need to install the optional IIS 6 backwards compatibility features of IIS.

ColdFusion 9.0.1 was designed to work with IIS 7+.  You do not (and should not) install the optional IIS 6 backwards compatibility features of IIS once you have installed the 9.0.1 upgrade.

Yes you HAVE to install the upgrade.  Adobe HAS NOT reverse engineered the original 9.0 installer to include the 9.0.1 update.  You have to install 9.0 then install the update.

[cf8_user]

Thank you - I will go back and give that a try.  I will uninstall all the IIS 6 options and re-install

9 + update.

[cf8_user]

Ok, making a little progress -

I can now display the default page for http://localhost but if I try to go to any other location i get the following:

Module	IsapiModule
Notification	ExecuteRequestHandler
Handler	JWildCardHandler
Error Code	0x800700c1

[Dave Watts]

Are you running a 32- or 64-bit version of Windows 7?

If you're running a 64-bit version of Windows 7, did you install a 32- or 64-bit version of CF?

If you're running a 64-bit version of Windows 7 and a 32-bit version of CF, did you configure your IIS application pool to be 32- or 64-bit?

For what you're trying to do, do you really need CF to work with IIS? Most developers really don't, and can just use the built-in JRun web server for CF development and testing. Hooking it to IIS doesn't really provide any useful additional functionality unless you're building something that specifically relies on IIS functionality.

Dave Watts, CTO, Fig Leaf Software

http://www.figleaf.com/

http://training.figleaf.com/

[cf8_user]

I am running windows 64 bit and CF 32 bit - I have tried the fix you mentioned and I am making some progress but till not working completely.  Technically, there isn't any reason for hooking into IIS except to be sure I know how it is done.  There is a possible chance that some of my work will go to a production server that is running both .NET and CF sites (CF 8 actually).  I can do my dev work with the built in server and may end up doing that so that I don't lose anymore time, I just wanted to get it working.

Thanks for the info

I will go back and try installing 64 bit CF and see if that makes any difference and if not I guess I will use the built in server.

Just as an FYI - here is what I am getting for an error now...

Error Summary

HTTP Error 500.23 - Internal Server Error

An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

Detailed Error Information

Module	ConfigurationValidationModule
Notification	BeginRequest
Handler	JWildCardHandler
Error Code	0x80070032

Requested URL	http://localhost:80/cfdev/
Physical Path	C:\cfDev\
Logon Method	Not yet determined
Logon User	Not yet determined

Again thanks for the help it is greatly appreciated!!

[Dave Watts]

I would definitely recommend using 64-bit CF on a 64-bit OS, unless you specifically need functionality that's only available in 32-bit environments, like COM.

When you install CF, you should choose the built-in web server rather than IIS when you install. Then, upgrade to 9.0.1 and use the Web Server Configuration Tool to connect CF to IIS. That way, you won't need the IIS 6 compatibility layer that CF 9 requires. And also, you won't have to worry about what happens if you can't get CF and IIS working together. However, you will need to set up a virtual directory to get to /CFIDE if you do this, as the physical CFIDE directory won't be in the IIS web root.

All that said, just because your apps will be deployed on IIS doesn't mean that you need IIS for development. I used to always set that up, but after a while I realized I didn't need it. I do CF and .NET development, and use IIS for ASP.NET projects only.

Dave Watts, CTO, Fig Leaf Software

http://www.figleaf.com/

http://training.figleaf.com/

[cf8_user]

ALL - Thanks again!

With your help and a little more use of "The Google" - I have figured out my problem and now have everything working.

1. I missed the IIS 32 bit configuration Dave spoke of.

2. I needed to change the app pool I was using from integrated to classic

3. Restarted - just to be sure.

.NET site is working

Default is working

CF dev site is working

Not sure if it will help anyone else but I am going to undo everything and step through the process from start to finish with these new items just to confirm it all works.

[cf8_user]

See all comments for total solution information. If anyone runs into the same problem and wants to know the steps I took to get my instance working just let me know.