I was working on a site today that is slowly wrapping up. One of the last things I needed to do was get the 404 page set up. In IIS, this means you need to tell IIS to check for script existance, otherwise CF will show you an ugly error.
So - I modified the settings and it worked fine... until my Flash developer let me know that all the Flash files on the site (the ones using remoting) weren't working. He was getting this error in his debugger: NetConnection.Call.BadVersion
I wasn't sure what it could be. I did some Googling - but didn't find anything. For the heck of it, I then tried to hit mysite/flashservices/gateway. Before CFMX7, you could use this as a way to test your Flash Remoting gateway. It doesn't work in CFMX7, but I tried it anyway. My custom 404 error page appeared so I knew then that it was related.
For the heck of it, I created a flashservices/gateway folder on the server - and remoting started working again.
Archived Comments
Ray - did you ever figure out why this was the case or find a solution other than creating the folder? This is going to crop up on a couple of sites we are doing so I want to remember it. I just know I'm going to be beating my brains out trying to remember where I heard of this problem before (ha).
Nope, sorry, no additional info.
Where exactly did you create the folder on the server? I am having the same exact problems and am not able to turn flashremoting on at all. Also can you tell me what is the configuration on your gateway-config.xml file? Thanks.
I created the folders under web root. Note - I had a simular issue last week. I tried this solution and it didn't work. What I did instead was remove and then reinstall the IIS connectors.
Hey ray, I see you haven't learned the source of the problem. I'm having the same, but I'll have to wait until off hours to reinstall the connector. But here's my question; Did you figure out how to quickly test remoting on CFMX 7 since going to the url doesn't work any more?
No, I did not. :(
I ran into the same problem with a site I have on a shared hosted server. What I found that worked for me was to create an empty flex2gateway directory in my web root and that took care of the NetConnection.Call.BadVersion problem.