Could not find a good solution for that anywhere so as a test we tried navigating on the site to pull up another page and that is when we started getting.
Got the general to work, CFIDE/Administrator does not work (won't accept http verb post, even though its properly configured to do so everywhere we can figure). Removed and added sites through Coldfusion config manager again. 127.0.0.1/CFIDE/Administrator started working at least.
More hair pulling later updated Coldfusion 11 to update 7 (was at 3 if I remember correctly). Got an end run around looking on the web for solutions, come to find that not even CFIDE/Administrator wasn't working. Pulled up a site (through localhost) that used one of the datasources and got a 500.* error. Force removed that, one more cycle of the Coldfusion config manager and finally coldfusion files seemed (more on that later) to be properly being served up. AboMapperCustom was still listed in all the site's Handler Mappings. Multiple tries of removing and adding sites through the config manager didn't work, then we noticed that Coldfusion 9 had not properly uninstalled and removed its vestiges from IIS.
INSTALL COLDFUSION 11 PDF WINDOWS INSTALL
This is of course where things started going horribly wrong.īeing a new install using the Coldfusion Web Server Configuration we added all the sites. We uninstalled Coldfusion 9 Enterprise Edition and then installed Coldfusion 11 Standard Edition.
It worked just as the old one did though we could only run each site through localhost as the old domains have not been transferred over to point to the new server. Made an exact copy of it to a new instance. We started with a working instance of Windows Server 2007 R2 using IIS 7 with Coldfusion 9 Enterprise Edition installed that hosts multiple sites (in fact its still currently running now).
0 kommentar(er)
