ColdFusion 10 Update 14 causes an application pool stoppage on one of our 2012/IIS8.5 servers. Has anyone else had any issues? We had to roll back to update 12.
Make sure you installed VC++ redistributable package for Visual Studio update 4 on your machine.
After installing restart IIS and start application pool and hit the cfm again.
If it is still doesn't work, check Windows Event Viewer and see if any errors are reported.
Share the error code and data from Event Viewer error.
You can also try to check dll using dependency walker.
Download dependency walker and open isapi_redirect.dll in it, which will be created in c:\coldfusion10\config\wsconfig\magicnumber\ after configuring connector.
If dependency walker reports any error, please share it.
Also please note that whatever custom changes you made in connector files(like workermap.properties...) before applying the update, has to be remade after applying the update and after reconfiguring the connector.
I think the dependency walker report you have shared is for the dll in update12.
Can you please analyze the isapi_redirect.dll installed by update14 and share the report. It would be great if you can send me the screenshot of the error.
And can you please share the connector logs too. Here are the steps to follow: Reconfigure the update14 connector. Go to connector install directory(C:/ColdFusion10/config/wsconfig/magicnumber/) edit file isapi_redirect.properties and change "log_level=info" to "log_level=debug". Hit the administrator and wait for app pool to crash. After the app pool crashes send the isapi_redirect.log from connector directory. Make sure you change the log_level to debug.
The event viewer error you shared doesn't has the error number. Error number usually is at the bottom of error window in the "data" area. It will be something like this 0x 00 00 07. So please send me fresh event viewer error report with the error number.
Also please brief me about your configuration like OS version, IIS version, number of clusters in coldfusion if any, no. of sites pointing to same connector or different connectors, after how much time is the app pool crashing.
Yes, that dependency walker report was for update 12 and 14 has been rolled back now, so I'm not sure if the DLL can be scanned now? This is a production server with no dev server available unfortunately. The event log excerpt is complete - there was no error number - the values were totally empty. We had VC++ installed too. OS is server 2012, IIS 8.5, no clusters, two sites, one for CFadmin, one for main site (set up by Anit originally I recall). App pool crashes about 30 seconds after a restart. The server works for a little while and serves pages, then dies. We have all .NET app pools stopped as we don't use ASP etc.
Milan, the event logs, ISAPI debug logs and CF logs have been sent to the cfinstal@ address. Please confirm receipt.
To finish up on this thread, Adobe engineering, after pouring over all our logs, finally confirmed that there was actually a bug in the ISAPI connector for update 14. A fixed connector was provided and this solved the issue of the application pool crash on our IIS 8.5 server. The connector had to be installed manually; doing it via the CF Admin led to a server crash (error 503) when the connector tool was run to add . Strangely, the connector tool also would not show any sites when trying to add/remove connectors, even when run as Administrator. Adobe tell us that update 15 will include the fix we have been given.
We are having the same issue with Window 2008 SP2 IIS 7.5 How can I go about getting the fixed connector? We have had sites go down twice in the last two days.
Phil, Adobe originally told us we were alone with this problem, but this now seems not to be the case. You'll need the most recent isapi_redirect.dll from firstname.lastname@example.org which addresses the application pool issue on IIS. Or wait for update 15 which we are told will include the fix.