Resolving “500 Internal Server Error” with ColdFusion 10 Update 14

October 16, 2014
Newbie 32 posts
Followers: 0 people
32

Resolving “500 Internal Server Error” with ColdFusion 10 Update 14

Newbie 32 posts
Followers: 0 people
October 16, 2014

We have seen that some of you have not been able to get the web server
connector working after applying update 14.

We did our investigation and following is our finding.

The connector binaries of ColdFusion 10 update 14 are built on top of  VC++
runtime 2012 update 4.

Installation of VC++ runtime requires admin privileges. If the ColdFusion
service runs as administrator or system account, the update itself install the
VC++ runtime as this account would have installation privileges.

If your ColdFusion service account is not running as administrator or system
account, applying the hotfix from administrator can’t install VC++ runtime and
you will get “500 internal server error” after configuring the
connector.

In this case, you need to manually install VC++ runtime 2012 32-bit and/or
64 bit depending on whether Web server is 32-bit or 64-bit.

You can download VC++ runtime here at:

http://www.microsoft.com/en-in/download/details.aspx?id=30679

When you install hotfix manually, administrator privileges are enforced and
so the installation of VC++ runtime is automatically taken care by the updater.

Normal
0

false
false
false

EN-US
JA
X-NONE

 

 

 

 

Comments (32)
2018-03-06 10:45:38
2018-03-06 10:45:38

I resolve my web server error with our diversion opinion, great to see your solution but also have some system error for which I read on https://notresponding.net/system-thread-exception/ and this helps me more in this, this web helps a lot to the user who is getting this type of issue.

Like
2015-05-15 06:44:39
2015-05-15 06:44:39

FYI, a user posted a question on StackOverflow as to why he could not update his ColdFusion installation after performing the lock down steps. He found out that the ColdFusion administrator’s update page relies on the /CFIDE/scripts directory to function (a-la the cfform tag). Since the lock down guide suggests denying any requests to that URI the update page was failing. He had to allow access in order to use the update feature. Here is a link to the post: http://stackoverflow.com/q/30205018/1636917

This is not good! The update feature should not require exposing that URI. This should be changed. The user was on ColdFusion 11.

Like
2015-03-31 09:40:17
2015-03-31 09:40:17

Pawel, I believe there should be a technote for CF10/CF11 with regards to this. The automatic updater still doesn’t work with my locked down installation (CF11) so until Adobe fixes this, they need to include details on how to manually install the updates for those that don’t know about this issue and forgetful people like me.

Like
2015-03-31 09:26:05
2015-03-31 09:26:05

My apologies, I see this is for ColdFusion 10 Update 14 not ColdFusion 11 Update 4, so please disregard my last comment. Time for a break 🙂

Like
2015-03-31 09:21:42
2015-03-31 09:21:42

Totally agree with Adam. Thank you for clarification blog, but where is the note about this on the actual technote? Technote is the first place I would go to find information on the update and since technote deosn’t have that info, how are we supposed to know that there could be those issues? It’s been months since the update came up and still no mention of this on the technote.

https://helpx.adobe.com/coldfusion/kb/coldfusion-11-update-4.html

Like
2014-12-03 08:17:57
2014-12-03 08:17:57

subscribe

Like
2014-11-16 14:11:26
2014-11-16 14:11:26

Big thanks to Chris – I found this thread after having a CF10 machine hosed by letting the CF admin do the Update 14 installation. I was missing the VC++ redistributable, and we follow the lockdown guide by having CF service run as a non-administrator.

At this point I’ve lost all faith in the automatic update process, and have little faith in the Adobe CF QA team in general (witness all the problems with CF10 initial release, and then again with CF11). Adobe needs to provide direct download links to the hotfix jars and provide manual installation instructions for the hotfix.

Like
2014-11-12 21:11:18
2014-11-12 21:11:18

Another thing we have noticed with this update. The Log File location has reverted to the default C drive. A *weird* coincidence it happened exactly at the time the update was applied.

We had the log file location changed to the d:drive for any of our servers that are running ColdFusion. It has now gone back and this can only be changed back by restarting the CF service gain. Not Happy.

Like
2014-11-03 21:40:35
2014-11-03 21:40:35

“bare bones install”

Yes, that’s what I use when testing new CF builds =P I just reformat, disconnect from network so OS can’t download updates, install an OS, set a restore point, then run a CF installer.

Thanks!,
-Aaron

Like
2014-10-24 04:17:58
2014-10-24 04:17:58

Rupesh wrote:
> we definitely have a very extensive QA lab setup

No, you clearly don’t!

An unmodified OS and base install is the simplest setup to test against – arguably the most obvious too – and would definitely be part of any “extensive” QA testing.

If CF/Adobe wants to be taken seriously, you need to hire someone independent to audit your entire QA and release process, implement their advice, and then have them review it again afterwards.

Like
2014-10-23 06:22:00
2014-10-23 06:22:00

What are the chances the hotfix page is actually updated to include this important detail?

http://helpx.adobe.com/coldfusion/kb/coldfusion-10-update-14.html

It’s been a week…

Like
2014-10-20 10:12:13
2014-10-20 10:12:13

[subscribe]

Like
2014-10-17 01:13:07
2014-10-17 01:13:07

This also demonstrates a gap in your approach to QA. QA of things like installers & updaters should not be done on the person’s own machine! They should be done on dedicated test machines with known states. One of those “known states” should be a bare bones install with no presuppositions about what’s on it.


Adam

Like
2014-10-17 01:02:01
2014-10-17 01:02:01

So what causes the runtime to be installed then ? Obviously something in the QA pool machines, but not a lot of your customers ?

Like
2014-10-17 00:39:27
2014-10-17 00:39:27

[Subscribe]

Like
2014-10-16 15:14:33
2014-10-16 15:14:33

All of them 🙂

Obviously that can’t happen, but why not script in the request filtering, handler mappings, and custom configuration for whom the CF service runs as? The Secure Profile is a step in the right direction, but so much more could be added to the installation process to implement a large majority of the lock down guidelines.

As it is now, even the updates (manual method since the CF Admin method doesn’t work) doesn’t take the initiative to lookup the current CF root (which can be found in the registry) and requires me to type it in.

Like
2014-10-16 14:00:59
2014-10-16 14:00:59

@Chris, what aspect of the lockdown guide recommendations are you suggesting should be implemented during the install?

Like
2014-10-16 11:33:23
2014-10-16 11:33:23

So every time I have to reconfigure WSconfig, I have to remember to replace the isapi_redirect.dll with the patched version in all the [magic number] sites… where is the latest version of this available for download? I figured it would be included in the updates. Com’on Adobe…

Like
2014-10-16 11:21:45
2014-10-16 11:21:45

There’s a couple hours lost.

All started with the POS “updater” in CF Admin. Said (2) available updates found, but only option to install CF11 Update 2 (I hadn’t installed Update 1). That hung during the installation process “Checking” something. Reloaded CF Admin, logged back in and tried “Re-install” option. That also hung at “Checking”. Then internal error 500.

Found this thread, tried reinstallation of VC++ without any change to error 500.

Tried reconfiguring the WC, no success. Found the following to manually install updates:

https://coldfusion.adobe.com/post.cfm/how-to-download-and-install-coldfusion-10-hotfix-directly

Downloaded CF11 HF1 and ran the following under admin cmd prompt:

[cfpath]jrebinjava -jar hotfix_001.jar

Server still trashed with error 500.

Ran [cfpath]jrebinjava -jar hotfix_002.jar

using the hotfix_002.jar file found in
[cfpath]cfusionhf-updates

Initial test, server appears to be functioning again, but needs further testing. At this rate, it might be years before it’s considered stable enough to replace productions’ CF9. We cannot have these types of issues applying updates. Why aren’t the recommendations in the lockdown guide implemented during the install?

Like
2014-10-16 11:00:42
2014-10-16 11:00:42

@Dave_Cordes – If the VC++ has been installed (on Windows) it will appear under the Programs and Features (Add/Remove programs) on your server.

Like
2014-10-16 10:42:14
2014-10-16 10:42:14

I already had the VC++ runtime. While running the install of it again, it shows repair or remove options. With repair option, my server is still giving 500 internal server error. BTW, my CF11 install is locked down per the guide.

Like
2014-10-16 10:40:48
2014-10-16 10:40:48

Is there a way to tell if VC++ runtime is already installed?

Like
2014-10-16 10:36:17
2014-10-16 10:36:17

[subscribe] :/

Like
2014-10-16 09:56:30
2014-10-16 09:56:30

[sunbscribe]

Like
2014-10-16 09:52:04
2014-10-16 09:52:04

Rupesh, we have the VC++ 2012 installed, and still we get a stopped application pool minutes after the server CF starts up.

Like
2014-10-16 08:52:58
2014-10-16 08:52:58

Subscribe.

In general I wonder about how much notice the CF team take of the lockdown guide.

Like
2014-10-16 08:26:25
2014-10-16 08:26:25

[subscribe]

Like
2014-10-16 08:17:51
2014-10-16 08:17:51

Yikes, truly.

In all seriousness though and as sad as it is, it would probably reflect what the 99.99% of ACF users out there are doing 🙁

I assume the connector update essentially makes it on par with the CF11 update 1/2 connector. Wasn’t there a connector update on CF11 update 1? I might be wrong – bit if it was, would this problem apply as well then?

Like
2014-10-16 07:41:31
2014-10-16 07:41:31

[reaches for popcorn]

Oh, go on Adobe, I’m looking forward to you answering *that* question…

Like
2014-10-16 07:37:39
2014-10-16 07:37:39

Yikes. Are you telling me the whole QA team at Adobe are running their ColdFusion servers *as administrator” ?!?
In direct conflict with their own guide ?

Like
2014-10-16 07:25:38
2014-10-16 07:25:38

[subscribe]

Like
2014-10-16 07:23:02
2014-10-16 07:23:02

yet another great update from adobe with numerous issues associated with deploying an update.
surely you should be aware if the connector is ‘built on top of’ another platform version and should make this clear in your deployment notes

Like
Add your comment