ColdFusion 9.0 Windows 7 64bit IIS7 and HTTP Error 500.0

[ilssac]

I am trying to install ColdFusion 9.0 Developer in Multi-home on a 64bit  Windows 7 workstation for the first time.

Every time I try, I am getting the dreaded HTTP 500.0 Internal Server  Error when I connect ColdFusion to an IIS 7 web site.

I've made sure that IIS 7 has the IIS Metadatabase and IIS6 configuration compatibility, ISAPI Etensions and ISAPI Filters enabled.

I've enabled 32bit application pools, as far as I can tell in the II7  websites.

But I am still unable to get ColdFusion and II7 working together.  As  soon as I connect a web site to a ColdFusion instance with the web  server connection tool, all requests (htm and cfm) to the web site  return the 500 error.

Can anybody help?

TIA
Ian

P.S.
I'm not quite ready to apply the 9.0.1 update, which I hear works  better with IIS7.  My workstation needs to be the same version as our  servers for the time being.

[ilssac]

Ok, I've restored the application pool to 64bit since, I am running the 64bit version of ColdFusion.

But I am still getting the HTTP 500 error.

[Charlie Arehart]

If you're on 64 bit Windows, why are you enabling 32 bit app pools? Are you running CF in 32 or 64 bit mode?

If you view the handler mappings for the web site you have in mind, do you see some for .cfm files? If you open the properties for that .cfm mapping (double-click), do you see its "executable" set to something like C:\ColdFusion9\runtime\lib\wsconfig\jrun_iis6.dll? Is there a mapping for the * path pointing to something like C:\ColdFusion9\runtime\lib\wsconfig\1\jrun_iis6_wildcard.dll? (The number in there may differ per configuration.)

/charlie

[ilssac]

I'm trying to run 64bit ColdFusion on a 64bit Windows 7 workstation.

Everything I have tried todate is made no difference.

If I uninstall the connectors, the HTML pages will show up in the website.

If I install the connector all requests for HTML and CFML pages will return a HTTP 500 error.

[ilssac]

So the issue was apperently security related.

I opened up the Inetpub and JRun4 directories wide open and the connector worked correctly.

Yeah I have my website up and running on my worksation!

So, now what would be more sensible security settings for these directories?

[BrianKeszler]

Were you able to lock down the directories at all, or did you leave them wide open?

I'm not very familiar with security, so can you describe what you did to open them up?

[ilssac]

I opened them up by setting the security permissions to the JRun4 directory and the Inetpub directory to allow the windows "everyone" user to have "full control".

I plan to lock it down.  But I have not done that exercise yet.  Apparently the missing piece was that the user that the IIS process runs under needs read and write permissions to the wsconfig directory under the JRun4 root.

[BrianKeszler]

Thanks for the reply.  I'll be sure to check out our user permissions.

My coworker found the following document and was able to solve our problem.  I haven't had a chance to read it yet, but there appears to be alot of good information.

http://dreamweavermx2.com/products/coldfusion/whitepapers/pdf/91025512_cf9_lockdownguide_wp_ue.pdf