I had recently blogged about not being able to connect to the Flex2Gateway when using an IISAdmin switcher and creating a new instance of a web site. Well today a coworker was setting up his PC to do the same thing and was experiencing the same problems.
We’ve narrowed it down to the JRunScripts Virtual directory that we had to add. He had created the virtual directory, but he had overlooked unchecking “Read” access, clicking the “Remove” button next to the application name, and selecting “Scripts and Executables” for Execute Permissions. I’m guessing it’s the Execute permissions that needed to be switched from “Scripts” that fixed the problem, but now at least I’ll know for future reference if this happens again.
I just ran into this problem again today and realized I had not pulled this post over from my old blog. This is the first post about my initial issues. The follow up post will have the solution that I used (and still solves the problem).
My manager had recently asked me to set up my PC to be able to switch web roots, making deploying my code to the live site a little less cumbersome. He had found a nice little program to do this (IISAdmin.NET for those interested). It allows you to choose what you want the web root to be so you can reference all of your files with absolute references (or to reference directories just like on your web server).
I had got everything set up in IISAdmin, set up my website in IIS, switched my web root to my new site and got everything working…except for my flex2gateway. For some reason, whenever I tried to remote via the flex2gateway, it kept coming back with the error Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Status 405 Cannot find ‘http://localhost/flex2gateway’ However, when I switched back to my Default Web Site, it worked correctly again. I tried restarting IIS, restarting ColdFusion, and nothing seemed to make it work. I then went to http://localhost/flex2gateway/ and it showed the (correct) blank white screen. I then noticed that I was using the new web root I had created. I then went back to my Flex app and tried connecting to CF again, and lo-and-behold, it worked correctly…what?!? I had made no changes other than visiting the flex2gateway directly in my web browser.
So I guess the fix is to either let ColdFusion simmer for a bit and it will “figure it out for itself” or (probably more accurate), open up the http://localhost/flex2gateway/ page for ColdFusion to add whatever settings it needs to for the flex2gateway for that newly moved web root localhost application. Either way, I’m not complaining, well, not until I have to do this for another site, and hopefully this process will work then too.