CFJSGeek, to be clear, the “method not allowed” is actually a GOOD thing. It confirms that, in that dev environment at least, your browser WAS able to get to RDS, but it’s setup to not allow a GET (which is what your browser sends by default). Are you saying you proceeded to setup CFB or CFS to point to that dev environment and it still didn’t work? Or did you misinterpret that message in your browser and stop there?
As for your other environment, let me say first that you do NOT need to add an empty CFIDE/main/ide.cfm. Instead, that request gets processed by CF as a servlet filter. There is no need for that file to exist.
That said, yes if you block the CFIDE folder (in IIS, for instance, if that’s what you mean by “http filter”), then yes it would fail.
And it shouldn’t matter whether debugging is on or not. As for the message you get when you say you turned it off, “unhandled error, use logging enabled clients if possible”, that’s one I never heard of, and I’ve been using the RDS feature (and helping people use it) for over 15 years, in CFS, HS, DW, and CFB. But I do see in googling that message that an old JRun Studio FAQ (it was an off-shoot of CFS) indicates that could happen if you have an invalid password.
Do you have the CF admin RDS security settings to “single password”, “separate username and password”, or “no password” (the latter would be dangerous on any public server, but of course having RDS at all on a public server would be worrisome). Are you positive you’re using the password defined there in the configuration of RDS in HS? Also, you mention using a username and password, which presumes then you need to have changed to “separate username and password”, and defined such a user in the “user manager” page of the CF Admin. You also need to give that user RDS access there, of course.
Can you confirm all these things, and we can try to go from there?
Thanks for the response Charlie. Right now I'm going to focus on the ColdFusion Studio environment issue.
I added the blank CFIDE/main/ide.cfm file because otherwise it would give me a 404 error. I know you can also set IIS to not check is a file exists, but I opted for this solution. If there is a better fix for this I'm all ears.
I will have the guy double check his password again. I've been trying "separate username and password" with him but I'll give "single password" a shot. I'm wonder if because CFS is so old that it didn't support separate logins.