A quick Google search turns up this link: http://ppshein.wordpress.com/2010/08/12/internal-500-error-cf9-on-window-2008/
So it might be that you just need to enable 32-bit apps to run in IIS and restart it. Barring that, a 500 status usually means it's the app server that's throwing an error. Did you see any errors in the CF9 logs or the IIS logs? Also, with https did you generate new certificates or are you using the same ones from the old server? Can you verify they were installed properly in IIS and CF9? (I personally don't know how but you should be able to get your network admins to double check that or just make sure when you connect to a basic web resource served up by IIS you don't see any certificate errors). I'm guessing you've run through this but it can't hurt to ask if you've cleared out your cache (browser, temp files, flash cookies if you're using any Flex) in case something on the client side is caching references to keys, certs, hashes, who-knows-what that were generated by the old server? Best of luck! -Marty On Mon, Jun 27, 2011 at 11:28 PM, Laurence MacNeill <laurence5...@gmail.com>wrote: > I'm at my wit's end here... > > We migrated everything over to a new server today... Win 2008, IIS 7, > CF9... We were running Win 2003, IIS 6 on the old server (but still had CF9 > on the old one, so nothing should've changed there). > > I copied the services-config.xml and the remoting-config.xml files from the > old server to the new one, since both the old one and the new one have CF9 > on them, and both are configured exactly the same way. > > I copied our crossdomain.xml file as well. Shouldn't be any changes there, > since the new server has the exact same domain-name as the old server > (because our domain-name now points to the new server). > > So someone please tell me why I'm getting the following error: > "Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Status 500: > url: 'https://www.mydomain.net/flex2gateway/cfamfsecure"; > > I've checked everything I know to check... It's always been some kind of > mis-configuration in the services-config or remote-config files before... > But not this time, apparently. I'm totally stumped. Could it somehow be > Win 2008 or IIS 7 that are causing the problem? Because those are the only > things that are different between the new server and the old one... > > Please help ASAP. > > Thanks. > L. > >
