Copy link to clipboard
Copied
Attempting to install CF10 on Windows Server 2008 R2 Standard 64bit SP1. I've attempted twice and received an error near the end of the installation process both times:
"ExecuteAppCmd.exe has stopped working."
After dismissing the error, the installation finishes but cfm templates are not being processed. Upon launch of the administrator on the server computer a 403 error is received:
Has anyone experienced this this issue, or have ideas about resolving?
Copy link to clipboard
Copied
AppCmd.exe is IIS command line tool.
No have not seen that before myself.
Perhaps run as administrator from Start > Adobe > CF10 > Web Server Configuration Tool. Does it look like CF10 is connected to IIS? Windows 2008 r2 so I guess IIS (web server role) is in use. EG:
HTH, Carl.
Copy link to clipboard
Copied
Yes, the configured server is as pictured. I also tried adding different configs (specific IPs), but when trying to remove them the same error was thrown. There was a version of MX7 previously installed if that makes a difference. 7 of course wouldn't run without some major tweakkng, so it was removed and we're trying 10 instead. Could it have left something behind? I see nothing suspicious in the temp directory.
Here's the error:
Copy link to clipboard
Copied
Hi,
We apologize for the inconvenience caused. We would suggest removing the MX7 connectors first, before you even configure the CF10 connectors. Launch the configuration tool(in admin mode to avoid other permissions issues) and recreate the connectors.
If that doesn't work, please try the steps http://helpx.adobe.com/coldfusion/kb/coldfusion10-iis-manual-connector-configuration.html. ColdFusion10 comes with a webserver configuration tool for connecting to external web servers. There can be occasions, however, when the tool doesn't work properly. If the tool doesn't work, you can configure the connector manually.
Hope this helps.
Regards,
Anit Kumar
Copy link to clipboard
Copied
When using the config tool, I can remove, and then re-add the connection, but get the same error when adding. I followed the steps for manual config in the link you posted, but cfm templates are still not rendering.
Is all this because MX7 left it's connector in place after uninslall? If so, is there a way to manually remove it, and then just reinstall 10?
Copy link to clipboard
Copied
Hi,
Buhje wrote:
I followed the steps for manual config in the link you posted, but cfm templates are still not rendering.
After following the manual config steps, can you check the handlers mappings(cfm, cfml, cfr, cfswf). They should be pointing to cf_root\config\wsconfig\[Magic Number]\isapi_redirect.dll
Can you check that.
Buhje wrote:
Is all this because MX7 left it's connector in place after uninslall? If so, is there a way to manually remove it, and then just reinstall 10?
We would suggest you to remove the MX7 connector manually (removing the physical files) first, and then try to reinstall CF 10.
Regards
Anit Kumar
Copy link to clipboard
Copied
Anit_Kumar wrote:
After following the manual config steps, can you check the handlers mappings(cfm, cfml, cfr, cfswf). They should be pointing to cf_root\config\wsconfig\[Magic Number]\isapi_redirect.dll
Can you check that.
Yes, pointing to C:\ColdFusion10\config\wsconfig\2\isapi_redirect.dll
We would suggest you to remove the MX7 connector manually (removing the physical files) first, and then try to reinstall CF 10.
Where are the physical files located?
Copy link to clipboard
Copied
Hi,
Do you still have ColdFusion MX7 installed on your machine? If yes, can you go to cf_root\config\wsconfig\ for MX7 and find the connectors in place.
Regards,
Anit Kumar
Copy link to clipboard
Copied
No, it was removed before I tried installing 10.
I've spent the better part of a day trying to track down this issue. I'm just going to reload the server, and try this again from scratch. Since this server is not yet in production, this is still a viable option. I find it hard to believe that installing an older version of CF will break any future installations. If that's the case, it's pretty sloppy programming!
Copy link to clipboard
Copied
While installing a new version, if you configure the webserver and that webserver has already a connector created with an older version of CF, it will not work.
Uninstallation would be much more easier to be followed regarding your scenario. Before you uninstall, i would suggest you to remove the connector first.
Regards,
Anit Kumar
Copy link to clipboard
Copied
I've restaged the server and attempted to install again on a clean reload of the OS and get the same error. Guess it's not related to MX7. I'll attempt a manual config of the connector.
Copy link to clipboard
Copied
Hi,
During the installation, which webserver did you chose? Also, please check the pm sent to you.
Regards,
Anit Kumar
Copy link to clipboard
Copied
If I understand the question correctly, I chose "All".
Copy link to clipboard
Copied
Hi,
As per our discussion, after enabling the internal port, we are able to access the CF Admin. The cfm pages are also serving properly. On the other hand, IIS is unable to serve the html pages as well. This infers, that CF is working properly.
Regards,
Anit Kumar
Copy link to clipboard
Copied
Thank you Anit for all of the 1 on 1 help. I'm strictly a CF programmer and don't know the first thing about IIS so I got some outside help. This is what we did to get it going:
1) Remove the isapi filter for cold fusion.
2) Run the Cold fusion server config and install the connector specifically to the Web site.
3) Set permissions for everyone + read + execute on all of c:\ColdFusion10
cfm templates are now being served, but I'm finding that there are a few differences in the way 10 handles certain tags, especially date functions and queries. I can handle re-coding CF though.
Thanks again for your help.