ColdFusion (2016 release) Update 9 and ColdFusion 11 Update 17 released

February 22, 2019
Staff 29 posts
Followers: 18 people
41

ColdFusion (2016 release) Update 9 and ColdFusion 11 Update 17 released

Staff 29 posts
Followers: 18 people
February 22, 2019

Update (2/25/2019): We have also updated the Docker image for the latest ColdFusion (2016 release) update. For more information, see ColdFusion containers.

NOTE: ColdFusion 11 Update 16 and ColdFusion (2016 release) Update 8 are no longer available for download. We recommend users to upgrade their versions of ColdFusion to the latest updates.

We are pleased to announce that based on your feedback and observations on the previous ColdFusion updates (12 Feb, 2019), we have released updates for:

The following are the tech notes for the releases:

Both updates contain fixes for a few critical bugs that were reported in the previous updates. To see the list of bugs that have been fixed and the known issues, see the documents below:

Docker containers

We have also updated the containers for ColdFusion (2018 release) and Performance Monitoring Toolset. For more information, see ColdFusion containers.

We would also like to thank ColdFusion users and the community for their support and helping us build a better product.

Comments (41)
2019-03-03 04:42:47
2019-03-03 04:42:47

Hi there

We’ve just updated all our servers with the latest round of updates (last 3) and suddenly CFHTTP is behaving differently. Some of our customer use PayPal IPN Verification which does a CFHTTP GET to the following URL:

https://www.paypal.com/cgi-bin/webscr?cmd=_notify-validate&#getHttpRequestData().content#

No code has been changed, just the new updates installed and restart. Seems either CFHTTP behaviour has changed or URL encoding?

This is a major issue for us as now all PayPal payments are failing.

Dave

Like
(4)
>
davequested
's comment
2019-03-03 13:33:37
2019-03-03 13:33:37
>
davequested
's comment

Dave, you say it is “behaving differently”. Can you elaborate?  Do you mean returning an error? a different result?

And have you created a single file test with a couple lines to do the cfhttp and dump the result? And have you tried that on another machine with the same version? That could help you see the problem, or help others try to replicate it.

Finally, have you confirmed there are 0 fatalerrors reported in the install log of the latest update you did, in cfusion\hf-updates subfolder for that latest update?

(And did really mean you did the “last 3”, as in 3 in an row? That would not have been necessary  They are cumulative, so you need only do the latest you want to do.)

Let us know if any of this helps.

Like
>
Charlie Arehart
's comment
2019-03-18 15:46:22
2019-03-18 15:46:22
>
Charlie Arehart
's comment

We have the same problem sending data to Twilio and is breaking all our call integrations.

Like
>
ehoffmandscxn
's comment
2019-03-18 16:20:43
2019-03-18 16:20:43
>
ehoffmandscxn
's comment

for reference:  we switched to `encodeForURL()` method.  Now works again.

Like
>
davequested
's comment
2019-04-19 16:14:10
2019-04-19 16:14:10
>
davequested
's comment

We are also having issues with strings being passed to our API & Solr after this update. Still determining what this update changed in handling those passed strings and why they all now require encoding.

Like
2019-03-01 11:40:48
2019-03-01 11:40:48

We’ve upgraded from CF-11 to CF-2016 Update 9 (Enterprise Versions). We have hundreds of Report Builder files which where working fine with CF-11.

In CF-2016, no € symbols are displayed in our reports. It does not matter whether a string containing a € symbol is passed to the report via a variable, or a € symbol is contained directly in a text field of the report. Instead of the € symbol, the currency sign (¤) [Unicode Character “¤” (U+00A4)] is displayed. We cannot find the reason for it. :-((

Like
(2)
(14)
>
KnuBew
's comment
2019-03-03 00:54:06
2019-03-03 00:54:06
>
KnuBew
's comment

Did you modify JAVA settings?

Like
>
Bernhard Döbler
's comment
2019-03-03 11:21:29
2019-03-03 11:21:29
>
Bernhard Döbler
's comment

Yes, but we’ve tried also the original JAVA settings in jvm.config – same failing result. We have raised a bug (4204059) report under https://tracker.adobe.com/#/view/CF-4204059

Like
>
Bernhard Döbler
's comment
2019-03-03 12:43:31
2019-03-03 12:43:31
>
Bernhard Döbler
's comment

We use the font “Helvetica” in most of our reports (*.cfr) for creating PDF files, because this font is listed as “ADOBE-BUILT-IN” font in the ColdFusion Administrator under “Server Settings > Font Management”. We never had problems with the EURO (€) symbol in our generated PDF files.

After changing the font to “Arial” in a report file (*.cfr), the € symbol is displayed correctly, although the font “Arial” is not listet in the ColdFusion Administrator under “Server Settings > Font Management”. That’s very strange.

I asume the bug may have something to do with some kind of wrong font mapping or a kind of wrong font fall-back in CF-2016.

We have hundreds of Report Builder files (*.cfr) and it’s nearly impossible for us to edit every single report file. This would take days.

Like
>
KnuBew
's comment
2019-03-03 13:49:53
2019-03-03 13:49:53
>
KnuBew
's comment

KnuBew, have you tried to create a simple demo with just a couple lines to show the problem, in a way that lets you or others demonstrate it? And to take cfreport out of the equation, could you try something simpler like a cfdocument with a single line of content that may demonstrate things? That could help you see the problem, or help others try to replicate it.

And could you then try that on another machine with the same version first, or on cffiddle.org or trycf.com?

Finally, have you confirmed there are 0 fatalerrors reported in the install log of the latest update you did, in cfusion\hf-updates subfolder for that latest update?

Let us know if any of this helps.

Like
>
Charlie Arehart
's comment
2019-03-03 15:54:48
2019-03-03 15:54:48
>
Charlie Arehart
's comment

Hello Charlie, thanks for your comment.

have you tried to create a simple demo with just a couple lines to show the problem, in a way that lets you or others demonstrate it?

Sorry, that’s not possible, because the error occours only in report files (*.cfr) . I’ve posted two files under: https://tracker.adobe.com/#/view/CF-4204059

And to take cfreport out of the equation, could you try something simpler like a cfdocument with a single line of content that may demonstrate things?

The <cfdocument> tag works like a charm without any problems.

<cfdocument format=”pdf” filename=”euroTest.pdf” overwrite=”yes” saveAsName=”euroTest.pdf”>
Show € symbol
</cfdocument>

The pdf is generated correctly with the € symbol.

And could you then try that on another machine with the same version first, or on cffiddle.org or trycf.com?

I’m working with a multi server enviroment. I have only one development machine, but I can reproduce the error on all running server instances. The production machine still runs under CF-11 and I cannot update it to CF-2016 until the reason for the error (and a fix) is found. Further testing is difficult for me, because I cannot run report files (*.cfr) on cffiddle.org and trycf.com .

Finally, have you confirmed there are 0 fatalerrors reported in the install log of the latest update you did, in cfusion\hf-updates subfolder for that latest update?

Under “cfusion\hf-updates” there is only a “hotfix_filelist.log”. This file only lists added, modified and removed files. In all other instances under “{instance_name}\hf-updates” I cannot find a “install log”.

The “Adobe_ColdFusion_2016_Install_02_20_2019_22_22_11.log” lists:

0 NonFatalErrors
0 FatalErrors

I hope that this information will help a little.

Best regards

Knut

Like
>
KnuBew
's comment
2019-03-03 15:58:31
2019-03-03 15:58:31
>
KnuBew
's comment

Sorry, block quotes didn’t work in my comment.

Like
>
KnuBew
's comment
2019-03-03 16:26:20
2019-03-03 16:26:20
>
KnuBew
's comment

Knut, thanks. So a few more things in reply:

About the sample CFR offered in the tracker, thanks. That’s perhaps the kind of demo I was referring to. That said, since cfr’s are binary, we can’t know if we can run it, if it may require specific args passed in on the cfreport tag
I am saying that for your sake, and Adobe’s, or anyone else who may help you, it would help for you to create a simple CFR (yes, open CF Report Builder and create a simple new report, with one line, using the font you’re referring to). And then share that, and a CFREPORT to call it (whether there or here). At least then others (or you) could try THAT on other servers.
Not to discourage you from seeking assistance, but it seems worth noting that since CF2016, CFReport and the Report Builder are deprecated  AND unsupported. See https://helpx.adobe.com/coldfusion/deprecated-features.html
That log is indeed what I was referring to (it has the word “install” in it). I suppose I could have been more specific for you, but I knew it would be only one of two log files there. And as for the cfusion hf-updates having no update install log, I suppose you may have applied updates ONLY to instances and NOT the cfusion instance, which seems perhaps the situation for you.

Like
>
Charlie Arehart
's comment
2019-03-03 16:35:22
2019-03-03 16:35:22
>
Charlie Arehart
's comment

In my last reply, those were supposed to be numbered paragraphs. Sadly, just as you lost your blockquotes, I lost the numbering. There is a problem with the portal (which happened in the past, when people would edit previous comments especially). I have reported that again to Adobe, privately, and also in a post I’d made in Oct (https://coldfusion.adobe.com/2018/10/seems-problem-editing-replies-since-recent-portal-update/), and I’d updated that in early Feb to say it was fixed (with a new post celebrating that), but now it’s back. I have added a comment today to both posts.

Like
>
Charlie Arehart
's comment
2019-03-03 17:53:04
2019-03-03 17:53:04
>
Charlie Arehart
's comment

> the sample CFR offered in the tracker…

The CFR sample is that simple kind of report, you’ve described. You can open it with a direct call to the file. There no need for additional parameters to call it.

> since CF2016, CFReport and the Report Builder are deprecated

Yeah, I know and I think it was a very bad decision from Adobe to deprecate CFReport and Report Builder without offering an alternative reporting tool for the CF users. Reporting was one of the main reasons to use ColdFusion in my company for our online ticketing application since 2008 … and we have hundreds of reports (*.cfr files).

And as for the cfusion hf-updates having no update install log, I suppose you may have applied updates ONLY to instances and NOT the cfusion instance, which seems perhaps the situation for you.

No, we always apply updates to all instances (inc. “cfusion”). Maybe there is no update log because we run CF on a linux machine?! Don’t know…

 

Like
>
KnuBew
's comment
2019-03-03 18:12:35
2019-03-03 18:12:35
>
KnuBew
's comment

Knut, ok on all that. But on your first point, we couldn’t have known, right?

Also, how about making it easier for folks to test it by offering a cfm with the cfreport that calls it? Most folks don’t use it at all. And I’m not at my computer to offer that for you as a confirmed successful test.

I’m just trying to help you help us, to help you  🙂

And I realize you may just wish to report the bug and leave it at waiting for Adobe. I just have seen many cases where a seeming bug could not be reproduced on another machine. Thus my pressing (and since Adobe may not help with this now-not-supported feature)

Like
>
Charlie Arehart
's comment
2019-03-03 19:21:09
2019-03-03 19:21:09
>
Charlie Arehart
's comment

Charlie,

> But on your first point, we couldn’t have known, right?

Yes, you’re right. Sorry, I missed to mention that.

> Also, how about making it easier for folks to test it by offering a cfm with the cfreport that calls it?

That’s right. I wrote a small cfm file to call the report file and to display the generated report on screen. I’ve added the file to https://tracker.adobe.com/#/view/CF-4204059

> I’m just trying to help you help us, to help you 🙂

Many Thanks. I really appreciate your tips.

Like
>
KnuBew
's comment
2019-03-03 19:59:57
2019-03-03 19:59:57
>
KnuBew
's comment

Thanks for adding that. Hope others may try that, whether following alone here or in tracker, or that I can later. Speaking of tracker, you should add a comment (if you haven’t already) saying that you added that file, so it will notify others following it.

Like
>
Charlie Arehart
's comment
2019-03-03 20:14:16
2019-03-03 20:14:16
>
Charlie Arehart
's comment

> you should add a comment (if you haven’t already) saying that you added that file, so it will notify others following it.

I’ve just added the comment to the tracker.

Again – thanks to you.

Like
>
KnuBew
's comment
2019-03-03 22:48:16
2019-03-03 22:48:16
>
KnuBew
's comment

Just an update to those following this thread: I just tried the code he shared, in Tracker, and I shared observations there. It really would be best to continue the conversation about this there, as it’s more a support issue and not about this specific update.

(I report there that it did not work for me on EITHER CF2016 update 9, which  this is about, OR on update 5, where I also tested it. So it doesn’t seem to be related to updates within cf2016, per se, or at least not THIS update.)

Like
2019-02-26 14:28:43
2019-02-26 14:28:43

Has anyone else experiencing an issue after installing CF11 Update 17 where a individual CFAdmin security user can no longer access the ‘Settings Summary’ page? Before I ran the update, my individual login could view the CFAdmin ‘Settings Summary’ page. Immediately after the CF11 Update 17 patch, I can’t. I *can* view that page when logged in as the root CFAdmin account, but policies require us to use individual user accounts. Error “The current user is not authorized to invoke this method.” appears as ‘cfaminapiSecurityError’ occurred at /CFIDE/adminapi.accessmanager.cfc:105. There’s nothing I can see in user setup — the user account is basically a super-user with everything enabled — that would keep it from accessing that page. I’ve reported the issue, and been told Adobe cannot replicate, and that it must be my environment. They also asked if I’d reset the connectors (I have). I understand the thought, but it worked exactly as it should before the update. The only thing that’s changed is running the CF11 Update 17 installer. Seems like this has happened before (https://coldfusion.adobe.com/discussion/2156921/). Has anyone else noticed this scenario? Thank you.

Like
(4)
>
CFDaddio2
's comment
2019-02-26 20:17:16
2019-02-26 20:17:16
>
CFDaddio2
's comment

Sorry for the long, run-on paragraph. As soon as I edited my original post, it would no longer accept line breaks.

Like
>
CFDaddio2
's comment
2019-02-26 20:17:53
2019-02-26 20:17:53
>
CFDaddio2
's comment

The problem could be due to an unnoticed error in the applying of the update. You don’t clarify if you have confirmed that you have looked in the install log for your update (in the hf-updates subfolder for your update 17), to ensure that it reports (near the top) that there were only all “successes” and zero “errors”. If any errors, that may cause your problem. For more, see:

https://www.carehart.org/blog/client/index.cfm/2016/9/6/solve_common_problems_with_CF_updates_in_10_and_above

If you would say that there are 0 errors, I will note that the number of people using separate admin users is a rather small percentage of the CF base, and even fewer would have necessarily yet applied update 17. I would think your next step would be to implement the free trial or developer edition on another box, confirm that it WORKS when you enable that, and then do a comparison of the two to find the difference.

Not the answer you sought, I’m sure.  But some things to go on.

Like
>
Charlie Arehart
's comment
2019-02-27 13:46:20
2019-02-27 13:46:20
>
Charlie Arehart
's comment

Thank you, Charlie. People like you are often amazing resources for issues like this, and you don’t get thanked enough.

For what it’s worth, I have checked the install log and there were zero errors reported. So, I’ll need to try your other suggestions. With the install-on-separate-box idea, are you suggesting just straight install or getting that new install up to u17 before verifying? I ask because, as I mentioned, I know it worked as it should on u15 … I skipped u16 because I wasn’t able to install it due to the ‘manual installation using admin account’ bug. So, it worked fine on u15, no install errors reported with u17, but no longer works with u17.

Thank you again. Have a nice day.

Matt Barrick

Like
>
CFDaddio2
's comment
2019-02-28 04:39:08
2019-02-28 04:39:08
>
CFDaddio2
's comment

Thanks for the very kind regards, Matt.Right, I was thinking that you might want to install cf11 on the new machine, test your issue, then apply the update, and test again. Then if it works, compare what’s different.

Like
2019-02-22 20:41:48
2019-02-22 20:41:48

FYI, whatever bug CF11u16 introduced to <cfpdf> is still in CF11u17.

Said bug, which appears to be induced by a previous action of “addWatermark”, outputs an error message of “Opetation could not be completed. Cause: An error occurred while reading source for the cfpdf tag.”

Opetation is not my misspelling.

Like
(7)
>
carl.samuelson.ric
's comment
2019-02-22 21:07:16
2019-02-22 21:07:16
>
carl.samuelson.ric
's comment

Carl, it seems you feel that is a problem all would hit, but that’s not one I had heard anyone mention in the comments of the blog post last week. (But I could have missed it.)  To help confirm if its unique to your setup, perhaps, could you put together a small example that demonstrates the problem? In perhaps just a few lines?

Better still, if you could take that demo code (failing for you) and try to run it on your own first in Adobe’s cffiddle.org site, that would be another way to confirm if the problem was universal or perhaps unique to you. Just worth it as a sanity check.

Like
>
Charlie Arehart
's comment
2019-02-25 14:47:24
2019-02-25 14:47:24
>
Charlie Arehart
's comment

Charlie,

That sounds great; however, cffiddle.org seems to be limited to CF2018 and CF2016.

Any other thoughts?

Like
>
carl.samuelson.ric
's comment
2019-02-25 15:11:56
2019-02-25 15:11:56
>
carl.samuelson.ric
's comment

Carl, you focused on the second paragraph, rather than the first. I asked if you could offer us some demo code, even just posted here, for folks to try to see if they would have the same issue you do.

As for the fact that cffiddle supports only CF2018 and 2016, ok. Sorry I didn’t connect the dot to your reporting being on 11. Still, you could try it there to confirm if what you have WORKS AT ALL, even on 2016 or 2018.

But here’s still more good news, if you really wanted to focus on running it on 11: you can use trycf.com, which is an older form of the same sort of tool (from the community) and which DOES support CF11.

Again, if you can run your demo live locally and it fails, then on their server and it works, that would seem to suggest the problem is on your end.  But again if you share a code or link to one of these tools, or a gist, then others could try it as well. Please do try it on one of those first, though, and let us know how it goes.

Like
>
Charlie Arehart
's comment
2019-02-25 15:37:45
2019-02-25 15:37:45
>
Charlie Arehart
's comment

Charlie,

I didn’t mean to imply I was ignoring paragraph 1, I was (and am) putting together a demo, to use in cffiddle and post back here. While I was doing that, I noticed that cffiddle ignores CF11.  But, I continued working on my demo example, and I may have backed into a fix for the bug.

Code, nutshell:

  • read pdf form
  • populate form params
  • output form to temp file
  • create another pdf, consisting of signature image
  • addWatermark variable (copyFrom: img pdf, source: temp file)
  • *write watermark variable back to temp file
  • delete file
  • cfcontent variable to browser as a pdf

As of CF11u16 the bug started throwing the previously reported error.

If I remove the (*superfluous) write to the file, the code works as it did in CF11u15 (and all CF11 versions prior); extremely odd.

I attempted to use my demo, on cffiddle, but, since I’m reading files and such, cffiddle shuts me down; so, it’s posted below.

edit: TryCF.com also shuts me down

Demo code:

<cfset temp = getTempFile(getTempDirectory(),”temp”) & “.pdf”>
<cfpdfform action=”populate” source=”https://pt01.ricomaha.com/fake/fake.pdf” destination=”#temp#” overwrite=”true”>
<cfpdfformparam name=”YourName” value=”Adobe User”>
<cfpdfformparam name=”DateToday” value=”#dateFormat(now(), ‘long’)#”>
</cfpdfform>

<cfdocument format=”pdf” name=”watermark”><img src=”https://pt01.ricomaha.com/fake/fake.png” style=”height:65px” /></cfdocument>
<cfset wfile = getTempFile(getTempDirectory(), “wfile”)>
<cffile action=”write” file=”#wfile#” output=”#watermark#”>

<cfpdf action=”addWatermark” copyFrom=”#wFile#” source=”#temp#” showonprint=”true” name=”fake” overwrite=”true” position=”90,-175″ opacity=”10″>

<!— deleting/commenting out this next line will stop the CF11u16/17 bug from firing —>
<cffile action=”write” file=”#temp#” output=”#toBinary(fake)#”>
<cffile action=”delete” file=”#temp#” >
<cfcontent type=”application/pdf” reset=”true” variable=”#toBinary(fake)#”>

Like
>
carl.samuelson.ric
's comment
2019-02-25 19:22:46
2019-02-25 19:22:46
>
carl.samuelson.ric
's comment

Carl, I only had a moment to try your code, and I was tripped up by the blog having changed ” and ‘ to special formatting. I am offering here the code corrected, for the sake of others who may try going forward.

And also note that when entering content here, you can change formatting, including changing the default style of “paragraph” to “preformatted text” using the drop-down on the top left, while typing.

Let’s see if that works better.

<cfset temp = getTempFile(getTempDirectory(),”temp”) & “.pdf”
<cfpdfform action=”populate” source=”https://pt01.ricomaha.com/fake/fake.pdf” destination=”#temp#” overwrite=”true”>
<cfpdfformparam name=”YourName” value=”Adobe User”
<cfpdfformparam name=”DateToday” value=”#dateFormat(now(), ‘long’)#”>
</cfpdfform>
<cfdocument format=”pdf” name=”watermark”>
<img src=”https://pt01.ricomaha.com/fake/fake.png” style=”height:65px” />
</cfdocument>
<cfset wfile = getTempFile(getTempDirectory(), “wfile”)>
<cffile action=”write” file=”#wfile#” output=”#watermark#”>
<cfpdf action=”addWatermark” copyFrom=”#wFile#” source=”#temp#” showonprint=”true” name=”fake” overwrite=”true” position=”90,-175″ opacity=”10″>
<!— deleting/commenting out this next line will stop the CF11u16/17 bug from firing —>
<cffile action=”write” file=”#temp#” output=”#toBinary(fake)#”>
<cffile action=”delete” file=”#temp#” >
<cfcontent type=”application/pdf” reset=”true” variable=”#toBinary(fake)#”>

But I have to leave it at that for others to try, for now, as I have a scheduled client call to take.

Like
>
carl.samuelson.ric
's comment
2019-02-25 20:57:42
2019-02-25 20:57:42
>
carl.samuelson.ric
's comment

Charlie,

Gah!! I knew there had to be a way to submit code.

I attempted to add my code, highlighted it all as “preformatted”, looked fine prior to submit; but, alas, when it came back it was “pretty” again. I even tried the “paste as text” option (also a no go).

Like
>
carl.samuelson.ric
's comment
2019-02-25 21:00:35
2019-02-25 21:00:35
>
carl.samuelson.ric
's comment

Here I tried to switch over to “text”, instead of visual; it posted a blank reply. 

Like
2019-02-22 16:13:27
2019-02-22 16:13:27

[Following]

Like
2019-02-22 15:53:00
2019-02-22 15:53:00

Downloading now and will validate the corrections for the various issues since I ran into almost all of them.

Like
2019-02-22 13:55:37
2019-02-22 13:55:37

Saurav, I realize you may be responding to my first statement (thanking you all for the quick turnaround). But what about the 3 questions I’d raised?

Like
(1)
>
Charlie Arehart
's comment
2019-02-22 14:02:44
2019-02-22 14:02:44
>
Charlie Arehart
's comment

Darn, I had meant the above to be a reply to the first comment, not a new one on its own. 🙁 That happens sometimes on my mobile for some reason, perhaps user error. Wish I could move it. Oh well, too late. Offering this breadcrumb for readers.

Like
2019-02-22 13:36:49
2019-02-22 13:36:49

Wow, thanks for the quick turnaround on the new update.

I’m a bit surprised to see them only for 11 and 2016. Are you all confirming that the issues fixed were based on issues that you could see were not possible in 2018? I really thought some folks had reported them there also, and that I’d even seen the tasks issue specifically with a client. I will try to replicate it today, or perhaps others here will confirm if they had.

Also, I’m surprised to see the odbc problem is listed only as a know issue” with a file manipulation we need to do ourselves. Any explanation on why you guys could not just do it for us?

And I’ll assume there is no refreshed cf2018 installer addressing the issue from last week’s refresh, which had the issue where it showed update 2 as both installed AND available? If not, that will confuse people for months until the next update to 2018.

As always, just trying to help.

Like
(3)
>
Charlie Arehart
's comment
2019-02-22 13:44:24
2019-02-22 13:44:24
>
Charlie Arehart
's comment

Thank you Charlie.

Like
>
SauravGhosh
's comment
2019-02-22 16:04:07
2019-02-22 16:04:07
>
SauravGhosh
's comment

 

Hi Charlie,

#1 – The problem should not affect 2018 as far as we tell. Would help if someone can provide a reproducible case.

#2 – Removing the dll files was a recommendation from Data Direct when they provided us new drivers in the last update cycle, so we had to replace the same with newer versions of the dll files. We are following up with data direct on this.

#3 – This can be handled without an installer bits refresh, so this will be fixed if it has not already been fixed.

Thanks,

Vamsee

 

 

Like
(1)
>
Vamseekrishna Nanneboina
's comment
2019-02-22 21:03:50
2019-02-22 21:03:50
>
Vamseekrishna Nanneboina
's comment

Thanks, Vamsee.

Like
Add your comment