ColdFusion (2018 release) Update 2, ColdFusion (2016 release) Update 8, and ColdFusion 11 Update 16 released

February 12, 2019
Staff 31 posts
Followers: 22 people
130

ColdFusion (2018 release) Update 2, ColdFusion (2016 release) Update 8, and ColdFusion 11 Update 16 released

Staff 31 posts
Followers: 22 people
February 12, 2019

Update (2/15/2019): We’ve updated the known issues documents with the following issues:

  • Scheduler deletes all tasks.
  • The QueryExecute function throws an exception.

We are working on the other issues and we will share a status update shortly. Thank you for reporting the issues.

Update (2/13/2019): This blog is updated with the following details for:

  • ColdFusion Builder (2018 release) Update 1

We are pleased to announce that we have released the updates for the following ColdFusion releases:

The following are the tech notes for each release:

The updates consist of both security and other feature enhancements. For information about the security vulnerabilities that have been addressed, see APSB19-10.

Release notes for this update and previous updates:

What’s new and changed in ColdFusion (2018 release) Update 2

Update 2 contains the following:

  • Support for Java 11. To download installers for Java 11 and Java 8, see Downloads. For more information, see Rakshith’s blog.
  • The tag cfschedule has two new actions- create and modify.
  • The function dayOfWeek has a new parameter calendar.
  • You can use cfloop as script for arrays, lists, structs, or queries. For more information, see cfloop-query and cfloop-struct, array, list.
  • Updated the following OEMs:
    1. Jetty 9.4.12
    2. ExtJS 6.6
    3. JPedal 8.4.31
  • Server Auto-lockdown includes a new installer for Mac OS. For more information, see Installer for Mac.
  • This update upgrades the connector library to a newer version. For the upgrade to be applied to the web server connector, reconfigure the connector.
  • Mobile updates-
  • New platform support matrix for the following:
    • OS Application Servers Web Server Databases External Services
      • Windows Server 2019
      • Solaris 11.3
      • OSX 10.14
      • WildFly 14.0
      • WebSphere 9.0.0.9
      Apache HTTPD 2.4.37
      • Oracle 18c
      • PostGreSQL11
      • IBM DB2 v11.1
      • Apache Derby-10.14.2
      • Microsoft Exchange 2016
      • Microsoft SharePoint 2016

Performance Monitoring Toolset

Performance Monitoring Toolset consists of the following new and changed features:

Bugs fixed and known issues list for Update 2

What’s new and changed in ColdFusion (2016 release) Update 8

Update 8 contains the following:

  • Support for Java 11. To download installers for Java 11 and Java 8, see Downloads. For more information, see Rakshith’s blog.
  • The function dayOfWeek has a new parameter calendar.
  • Updated the following OEMs:
    • Jetty 9.4.12
    • JPedal 8.6.2 for Document Management
    • PDFgServlet 9.4.12
  • You can use cfloop as script for arrays, lists, structs, or queries. For more information, see cfloop-query and cfloop-struct, array, list.
  • This update upgrades the connector library to a newer version. For the upgrade to be applied to the web server connector, reconfigure the connector.
  • Support for Microsoft Exchange 2016.
  • Bug fixes and list of known issues.

What’s new and changed in ColdFusion 11 Update 16

Update 16 contains the following:

  • Addresses security vulnerabilities as mentioned in the security bulletin APSB19-10. For the security fixes to take effect, ColdFusion must be on JDK 1.7.0_131 or JDK 1.8.0_121 or higher.
  • Support for JPedal 8.6.2 used in Document Management.
  • Bug fixes and list of known issues.

What’s new and changed in ColdFusion Builder (2018 release) Update 1

Comments (130)
2019-03-09 15:04:06
2019-03-09 15:04:06

Where can we download an offline installation package for the ColdFusion Builder 2018 Update 1? The update release notes at https://helpx.adobe.com/coldfusion/kb/coldfusion-builder-2018-update-1.html only have installation instructions for using the online update URL mechanism.

For past versions of Builder updates, the installation instructions had links to zip files for performing offline installation of the update, see e.g. CF Builder 2016 Update 4: https://helpx.adobe.com/coldfusion/kb/coldfusion-builder-2016-update-4.html

Like
2019-03-09 14:50:19
2019-03-09 14:50:19

I don’t think it’s mentioned anywhere, but a number of the supplementary downloads available for ColdFusion 2018 have refreshed installers available from February 2019:

https://www.adobe.com/support/coldfusion/downloads.html

As far as I can tell, the following installers were refreshed:

Add-on Services Installers for ColdFusion (2018 release)
ColdFusion (2018 release) .NET Integration Service Installer
ColdFusion (2018 release) Performance Monitoring Toolset
ColdFusion (2018 release) Server Auto-Lockdown

Significant here is that the PMT has a refreshed installer. I don’t know if this includes PMT Update 1 or not. Note that if you go to the main download link for CF 2018 (http://www.adobe.com/go/trycoldfusion) it still offers the old installer.

Note that the MD5 checksums posted on the download page are often wrong. For example, at the time of this comment, the MD5 checksum of the .NET Integration Service Installer still says 2541d06f9a0e99350f498276ec44adea, which is for the old installer.

Like
(1)
>
Legorol San
's comment
2019-03-09 17:35:58
2019-03-09 17:35:58
>
Legorol San
's comment

ColdFusion Builder 2018 installer also seems to have been refreshed.

Like
2019-03-09 14:42:39
2019-03-09 14:42:39

[editing the comment ate all the formatting, so I reposted it]

Like
2019-02-22 14:10:27
2019-02-22 14:10:27

Adobe has released today a new set of updates for cf2016 and 11, removing last week’s (no change for cf2018, though). See their new blog post (and comments there) for more: https://coldfusion.adobe.com/2019/02/coldfusion-2016-release-update-9-coldfusion-11-update-17-released/

Like
(1)
>
Charlie Arehart
's comment
2019-03-05 20:43:34
2019-03-05 20:43:34
>
Charlie Arehart
's comment

Actually I found the CF2016 had Update 10 available not Update 9 – but it didn’t fark up scheduled tasks…

Like
2019-02-21 22:43:27
2019-02-21 22:43:27

To folks trying to read this massive post (well, massive because of over 100 comments), you’ve probably struggled because the portal’s default behavior is to hide replies, to not easily see all replies AND comments in an option of reverse descending order, and more.

Check out:

https://coldfusion.adobe.com/2019/02/adobe-please-change-portal-working-posts-dozens-comments-5-proposed-enhancements/

I created that as a post here to ask Adobe for these features, since there’s no place in the Tracker to file issues about the Portal. (And I know the URL is ugly. The portal creates it, not the author.)

If you are interested in the above features and want to add your support, go check it out. (And before you may comment here based solely on what I said, please read the post first. I address various options, alternatives, and considerations. And I ACKNOWLEDGE there that Adobe should of course focus on the update problems, before portal issues!)

That said, I appreciate that this comment alone is “off-topic” for the blog post on the updates, but it’s on-topic because this is the most-commented post in the life of the new portal. And I suspect I am not alone in my frustrations. Since it’s not easy for readers to know otherwise that this other post exists, I felt this was the best place to mention it.

Like
2019-02-21 01:21:35
2019-02-21 01:21:35

Just installed CF2016 Update 8 on Server 2012 R2. The upgrade process completed successfully, I removed and re-added the Web Server Connector, upgraded to Java 8 Update 202. The CF Administrator was working properly, but all DataSources failed to verify or connect. Note, these are not ODBC Socket datasources – they are Microsoft SQL Server datasources using native JDBC.

Has anybody else experienced this issue? Is there a fix for this?

Where should I be looking for error information?

Can anyone help?

Like
(8)
>
Benjamin Reid
's comment
2019-02-21 05:31:39
2019-02-21 05:31:39
>
Benjamin Reid
's comment

Benjamin, I know you say the update was “successful”, but can you double-check to make sure there are no errors indicated in the install log for the update? see the cfusion\hf-updates folder, then the subfolder for this update 8, and in there see the install log (not the filelist log). Near the top of the will be a table of successes and errors. Are there 0 errors?

Like
>
Benjamin Reid
's comment
2019-02-22 12:12:05
2019-02-22 12:12:05
>
Benjamin Reid
's comment

Hi Benjamin,

I created a datasource using the native JDBC . I used the driver “mssql-jdbc-6.1.0.jre8.jar” to create the database . Then I applied update 8 . Verifying the database shows OK to me. Is there something that I am missing ?

Regards,

Suchika

Like
(1)
>
Benjamin Reid
's comment
2019-02-22 16:08:49
2019-02-22 16:08:49
>
Benjamin Reid
's comment

We also run the Microsoft native JDBC driver instead of the built in CF one of CF11 and CF2016.  We did not experience any issue post upgrade on either.  Which version of the JDBC driver are you running?  There have been updates along the way to support newer releases of Java.  We’re running mssql-jdbc-7.0.0.jre8.jar in production and mssql-jdbc-7.2.1.jre8.jar in development/testing right now.

Like
(1)
>
Leith Tussing
's comment
2019-02-22 16:38:32
2019-02-22 16:38:32
>
Leith Tussing
's comment

While Leith and Suchika are focused on Ben’s presentation of the problem as a possible JDBC issue, I will repeat my first reply to him, asking if instead this may just be the result of an error in the applying of the update (please read my first reply carefully, Ben, and don’t just say that you know “the update took”).

Errors in the RUNNING of the update are surprisingly common, and it can sometimes be that CF comes up even though there WERE errors, which ARE tracked in the update install log, if you look in the right place. and yet then some functionality may fail, while all else works.

So Ben, I hope you will let us know whether you had errors or not, as it would influence next steps and further comment.

Like
>
Benjamin Reid
's comment
2019-02-27 02:02:37
2019-02-27 02:02:37
>
Benjamin Reid
's comment

I am currently seeking assistance on this from the Adobe CF Team in India. They have remote connected to investigate the issue. They further suggested we load Update 9 to fix any other issues, which we did, with the same outcome.

Something additionally relevant to the discussion is that we use SSL encrypted connections to SQL Server with a wildcard certificate connecting to SQL on LOCALHOST.

With the Adobe team connected we were able to get the datasources to verify, BUT only when NOT using SSL encryption.

We have since verified the configuration of our SSL encryption in SQL Configuration Manager and also in RegEdit.

We also reverted the VM back to the snapshot prior to loading Update 8/9, where everything was working. We then loaded Update 9 from the Administrator (skipping Update 8), with again the same outcome.

@Charlie – yes I checked the log for Update 8, no failures. I did not check the log for Update 9.

Our current thinking is this issue is limited to JDBC Microsoft SQL Server DataSources that use SSL encryption with the Connection String: “EncryptionMethod=SSL; CryptoProtocolVersion=TLSv1.2; ValidateServerCertificate=0;”.

Adobe are continuing to provide support on this. I will post with an update again when I have more information.

Like
>
Leith Tussing
's comment
2019-02-27 02:07:57
2019-02-27 02:07:57
>
Leith Tussing
's comment

I haven’t tried using the Microsoft native JDBC driver because the built-in one has always worked for us.

What were the reasons you chose to use the native one over the built-in?

I am not familiar with the steps for how to use/configure the MS native one – do you have any resources that point to that?

Like
>
Benjamin Reid
's comment
2019-03-05 23:29:30
2019-03-05 23:29:30
>
Benjamin Reid
's comment

Nimit Sharma from Adobe has confirmed my issue with JDBC Microsoft SQL Server DataSources that use SSL encryption with the Connection String: “EncryptionMethod=SSL; CryptoProtocolVersion=TLSv1.2; ValidateServerCertificate=0;”.

The hotfix updated the macromedia_drivers.jar library, and apparently currently has an issue with SSL encrypted datasources.

They offered a work-around that is safe to use on production servers:

Apply the latest update on your CF2016 server.
If the data source configured with SSL does not work, then stop CF2016 service
Copy macromedia_drivers.jar available inside the backup folder [i.e. <cf_install_root>/<instance_name>/hf-updates/<hf-2018-0000*-******>/backup/lib/] and place it in <cf_install_root>/<instance_name>/lib folder.
Start CF2016 service
Verify the data source.

This work-around has been successful for us.

Adobe is continuing to investigate.

Like
>
Benjamin Reid
's comment
2019-03-12 07:44:01
2019-03-12 07:44:01
>
Benjamin Reid
's comment

Bug: DataSource SSL Encryption broken with CF2016 Update 8/9/10 and CF2018 Update 3

https://tracker.adobe.com/#/view/CF-4204087

Like
2019-02-20 19:10:15
2019-02-20 19:10:15

Attachment

Trying to upgrade to Cf2016 update 8.  I installed the update from the administrator.  That worked fine. Service restart fine.  The ODBC server didn’t restart, but the fix mentioned above resolved that issue.  Installed Java 11 from the adobe link and changed the path in the jvm.config and CF App server won’t restart! I also installed java 8_202 so I bounced back to it and CF is fine on it.  The windows system error is in the attached jpg file, but it says: The ColdFusion 2016 Application Server service terminated with the following service-specific error:
The system cannot find the file specified.

I have verified the java location but CF is not happy on Java11.  Any thoughts?

Like
(1)
(6)
>
rcasdorph
's comment
2019-02-21 05:34:41
2019-02-21 05:34:41
>
rcasdorph
's comment

rcasdorph, are you sure that the bit-level of your CF is the same as the bit-level of the JVM you got (32-bit or 64-bit)? If so, what is the line of code you used to update the jvm.config? Did you save it as a comment? Did you point to the JRE folder within the new JVM? And since this is Windows, did you escape the \ separator to be \\ or /, as is required by Java on Windows?

Like
>
Charlie Arehart
's comment
2019-02-21 15:12:53
2019-02-21 15:12:53
>
Charlie Arehart
's comment

The current java version is 8_201 – Java HotSpot(TM) 64-Bit Server VM.

I can run java from the 11 folder and I get Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)

I selected the version in the administrator so I assume it will correctly enter the path. 

This fails: java.home=C:/Program Files/Java/jdk-11.0.2

This works: java.home=C:/Program Files/Java/jre1.8.0_201

Anything else to try?

Like
>
rcasdorph
's comment
2019-02-21 15:34:14
2019-02-21 15:34:14
>
rcasdorph
's comment

Yes, there is something else you need to do. We can tell from the paths you list (though I realize it was not clear to you).

Point to the jre folder under the jdk folder. Your cf8 jvm WAS a JRE, so the top-level path was enough there.

Let us know if that works.

Like
>
Charlie Arehart
's comment
2019-02-21 15:44:13
2019-02-21 15:44:13
>
Charlie Arehart
's comment

Attachment

There isn’t a JRE folder.  I attached a screenshot.  I’m feeling pretty stupid. This feels like it should be easy. The graphic doesn’t show it, but there are 6 folders: bin, conf, include, jmods, legal, and lib. 

Like
>
rcasdorph
's comment
2019-02-21 16:12:16
2019-02-21 16:12:16
>
rcasdorph
's comment

Agh, you’re right. I’m sorry. I was myself lulled into recalling how things were before Java 11 (and 10). The JDK install does NOT in fact have a JRE subfolder (like it did for Java 8 and below).

I will tell you that in my current CF2018 implementation, on update 2 (but not yet having updated to using Java 11), the CF Admin “java and jvm” page setting for “java virtual machine path” shows this:

C:/Program Files/Java/jdk-10.0.2

That matches what you have. So it’s certainly odd that you are getting the error you do.

What else to consider?

  • you say you applied update 8 for CF2016, which is of course required for you to be able to use CF2016 with Java 11. Can you check the cfusion/hf-updates subfolder for your update 8, and view its install log, to see its table of successes and errors (near the top of the log), to make sure there were no errors during the install?
  • I know you said you tested java in the jdk11 folder, and the result shows it reported being a 64-bit JDK. There’s the SLIGHTEST possibility that you have some other “public jre” on the box that could be 64-bit while this one is not. If instead you went to that java 11 bin folder, at the cmd line, and used “./java -version”, that would ensure it looks in THAT folder for the java when reporting its version. What does it report? If it may differ from the above, you can also use “where java” command to ask Windows to tell you where it had found the java command when you typed it before without the “./”  (And I know it’s not likely this is the issue, since this Java 11 is indeed in the program files, which means it should be a 64-bit app. But one could FORCE something there. These are merely sanity checks, given the oddity of your problem.)
  • Finally, I suppose you COULD try Java 10 instead. Not that you should have to, and while Adobe doesn’t formally say they support it, usually if they support a higher number (as CF2016 update 8 now supports Java 11), that should implicitly mean that it should support 10, though not necessarily. Again, this is more just a sanity check for you.

Let us know what you find. Something surely seems amiss. And if you may be curious to read more, I covered a lot of these things (about how you can try to change the JVM that CF uses, and find it won’t start) in a blog post in 2014:

http://www.carehart.org/blog/client/index.cfm/2014/12/11/help_I_updated_CFs_JVM_and_it_wont_start

Sure, that’s from before Java 11 (or 10 or 9), but the concepts, techniques, mistakes, and solutions do still apply.

Hope that helps.

Like
>
Charlie Arehart
's comment
2019-02-28 21:53:01
2019-02-28 21:53:01
>
Charlie Arehart
's comment

Thanks for your help Charlie…Here’s what to do to figure it out.

Run cfstart and see what errors you get and then fix them…

I took the following crap out of my JVM and then it runs fine!
D:\ColdFusion2016\cfusion\bin>cfstart.bat
Unrecognized VM option ‘UseGCLogFileRotation’
Could not create the Java virtual machine.
 
D:\ColdFusion2016\cfusion\bin>cfstart.bat
Unrecognized VM option ‘NumberOfGCLogFiles=3’
Could not create the Java virtual machine.
 
D:\ColdFusion2016\cfusion\bin>cfstart.bat
Unrecognized VM option ‘GCLogFileSize=10240k’
Could not create the Java virtual machine.
 
D:\ColdFusion2016\cfusion\bin>cfstart.bat
Unrecognized VM option ‘PrintGCTimeStamps’
Could not create the Java virtual machine.
 
D:\ColdFusion2016\cfusion\bin>cfstart.bat
Unrecognized VM option ‘PrintHeapAtGC’
Could not create the Java virtual machine.
 

Like
2019-02-16 15:33:08
2019-02-16 15:33:08

Saurav, I see you have added an update to the top of the blog post indicating known issues. Thanks very much for that.

But why don’t you list there the other issues that have been brought here by several people:

  • The update may fail if the windows user running cf is not specifically listed in the administrors group
  • Those using the cf odbc services will find those don’t start unless the manually copy in the needed mscvr dll

If there are others, folks, please comment here so he can get them listed also. (And Saurav, you may want to add another mention after your new points to lead folks also to the existing known issues doc that was offered at release.)

Like
(2)
>
Charlie Arehart
's comment
2019-02-16 16:16:33
2019-02-16 16:16:33
>
Charlie Arehart
's comment

Thank you Charlie. We shall update the blog when we have more information regarding the issues.

Like
>
Charlie Arehart
's comment
2019-02-18 17:33:33
2019-02-18 17:33:33
>
Charlie Arehart
's comment

[Following]

Like
2019-02-16 05:02:21
2019-02-16 05:02:21

Woah, was there a refresh to the CF2018 Installer, too? which incorporates update 2 AND Java 11? It seems so, but it has not been mentioned here or in the release notes.

I was working with someone tonight who had gotten a CF2018 installer today, and we were shocked to find this was the case. One oddity: though “settings summary” showed that it was on CF2018,0,2,[somenumber] and the JVM was indeed 11.0.1, we found that the available updates AND the installed updates both listed “update 2”. And the installed updates clearly said that update 2 was pre-installed. But more odd, the “starbust” in the top right of the Admin also showed a 1. Something is not right about all that, but it’s great to see the installer incorporating the update and new jvm.

That said, we really need to know about this (it should be announced), because it does affect things. Also, in the past, installer refreshes also slipped in still OTHER changes. If there are any known differences implemented by this new installer, please do let us know that also.

Like
(1)
(6)
>
Charlie Arehart
's comment
2019-02-16 11:56:22
2019-02-16 11:56:22
>
Charlie Arehart
's comment

Charlie, actually this page, linked from the blog post, has mentioned the installer refresh right from the start: https://helpx.adobe.com/coldfusion/kb/coldfusion-2018-updates.html

It is true that it’s not mentioned in the blog post itself, nor are there details about the refresh as you point out.

Like
>
Legorol San
's comment
2019-02-16 15:25:30
2019-02-16 15:25:30
>
Legorol San
's comment

Ah, yes. Thanks. But yep, more attention or even a separate blog post may be warranted. There has been one for past installer refreshes.

That said, past refreshes didn’t get indicated like that in the updates page, so that’s an improvement. But it’s also why I didn’t even think to look there for news of such. 🙂

So again, thanks for pointing it out.

Like
>
Charlie Arehart
's comment
2019-02-18 13:22:21
2019-02-18 13:22:21
>
Charlie Arehart
's comment

@Charlie – The refreshed installers have Java 11 and Update 2 baked in. The “bulb” notification showing “1 update available” can be ignored as installing the same does not change anything.

Like
>
Vamseekrishna Nanneboina
's comment
2019-02-18 14:02:05
2019-02-18 14:02:05
>
Vamseekrishna Nanneboina
's comment

Vamseekrishna, thanks for clarifying. But are you saying something will be done to fix that? It’s certainly going to cause confusion (along with it also listing update 2 as both installed and available).

And the other question still stands: are those changes (the inclusion of update 2 and java 11) really ALL that was added/changed in this refresh? Definitely nothing else?

Like
>
Charlie Arehart
's comment
2019-02-19 10:00:55
2019-02-19 10:00:55
>
Charlie Arehart
's comment

Regarding #2, the primary reason for refreshing the installers was to bundle Java 11, so the scope was kind of limited to Java 11 and Update 2 bug fixes. We’ve also added support for the Lockdown installer for Mac OS X.  We will see if anything can be done to fix #1 outside of refreshing the installers again.

Like
>
Vamseekrishna Nanneboina
's comment
2019-02-19 14:53:48
2019-02-19 14:53:48
>
Vamseekrishna Nanneboina
's comment

Thanks. So two points:

First, as for what changed in the refreshed cf2018 installers, you say it was “kind of limited” to baking in update 2 and Java 11. Can you confirm there was nothing else? (The lock down installer you mention would be a separate download.)

Second, as for the confusion about that new installer causing the admin to show update 2 as available (despite already having it), and whether you should create a new installer to fix that… well, this issue would affect people for months if unchanged, until the next update. I can see it leading to lots of confusion.

Granted, there’s already going to be confusion as many never notice the new installer, and some will continue to use the original installer while others use the new one (this one from last week). Adding a 3rd to the mix does increase the complexity of that. Always trade-offs.

Actually, this raises an interesting thought: perhaps the cf installer UI should be modified (going forward) to have a screen offering to check if the installer being used is indeed the latest one available for that release.

This issue of multiple generations of installers for a given release and is (changing over time for various reasons) is not new. And it will likely happen in future releases. A check in the installer could help with this.

(And yes, I realize it would only help those with an internet connection on the machine where cf is being installed. The installer page could indicate what installer they have and offer a link for people to go to a page–via another computer–which would show the different iterations of installers for that release and that OS, or at least offer the latest. At least this way, the user would know if their installer was NOT the latest for that release and OS.)

Complicating? Perhaps. But it’s due to your having had multiple generations of installers for a given release.

Like
2019-02-16 02:06:10
2019-02-16 02:06:10

Scheduled Tasks are gone (CF11 & CF2016) Wow! do you not test these things, before release? Is this “Abode” a new startup software company with a completely incompetent staff

Like
(1)
(2)
>
gtbsf81
's comment
2019-02-21 21:29:25
2019-02-21 21:29:25
>
gtbsf81
's comment

Yeah. Backed up the neocron.xml file (a remnant of ColdFusion MX). Did the updated and yes broken. Copied my backup neocron.xml file across and restarted server. Still broken with this error:

The following information is meant for the website developer for debugging purposes.

Error Occurred While Processing Request

The system has attempted to use an undefined value, which usually indicates a programming error, either in your code or some system code.Null Pointers are another name for undefined values.

The error occurred in scheduletasks.cfm: line 201

-1 : Unable to display error’s location in a CFML template.

Like
>
Peter Tilbrook
's comment
2019-02-22 01:21:39
2019-02-22 01:21:39
>
Peter Tilbrook
's comment

Peter, the solution is discussed in other comments here, and on the bug ticket:

https://tracker.adobe.com/#/view/CF-4204021?1

It’s that you need to add an “archived” element to your tasks (each of them, in the neo-cron.xml file–even the one you recover from before the update). You need to top CF, recover the file, edit it this way, and then restart CF for the tasks to all work, at least until Adobe fixes the update.

Like
2019-02-15 18:25:24
2019-02-15 18:25:24

My CF 2016 ODBC Server Service would not start after I manually installed the update. When I ran the service command manually in the command prompt, it told me that would not start because the MSVCR100.dll was not in the \cfusion\db\slserver54\bin folder. I fixed this problem by copying the MSVCR100.dll from my JAVA JDK bin folder to the \cfusion\db\slserver54\bin folder.

Like
(2)
(1)
>
Vincent Krist
's comment
2019-02-15 19:18:18
2019-02-15 19:18:18
>
Vincent Krist
's comment

I’ll add this to my issue/workaround list below.  I did not have this happen on our CF2016 install so I didn’t add it to that area.

Like
2019-02-15 18:24:57
2019-02-15 18:24:57

Could you please elaborate on this known issue:

Issue #2

An exception occurs when returning the result of queryExecute from a function in a CFC

This sounds like a complete showstopper for a lot of my applications!

Like
(2)
>
Hemi345
's comment
2019-02-18 13:39:17
2019-02-18 13:39:17
>
Hemi345
's comment

The below bug report has the details:

https://tracker.adobe.com/#/view/CF-420402

Also, what version of ColdFusion are you on?

Like
>
Vamseekrishna Nanneboina
's comment
2019-02-20 18:34:20
2019-02-20 18:34:20
>
Vamseekrishna Nanneboina
's comment

CF2016.

Like
2019-02-14 14:48:43
2019-02-14 14:48:43

Issues with workarounds to problems I’ve experienced with these updates on CF11 and CF2016 in one post instead of all over the place.

Issue 1 – No Administrative Privilege during manual installation (CF11 & CF2016)

Cause – The installer is looking for your logged in Windows user account to be in the local administrators group.  If your account is in another local group or domain group the installer doesn’t think you’re an administrator.

Workaround – Add your logged in account to the local administrators group.

 

Issue 2 – ColdFusion 11 ODBC Server service fails to start (CF11)

Cause – The CF11 HF15 and HF16 installer delete without backing up the CF\cfusion\db\slserver54\bin\msvcr71.dll from the system which is required for the ColdFusion 11 ODBC Server service to start.

Workaround – Backup the file before installing and then restore after updating.  You can grab the file from another installation or previous backup.

 

Issue 3 – Scheduled Tasks are gone (CF11 & CF2016)

Cause – With HF16 the neo-crons.xml file must have a var named cluster that didn’t exist in previous jobs if you had upgraded from older versions of CF.  If the neo-crons.xml does not have this value in every job it will wipe out the contents of your neo-crons.xml file.

Workaround – Manually edit a backup copy of the neo-crons.xml adding <var name=’clustered’><boolean value=’false’/></var> to each job and then replace the wiped out copy with this one and restart the services.  If it gets wiped out again you missed a job.  You can also rebuild all of your jobs by hand too.

Like
(8)
(11)
>
Leith Tussing
's comment
2019-02-14 16:46:18
2019-02-14 16:46:18
>
Leith Tussing
's comment

I created a bug report for Issue 3:https://tracker.adobe.com/#/view/CF-4204021

Lots of people are reporting this: https://forums.adobe.com/thread/2595082

FYI Adobe is apparently aware of this issue.

Like
(1)
>
Leith Tussing
's comment
2019-02-15 12:53:07
2019-02-15 12:53:07
>
Leith Tussing
's comment

Very, very helpful. Thanks, Leith (and Pete).

Like
>
Leith Tussing
's comment
2019-02-15 19:34:55
2019-02-15 19:34:55
>
Leith Tussing
's comment

I wanted to add this info here, someone reported that the issue 2 above happened to them with CF2016 as well.  The DLL name is slightly different to backup & recover.

 

CF/cfusion/db/slserver54/bin/MSVCR100.dll

 

The reason mine likely worked is I have the MS VC++ 2010 redistributable installed which is what MSVCR100.dll is part of but I do not have Visual Studio .NET 2003 redistributable installed (as it is no longer supported) which msvcr71.dll is part of.  I looked in my CF2016 folder and that dll is missing.  Using Process Monitor I can watch it go find it in the Windows folder where CF11 cannot find the older copy as I do not have it installed at the system level which then requires the file to be in the folder to operate.

Like
>
Leith Tussing
's comment
2019-02-18 19:00:43
2019-02-18 19:00:43
>
Leith Tussing
's comment

I should add here also that this problem about scheduled task loss does ALSO happen in CF2018 (not just CF11 and 2016 as indicated above).

That said, it does seem to be unique to when folks had previously imported or migrated tasks from a previous edition that did NOT put that cluster element in place (or it may have put it in as a string vs a boolean). I’m not minimizing the problem at all: just explaining that it may not hit EVERYONE using sched tasks, but those with certain characteristics, which is worth knowing (and I hope Adobe will clarify or at least consider as they resolve things).

Like
>
Charlie Arehart
's comment
2019-02-19 07:43:50
2019-02-19 07:43:50
>
Charlie Arehart
's comment

Hi Leith,

Regarding issue #1 , can you please confirm if the issue does not occur in CF 11 update 15 or earlier updates since no changes have been done to the update installer. We tried to simulate the same at our end, but we were unsuccessful . We can have a detailed discussion over email, can you share your email address at suchsing@adobe.com?

Thanks & Regards,

Suchika

Like
>
Charlie Arehart
's comment
2019-02-19 12:38:39
2019-02-19 12:38:39
>
Charlie Arehart
's comment

Hi Charlie,

Are you sure that Schedule task issue occurs with CF 2018 ? We acknowledge that this is an issue in CF 11 & CF 2016  but should not be an issue in Cf 2018.

Regards,

Suchika

Like
>
Suchika Singh
's comment
2019-02-19 13:40:04
2019-02-19 13:40:04
>
Suchika Singh
's comment

Suchika, this issue started with CF11 update 15 and did not exist before then.  There’s a long thread about this issue when CF11 update 15 dropped.  That update and update 16 delete the msvcr71.dll file from that folder without backing it up and there is no replacement.

 

https://forums.adobe.com/thread/2534653

Like
>
Suchika Singh
's comment
2019-02-19 14:22:37
2019-02-19 14:22:37
>
Suchika Singh
's comment

Suchika, yes, I am confirming the scheduled task issue happened on cf2018.

As I reported in the other long comment about the issue last week (where Leith shared the solution), I was working with a client who experienced the issue, and we solved it by modifying the cluster element.

Again, the issue seems to be related to whether the tasks had been previously imported from an earlier edition. Is that what you’re finding, too, but you’ve not been able to force it on cf2018?

Like
>
Charlie Arehart
's comment
2019-02-21 22:25:01
2019-02-21 22:25:01
>
Charlie Arehart
's comment

The backup folder for all CF2016 updates appear to NOT nake a backup of the neo-cron.xml file…

Like
>
Peter Tilbrook
's comment
2019-02-21 22:35:01
2019-02-21 22:35:01
>
Peter Tilbrook
's comment

No, Peter, it does not. Then again, I don’t see anyone here saying that it did. But perhaps you were inferring that from the mentions of a “backup” of the neo-cron.xml. Folks were referring to the neo-cron.bak that CF creates.

Anyway, to your saying you don’t find it in the backup folder for the updates, that is true that it does not. But someone asked about that in a vote on the tracker bug ticket for this issue (https://tracker.adobe.com/#/view/CF-4204021?1), and I addressed that with a comment. Since we can’t point to specific comments in Tracker (that I can see), I am repeating it here for you and anyone else who may see/ask the same question:

Eric asks in a vote comment (on the right), “Trying to find a backup neo-cron file. Why doesn’t the updater save a backup??”

My answer will be of little consolation, but FWIW, it’s not the updater that lost the neo-cron.bak file. It was the first launch of CF, which when it found your neo-cron.xml didn’t have what it liked (because of a mistake in the updater), it was THEN that your neo-cron files got messed up. (I saw this with a client, though I didn’t notice if it first saved off the existing neo-cron.xml over the bak, or it saved what it now modified, removing what it saw as “bad” tasks, over the bak.)

Anyway, I know that’s a technicality. You wish CF would have done a better job to save the tasks. (That’s really a bigger discussion, because CF also overwrites the bak file WHENEVER a task simply RUNS, not just when tasks are added/edited/deleted. That’s because it holds not only the DEFINITION of the tasks but info about the last EXECUTION of any.)

I’m simply pointing out that technically there was nothing in the updater that was SUPPOSED to mess with the neo-cron.xml, so there was no reason therefore for them to have thought to back it up as part of the update. And I can confirm, there are NO neo files in the cfusion\hf-updates\hf-2018-00002-313961\backup\lib folder (nor have their been in the lib folders of backups for MOST CF updates, as the updater only backs up the files it IS knowingly changing).

Oh, and as for that “bigger discussion” of concerns with how CF only keeps ONE generation of the neo-*.bak files, and worse how it UPDATES that neo-cron.xml (and therefore backs it up to the .bak) file WHENEVER A TASK RUNS. That’s a problem I’ve complained about for a long time.

For any interested, search that ticket above for my reference to and subsequent discussion of https://tracker.adobe.com/#/view/CF-4200009, and then go view and vote on that as well.

Like
>
Peter Tilbrook
's comment
2019-02-22 04:07:05
2019-02-22 04:07:05
>
Peter Tilbrook
's comment

Peter, FWIW, I replied to this comment of yours earlier today, but somehow I’m not seeing it here. I don’t know if it may be awaiting some moderation. But in case it’s not, I don’t want to forget to reply with at least something, so here’s another attempt (not including any URLs, if that may have been the issue).

About what you say, it’s not that anyone did say here that they do (or should) expect the neo-cron.xml to be backed up by the updated. They were talking about the loss of the .bak (backup) file.

But I appreciate that you may indeed wonder why the updater did not back that file up. I have an explanation of that, as someone else did ask that, today, on the Adobe tracker bug report on this, CF-4204021 (at tracker.adobe.com).

See my reply to that, as one of the last comments currently there earlier today. You can search (in your browser find) for the comment starting with the words:

Eric asks in a vote comment (on the right), “Trying to find a backup neo-cron file. Why doesn’t the updater save a backup??”

And then I share my answer to that, if it may be of help for you.

Like
2019-02-14 01:03:54
2019-02-14 01:03:54

Will there be an update for ColdFusion Builder 2016 too?

Like
(3)
>
Legorol San
's comment
2019-02-14 13:43:03
2019-02-14 13:43:03
>
Legorol San
's comment

No plan for the same as of now.

Like
>
Vamseekrishna Nanneboina
's comment
2019-02-14 16:46:12
2019-02-14 16:46:12
>
Vamseekrishna Nanneboina
's comment

Builder 2016 is still very much under support (and even Builder 3.x until Apr 2019), both of which suffer from many of the same bugs that were fixed in Builder 2018 with this update. Can we please have these bugs fixed?

Like
>
Legorol San
's comment
2019-02-15 04:04:42
2019-02-15 04:04:42
>
Legorol San
's comment

@Legoral – We can evaluate porting back some critical bug fixes to CFB 2016.

Like
2019-02-14 01:02:58
2019-02-14 01:02:58

What are the exact licence terms and conditions for using the versions of Java 8 and Java 11 posted on the Downloads page linked in the blog post? Under Additional Third Party Installers there is a Terms of Use entry with two links:

https://www.adobe.com/legal/licenses-terms.html, which is just the general licence terms for various Adobe products.

http://www.adobe.com/go/thirdparty, which links to a PDF containing thousands of third-party licence notices, and it’s unclear which, if any, is applicable to the Java downloads.

In particular, I’m looking for the exact terms under which Adobe provides versions of Java now (and going forward) for production use. As the users, we are not in a direct relationship with Oracle, only with Adobe, so I’d like to know the terms and restrictions for production use of Java. (For example, only permitted to use in conjunction with ColdFusion, or any other restrictions).

 

Like
(4)
(3)
>
Legorol San
's comment
2019-02-15 03:58:16
2019-02-15 03:58:16
>
Legorol San
's comment

Legorol Take a look at this blog post clarifying the usage of Java: https://coldfusion.adobe.com/2019/01/oracle-java-support-adobe-coldfusion/

 

Like
>
Rakshith Naresh
's comment
2019-02-16 12:05:09
2019-02-16 12:05:09
>
Rakshith Naresh
's comment

I have read that blog post multiple times, i even asked a question in the comments about this, which you responded to.

The point is that the blog post is just a casual explanation in layman’s terms. While that is very useful and I appreciate it, it’s not quite enough.

As of now, I can’t find any legal terms and conditions that govern our production usage of Java based on the installers that Adobe is making available. This has my organisation concerned, we have no legal document to point to in case of an audit.

If we are found using eg Java 11 in production, and all we can say is “Adobe said it’s ok”, we are on pretty thin ground.

Like
(4)
>
Legorol San
's comment
2019-03-04 17:40:20
2019-03-04 17:40:20
>
Legorol San
's comment

Has there ever been a clarification on this point, which Legorol and others have raised?

Like
2019-02-13 23:43:13
2019-02-13 23:43:13

Great news on the Windows Server 2019 support for CF2018. When will the support matrix be updated to match?

Like
(1)
(2)
>
Joshua Todd Cowper
's comment
2019-02-14 06:54:28
2019-02-14 06:54:28
>
Joshua Todd Cowper
's comment

We’ll update it shortly.

Like
(2)
>
Joshua Todd Cowper
's comment
2019-02-15 07:10:30
2019-02-15 07:10:30
>
Joshua Todd Cowper
's comment
Like
(2)
2019-02-13 19:00:24
2019-02-13 19:00:24

I am unable to install Update 8 on our CF 2016 server. The server is running CF 2016 Update 7 on Windows Server 2008 R2. Coldfusion 2016 was originally installed using Pete Freitag’s lockdown guide and we have never had any problems installing the previous updates. The Coldfusion services are running under a domain user.

 

My first attempt to install CF 2016 Update 8 failed with what appeared to be privilege issues noted in the installation log, I restored the server to our latest backup from before the upgrade attempt and added the domain user that is running the CF service to the local administrator group so it has full access to the files and folders that the installation log says it could create files in.Unfortunately, I still got the same three problems:

Problem 1 – Coldfusion Admin Update page blew up

I used the ColdFusion Administrator to download and install the update. The process proceeded normally and the service restarted and I saw the login page for the administrator but after I logged in the updates page threw this error:

 

The getProxyHost method was not found.

Either there are no methods with the specified method name and argument types or the getProxyHost method is overloaded with argument types that ColdFusion cannot decipher reliably. ColdFusion found 0 methods that match the provided arguments. If this is a Java object and you verified that the method exists, use the javacast function to reduce ambiguity.

 

The error occurred in C:/(redacted)/cfusion/wwwroot/CFIDE/administrator/updates/_settings.cfm: line 345

Called from C:/(redacted)/cfusion/wwwroot/CFIDE/administrator/updates/_settings.cfm: line 135

Called from C:/(redacted)/cfusion/wwwroot/CFIDE/administrator/updates/_settings.cfm: line 1

Called from index.cfm: line 206

Called from index.cfm: line 78

Called from index.cfm: line 77

Called from index.cfm: line 1

 

Problem 2 – Installation was unable to create/copy files

An example of one of the 23 fatal errors from the Adobe_ColdFusion_2016_Update_8_Install_02_13_2019_09_32_41.log file that makes no sense to me is listed below:

 

Moving files failed:

Status: FATAL ERROR

Additional Notes: FATAL ERROR – Could not move the file C:\(redacted)\cfusion\lib\updates\chf20160007.jar to the backup location C:\ (redacted)\cfusion\hf-updates\hf-2016-00008-313934\backup\lib\updates\chf20160007.jar

 

Problem 3 – Services are gone

I also noticed that the Windows Services Panel no longer has the “Coldfusion 2016 ODBC Agent” and “Coldfusion 2016 ODBC Server” services at all. The other services are present.

I did run wsconfig as administrator after all the errors I found above but it unsurprisingly made no difference.

 

 

Like
(1)
(2)
>
Vincent Krist
's comment
2019-02-13 19:10:55
2019-02-13 19:10:55
>
Vincent Krist
's comment

This is the issue I usually see happen when I’ve tried to do the install via the admin in the past.  It’s not a permissions issue but the files are locked by CF/Java still.  From my experience the CF services are sent a shutdown command but they’re still in memory when the install process kicks off before everything has fully shutdown.  Because of this some files are still locked by the processes running and cannot be removed/replaced.  I’ve used Process Monitor and watched this happen a number of times which is why I do all of the updates manually.

 

Your install is in a bad state, the best way to resolve this I’ve found is to roll back the update by using the uninstall.jar in the HF folder and then manually install the update again with the CF services shutdown first.

Like
(1)
>
Leith Tussing
's comment
2019-02-13 22:27:03
2019-02-13 22:27:03
>
Leith Tussing
's comment

Thanks! The manual installation process from the command prompt worked for me.

Like
2019-02-13 15:59:37
2019-02-13 15:59:37

I’m showing that scheduled tasks are removed from admin after upgrading on multiple test servers, neo-cron.bak is not showing any prior tasks. CF 2016 Update 8, Windows Server 2008 R2

Like
(3)
(7)
>
Chris Reese
's comment
2019-02-13 18:44:28
2019-02-13 18:44:28
>
Chris Reese
's comment

Same isssue here. CF11 Standard, Update 16.  After applying update, all scheduled tasks are gone and even neo-cron.bak is empty.  Tried putting a backup copy of our neo-cron.xml file to replace the new one (stopped and started server), and it just did the same thing, wiped the neo-cron.xml clean again.  All scheduled tasks deleted!!

Like
(1)
>
gstboces1
's comment
2019-02-13 21:12:12
2019-02-13 21:12:12
>
gstboces1
's comment

Manually recreating your schedule tasks in cfadmin, it worked for me.

Like
>
Chris Reese
's comment
2019-02-14 01:20:42
2019-02-14 01:20:42
>
Chris Reese
's comment

I found the root cause.  With the new hotfix it expects there to be a new var named cluster that didn’t exist in previous jobs.  If any job is missing this new var the system will wipe out all of your crons.  If you edit your old neo-cron.xml file and add it to each job you can then restore your previous jobs by putting the file in place.

 

<var name=’clustered’>
<boolean value=’false’/>
</var>

Like
(3)
>
Leith Tussing
's comment
2019-02-14 09:15:25
2019-02-14 09:15:25
>
Leith Tussing
's comment

Hi ,

The entry :

<var name=’clustered’>
<boolean value=’false’/>
</var>

has been a part of neo-cron.xml from CF 10 . So any task that was created in CF 11 should have this entry . I am not sure why did your tasks not have this entry from before. Did you migrate your tasks from an earlier version of CF ? We might not have handled this scenario and can be a bug .

Thanks,

Suchika

 

 

Like
(1)
>
Suchika Singh
's comment
2019-02-14 13:48:43
2019-02-14 13:48:43
>
Suchika Singh
's comment

Yes, these are systems that have been upgraded from older versions of CF through the years.  It’s triggered on all of our development upgrades so far and I’ve had to rebuild the crons on all of them.

Like
(1)
>
Leith Tussing
's comment
2019-02-14 14:45:43
2019-02-14 14:45:43
>
Leith Tussing
's comment

Great find Leith, was able to resurrect all tasks.

Thanks for your help

Like
(1)
>
gstboces1
's comment
2019-02-14 18:26:11
2019-02-14 18:26:11
>
gstboces1
's comment

We have noticed the same loss of all scheduled tasks after the CF2016 update 8 on RHEL 7.

Like
2019-02-13 15:06:32
2019-02-13 15:06:32

Does anyone from Adobe monitor the #Adobe channel on CFML Slack?   I’ve had issues with these updates on CF2016 and there are others posting about issues as well.

I’m getting:  Incompatible object argument for function call

Others are reporting issues with queryExecute

Like
(1)
(3)
>
Jim Priest
's comment
2019-02-13 15:13:28
2019-02-13 15:13:28
>
Jim Priest
's comment

Jim, thanks for reporting. Could you share more details on saghosh@adobe.com, and we shall look into it.

Like
(1)
>
Jim Priest
's comment
2019-02-13 17:57:00
2019-02-13 17:57:00
>
Jim Priest
's comment

Jim,

Did you try to flush out the old classes as advised by Suchika on your other comment?

It would help if you can get the detailed stack trace for that error in the exceptions.log file. That should probably point to the defaulting function.

To elaborate, all the classes from compiled CFMLs go in <cf_root>/cfusion/wwwroot/WEB-INF/cfclasses directory. If your trusted cache is enabled, the old classes may continue to be used. So could  you delete all the classes in this directory and restart the server for a good measure.

The issue with queryExecute is when you are using it in a specific manner. ie, when the result from the operation is being stored in a struct or other data structure rather than a variable. We’ll be sharing more details and the fix for that soon.

Like
(1)
>
Jim Priest
's comment
2019-02-15 17:59:23
2019-02-15 17:59:23
>
Jim Priest
's comment

I sent in stack track and the new jar file sent over resolved my ” Incompatible object argument for function call” issue:  hf201600-4204019.jar

Hopefully that gets rolled into the other fixes and you guys do an Update 9.  I really hope you don’t try to update the update and ‘fix’ Update 8.

Like
2019-02-13 09:35:41
2019-02-13 09:35:41

All, we have updated this blog with information about ColdFusion Builder (2018 release) Update 1.

Like
(2)
2019-02-13 04:10:04
2019-02-13 04:10:04

Please correct the pubDate field in the Updates XML, currently it says the updates were released on February 12, 2018 – which should of course be 2019.

See https://cfdownload.adobe.com/pub/adobe/coldfusion/xml/updates.xml

Like
(1)
(2)
>
Benjamin Reid
's comment
2019-02-13 06:56:00
2019-02-13 06:56:00
>
Benjamin Reid
's comment

Thanks for flagging this Benjamin. We are working on it.

Like
(1)
>
Benjamin Reid
's comment
2019-02-13 07:29:59
2019-02-13 07:29:59
>
Benjamin Reid
's comment

Thanks for reporting , we have fixed it.

 

Like
(2)
2019-02-13 03:34:42
2019-02-13 03:34:42

Leith and Darren, I have run the same updates in the same ways you have described, and I did not get the error.

So first, can you guys be more specific about where you see the error about permissions?

Second, given the mention of permissions, some may wonder if this has to do with having run the CF2018 auto lockdown, like I mentioned in a previous comment. Darren, have you? In Leith’s case, he is reporting this with CF2016 which does not have the lockdown tool. But did either of you apply any “lockdown” by following the lockdown guide? It may not matter, but it’s a useful point for us to ponder.

So Leith, I have run the CF2016 update 8 today on a Server 2008 R2, with no problem. And yep, I ran it from the command line (as admin). I got no error about privileges. That’s why I would like to hear where you saw the error. I had none in the Java UI, I had none in the hf-updates log for the update.

And Darren, I applied CF2016 update 8 on a Windows Server 2016 machine (and a Windows 10 machine) as well. I did that via the Admin (you don’t indicate if you used the Admin or the command line, like Leith). Again, it worked. There were no errors of any sort about permissions (in the CF admin popup about the update progress, or in the hf-update log file for the update.)

FWIW, I will report that I had one non-fatal error in that log (with the CF2016 update on the Server 2016 machine), but CF came up no problem. It reported: “Unable to delete directory C:\ColdFusion2016\cfusion\wwwroot\cf_scripts\cfclient\dnfi\ios\plugins\cordova-plugin-device-orientation\www”, and that folder was indeed there (dated with today’s date). And FWIW, I find it on my other CF2016 install that I updated (the one I mentioned above, which was done on both a Windows 10 and Server 2012 R2 machine).

So bottom line, I’m not seeing the errors you guys are, in case anyone may think, “crap, no one can apply the updates. What the heck is wrong!” Indeed, I have applied the updates to 2016 and 2018 on 3 machines with different versions of Windows now.

Finally, FWIW, have you guys (Darren and Leith) checked the log file for the update you applied? It would be in the cfusion\hf-updates\hf-2016-00008-313934 folder within your CF instance (after you had applied that update), and then as a file with a name like Adobe_ColdFusion_2016_Update_8_Install_[date and time of update]. (The hotfix_filelist.log there is NOT the log that tracks success or failure, despite what the updater says.)

And this install log should be there even if you had an error in the update–though again I look forward to hearing the details of the errors you guys got, and indeed whether there was a log for the update.

Finally, if you or anyone else reading along (and having troubles) might trip over many of several common problems that have happened in applying updates, whether to CF10, 11, 2016, or 2016 (not unique to this newest one), I have a blog post with more on the problems and solutions, which may be helpful:

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

Like
(2)
(13)
>
Charlie Arehart
's comment
2019-02-13 14:42:36
2019-02-13 14:42:36
>
Charlie Arehart
's comment

Charlie, thanks for the reply.  Below is all of my details and process, I’ll reference my CF11 install but the same results happened with the CF2016 as well.

  • Windows 2008 R2 with latest SP+MS updates
  • CF11 HF15 & CF2016 HF7 both 64bit
  • Java JRE 1.8.0_201 64bit
  • Manual lockdown guide performed on both CF installs (both done 2+ years ago)
  • Both run under unique local user accounts that have full write permission to the CF folder structure

I downloaded the hotfix jars from the website and placed them in the CF\cfusion\hf-updates folder structure.

  • hotfix_016.jar – 128,282,624 bytes – SHA1: AD37E774C1903C83FD004D1A605058C328FC0652
  • hotfix-008-313934.jar – 174,841,856 bytes – SHA1: CCBE289D01D7BC3A05A47EB319B19F3A99F7D2EA

Logged in as an admin I opened an admin CMD and then ran the java.exe -jar CF\cfusion\hf-updates\hotfix_016.jar using the JRE 1.8.0_201 that my CF is running on.  The installer GUI starts up, I click next, I accept the license, I choose my CF11 folder structure and hit next and I get the error about not having admin privilege.

Pre-Installation Check

No Administrative Privilege

You should have administrative rights to install the Hotfix.  Make sure “Run as administrator” option is used on Windows Vista, Windows 7, Windows Server 2008 and later versions.

I click OK and the installer closes (which actually just shut down CF11 so I had to go start it back up manually afterwards).  There is no hf-11-00016 folder created and no new log files in the hf-updates folder.  Things I tried to resolve this.

  • New CMD as admin
  • Batch file run as admin
  • PowerShell run as admin
  • Gave Everyone account fill access to the CF folder structure
  • Ran using the newly provided by Adobe JDK 1.8.0_202
  • Ran using the old JRE inside of CF11 folder structure
  • Tried with CF11 running and CF11 pre-shutdown
  • Shutdown anti-virus

My process above is how I’ve been updating CF10, CF11, CF2016 for years without issue.  Besides Windows updates & Java updates the system’s configuration has stayed the same since the last time I installed the previous hotfixes for CF11 and CF2016 on this server.

Like
(1)
>
Leith Tussing
's comment
2019-02-13 15:31:30
2019-02-13 15:31:30
>
Leith Tussing
's comment

OK on all that, Leith. And good job spec’ing it all out.

That said, since it keeps complaining about not being run as admin privs, I would focus next on that. I realize have said (clearly) that you ARE running as admin. How about trying one more thing.

Whenever I want to make sure I AM running as admin (regardless of the title bar in the command line indicating it or not), I use this command:

net session

If that comes back with an error, then I am not running as admin. If it comes back with “no entries” or some other message, then I am.

Can you try that, using your environment on which this is happening? And once you confirm it does NOT have an error, could you try the update from the cmd line again? (I realize that if it still fails, then it stops CF which is a pain, but give it a shot when you can.)

Finally, if all that gets you nowhere, you don’t say whether you tried running it in the admin, as Piyush asked in his reply to you. Can you let us know? I get that it may not be your preferred approach, but again if the goal is to get the update applied, it’s worth a shot. We can see if others do indeed report the same problem as you–though again, I did not, with the identical setup.

Like
(2)
>
Charlie Arehart
's comment
2019-02-13 15:31:46
2019-02-13 15:31:46
>
Charlie Arehart
's comment

I’ve additionally tried rebooting the server and also made the local unique user account an admin, same results.

Like
(1)
>
Charlie Arehart
's comment
2019-02-13 15:43:14
2019-02-13 15:43:14
>
Charlie Arehart
's comment

I ran net session in the CMD I had open still and it ran correctly and showed me active sessions.  I then ran the install process again and the same behavior happened.

I did try doing it through the admin last night and it did “install” but errored like every other time I’ve tried to run it from the admin (which is why I don’t).  The system started the process shutdown but as I’ve witnessed in the past using Process Monitor begins installation while the processes are still in memory resulting in a bad install because the files are locked.  The HF15 file couldn’t be moved and was left behind as well as several other jar files.  I had to run the HF16 uninstall to revert to get the server functional again.  I’ve reported this issue in the past but gave up on even trying to do it this way because it has always had a high chance of failure on any of our systems since the process was introduced.

Like
(1)
>
Charlie Arehart
's comment
2019-02-13 16:06:57
2019-02-13 16:06:57
>
Charlie Arehart
's comment

I fixed the issue.

 

The installer is looking if my exact user account I’m logged in with is in the local administrators group.  My account is part of a domain group that is in the administrators group so when it looks in the local administrators group it thinks I’m not an admin of this system.  Adding my specific account to the local administrators group let the installer realize that yes I am an admin and continue.  I was able to successfully complete the CF11 HF16 install.  I will have to wait till after hours to attempt the CF2016 as it is in use by developers.

Like
(2)
>
Charlie Arehart
's comment
2019-02-13 16:21:48
2019-02-13 16:21:48
>
Charlie Arehart
's comment

The missing msvcr71.dll bug from HF15 is still present in this updater.  The installer deleted without backing up the CF\cfusion\db\slserver54\bin\msvcr71.dll from the system which is required for the ColdFusion 11 ODBC Server service to start.  Luckily I always make a full folder backup of the CF before doing an update and copied it back over again.

https://coldfusion.adobe.com/discussion/2534653/

Like
(1)
>
Charlie Arehart
's comment
2019-02-13 17:35:14
2019-02-13 17:35:14
>
Charlie Arehart
's comment

Posted this below, when I went hunting for the install logs here what I found.

<cf_root>/cfusion/hf-updates  does not exist for Update 8, though I can see updates 4 through 7 which I applied before (using same admin account)

In <cf_root>/cfusion/lib/updates only the Update 7 file shows in there, no files for updates 4 through 6 or for 8.

Like
(1)
>
Charlie Arehart
's comment
2019-02-13 17:49:09
2019-02-13 17:49:09
>
Charlie Arehart
's comment

As i’m not getting the updater log file, I ran using java -verbose, the liast line below is the point of failure.

[Loaded sun.reflect.UnsafeObjectFieldAccessorImpl from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded javax.swing.ImageIcon$3 from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.peer.DialogPeer from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded sun.awt.windows.WDialogPeer from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.event.WindowAdapter from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded Flexeraaua$4 from file:/C:/ColdFusion2016/jre1.8.0_192/bin/ColdFusion-hotfix-008-313934.jar]
[Loaded Flexeraaua$5 from file:/C:/ColdFusion2016/jre1.8.0_192/bin/ColdFusion-hotfix-008-313934.jar]
[Loaded Flexeraata from file:/C:/ColdFusion2016/jre1.8.0_192/bin/ColdFusion-hotfix-008-313934.jar]
[Loaded Flexeraatn from file:/C:/ColdFusion2016/jre1.8.0_192/bin/ColdFusion-hotfix-008-313934.jar]
[Loaded sun.awt.util.IdentityLinkedList from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded sun.awt.util.IdentityLinkedList$Entry from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.Dialog$4 from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded sun.awt.util.IdentityLinkedList$ListItr from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.peer.FileDialogPeer from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded sun.awt.windows.WFileDialogPeer from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded sun.awt.windows.WPrintDialogPeer from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.ModalEventFilter$1 from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.ModalEventFilter$ApplicationModalEventFilter from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.Dialog$1 from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded sun.awt.ModalityEvent from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.Dialog$3 from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.SecondaryLoop from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.WaitDispatchSupport from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.WaitDispatchSupport$5 from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.WaitDispatchSupport$1 from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.WaitDispatchSupport$2 from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded java.awt.WaitDispatchSupport$4 from C:\ColdFusion2016\jre1.8.0_192\lib\rt.jar]
[Loaded Flexeraaua$4$1 from file:/C:/ColdFusion2016/jre1.8.0_192/bin/ColdFusion-hotfix-008-313934.jar]

Like
(1)
>
Leith Tussing
's comment
2019-02-13 19:00:01
2019-02-13 19:00:01
>
Leith Tussing
's comment

Leith, that’s awesome. Thanks. (Your pointing out the need for the cf user, running the CF service, to be in the “administrator” group.) You mention not being able to test it. I did, since I saw this finally while working with a client.

We also found that it was not enough to just add the cf user to the admin group. Even with that done, we could not run the CF update from the command line merely running “as admin”. We instead had to open the command line AS THAT CF user. More on that in a moment.

And a question stands as to whether you (and Darren) are tripping over this because of a change in the update mechanism. Perhaps Adobe will report if this is so, later.

All that said, I will repeat that I am on NOT experiencing this on my Server 2008 R2 where I DID successfully update CF2016 and 2018 yesterday. In both cases, the CF services IS running as a user (cfuser), and that user is NOT in the “administrators” group. So here again, there seems something unique about those who WOULD have the problem.

But again I did today finally see the problem, while working with a client. And they got the error, which it may help to elaborate on a bit (for others). No one has clarified it here. It’s a popup WHILE using the command-line updater, and the title is indeed “insufficient permissions”, and then it goes on to report something like (not verbatim), the user account should have read/write privileges to the files in the cf root dir and have privileges to stop and start the service. (If anyone who gets the error could give it to us exactly, it could help someone googling for the error in the future, to find this.)

As for running the command line as that CF user, that can be a challenge depending on the Windows version. You should be able to right-click on the “command line” element in the start menu, and see “run as different user”, but you may not see that. And doing a shift-right-click doesn’t, either.

But I found that (at least on that Server 2008 R2), if instead I had him type cmd in the start menu search, when that found the command line, he COULD use shift-right-click to then see and choose “run as different user”, and then we ran the update from the command line, as that user, and it DID work, without the error.

Some good news is that on Server 2016, you CAN more simply just right-click on the command line option in the start menu, and use “more” and then “run as different user”.

Yes, all that’s a hassle. Again, hopefully we can better find both why SOME would get it and not others, and then why it happens in THIS update and not previous ones. Bes tof all, perhaps Adobe can revise the update to remove that.

Hope that’s helpful.

Like
(2)
>
Charlie Arehart
's comment
2019-02-13 19:43:15
2019-02-13 19:43:15
>
Charlie Arehart
's comment

Not my CF service user, that’s actually a local user account that has no User or Admin permissions.  The issue is my personal account I’m logged into the server with to do administration.  I’m logging in with for example my “lt_admin” account and running the CMD prompt as admin to do work.  My lt_admin account is part of a domain group which that group is part of the local administrators group.  The CF HF updater is looking in the local administrator group for lt_admin and is not finding it and then gives me the No Admin Privs error.  I had to actually add my lt_admin account to the local administrators group even though I’m an admin via the domain group so their updater would acknowledge I’m an admin.

 

Like
(2)
>
Leith Tussing
's comment
2019-02-13 21:44:03
2019-02-13 21:44:03
>
Leith Tussing
's comment

Ok did the following:

Explicit Full Control to my Domain admin on CF Folder.  No Joy.

Explicit change owner to my Domain admin on CF Folder.  Still no Joy.

Added Domain admin account to server Administrators group driectly. This worked and installer functioned.

However the CF Services did not restart, saying that port 8500 already in use. Rebooting server entirely to see if that solves the restarting issue.

 

Like
(1)
>
Darren Gavin
's comment
2019-02-13 21:47:39
2019-02-13 21:47:39
>
Darren Gavin
's comment

This is likely because the CF updater likes to start the main coldfusion.exe as the process you’re running under and not actually start the service.  Whenever I do the manual install I always have to then go kill a coldfusion.exe running under my user process so I can then start the actual service.

Like
(1)
>
Leith Tussing
's comment
2019-02-13 22:10:56
2019-02-13 22:10:56
>
Leith Tussing
's comment

Reboot fix the services restarting, however the ColdFusion Add-On Service is now failing with 1067: The Process Terminated Unexpectedly

Not finding anything in log files or windows events to help on this one.

Like
(1)
2019-02-12 23:48:30
2019-02-12 23:48:30

Seeing the same issue as Leith on CF 2016 Update 8 – Windows 2016 Server.  I went as far taking ownership of the ColdFusion folder on the server itself with admin account and the installer still says insufficient permissions, but does not say on what item that permission issue is happening on.

The updater does shut down the first (primary/enterprise) CF instance on an enterprise build, but not the other instances.

I also tried manually stopping all CF instances after I noticed that, but that error still shows up.

Like
(1)
(4)
>
Darren Gavin
's comment
2019-02-13 09:57:33
2019-02-13 09:57:33
>
Darren Gavin
's comment

Darren,

Where exactly or at what point, do you see the permission related error? Can you share the update installation log at <cf_root>/cfusion/hf-updates. You may send that to me at pnayak@adobe.com

Can you check if the same directory in the non-default instances to see if there are any logs? Do you see the chf2016xx8 jar in the <cf_root>/cfusion/lib/updates dir?

Like
(1)
>
Darren Gavin
's comment
2019-02-13 16:08:57
2019-02-13 16:08:57
>
Darren Gavin
's comment

Darren if you have the same issue I do make sure your admin account you’re logged in with is part of the system’s local administrators group and not a member of a group that is in the administrator’s group.  I had to manually add my logged in account to the group for the installer to realize I’m an admin even though I’m an admin via another group.

Like
(1)
>
PiyushN
's comment
2019-02-13 17:08:23
2019-02-13 17:08:23
>
PiyushN
's comment

<cf_root>/cfusion/hf-updates  does not exist for Update 8, though I can see updates 4 through 7 which I applied before.

In <cf_root>/cfusion/lib/updates only the Update 7 file shows in there.

Like
(1)
>
Darren Gavin
's comment
2019-02-13 18:23:26
2019-02-13 18:23:26
>
Darren Gavin
's comment

Darren,

If I understand you correctly, you have multiple CF instances clustered together.

Now, if you are attempt to install the update from the administrator of the primary CF instance,  you should see a dialog box with check-boxes for all the other instances. If you continue, the updater jar would be downloaded and placed in the <cf_root>/cfusion/hf-updates directory. It would go by the name “hotfix-008-313934.jar”. The CF instances are than stopped and a java process launches to run that jar.

Is the new update jar downloaded? It is not clear from your comment when you see that permission error.  Is it logged somewhere or does it come up in a dialog box soon after you hit the “download and install” button.

Ideally, if you are running the update from the CF admin, then the updater process should launch with the same user account that CF server is using.

You could try running the update jar manually from the windows command prompt. Ref. https://coldfusion.adobe.com/2012/12/coldfusion-hotfix-installation-guide/

You may also contact cfsup@adobe.com for help.

Like
(1)
2019-02-12 23:30:35
2019-02-12 23:30:35

Thanks for the post, Saurav. That said, I have a few concerns.

Why does this say (given that the connector has been updated) that we should “reconfigure the connector”? We should just be able to “upgrade” it, which is a new feature of the wsconfig UI as of CF2016. And note that the release notes page for the update DOES indicate this, as the last sentence in its section on the connector (though the wording above that is confusing there).

Also, speaking of the release notes, there is a real problem there. (And since we can’t add comments there, I am adding it here, for you guys to consider.) See the discussion there about how the update process has a challenge if one has run the CF2018 auto-lockdown tool (and how files permissions need to be corrected after running the update).

Curiously, the CF2018 update 2 release notes page lacks needed detail (that was in the update 1 release note). The update 2 note discussion of that post-update/lockdown tool issue simply ends discussion with “After the installation, there will be a few files with permission-related issues.” That will certainly scare people!

Instead, note that the cf2018 update 1 technote went on to offer commands for both Windows and Linux for how to reset those needed permissions. Someone needs to correct that in the technote for update 2. (This matter does not apply to CF2016 or 11, as they do not have the auto-lockdown tool.)

Finally, one lesser concern with this post is with the link currently offered here to the docs on the new MacOS installer for the autolockdown tool: it has two pound signs in it, where it should be one (in order to take folks properly to that anchor in their browser).

Hope all that’s helpful to readers.

BTW, I had made an earlier comment were in fact I pointed out the release notes URL, among some other things. But because of that link (and another), the post was “moderated” and so is not visible as I write this comment.

Like
(1)
(3)
>
Charlie Arehart
's comment
2019-02-13 03:08:22
2019-02-13 03:08:22
>
Charlie Arehart
's comment

Thank you, Charlie for your comments. I’ll look into these and fix them.

Like
(1)
>
SauravGhosh
's comment
2019-02-19 06:28:26
2019-02-19 06:28:26
>
SauravGhosh
's comment

Saurav, the issues I pointed out here last week remain:

First, the blog post and release notes talk about “reconfiguring” the connector, with no mention of the available “upgrade” feature in the wsconfig tool.

Second, the release notes (https://helpx.adobe.com/coldfusion/kb/coldfusion-2018-update-2.html) still have a truncated discussion of the extra steps needed when applying the update, if you have run the auto-lockdown tool. Again, compare the discussion there to the extra info  in the update 1 release note.

I realize you guys are all busy with the many issues in the update. I am simply trying to help you keep in mind these issues identified last week.

Like
>
Charlie Arehart
's comment
2019-02-19 06:33:10
2019-02-19 06:33:10
>
Charlie Arehart
's comment

Thanks Charlie. I’ll update the blog accordingly.

Like
2019-02-12 22:48:01
2019-02-12 22:48:01

When I try to run both CF11 and CF2016 updates I get an error about not having administrative privilege to install with on WIndows Server 2008 R2.  I’m installing them the same way I always have, run as admin CMD and use java.exe -jar hotfix.jar to run it.  I even tried making a batch file with the command in it and ran that as admin and from an admin PowerShell but all of them fail with the same error about not being run as administrator.  The account I’m logged in as an administrator too.  If I run the previous updater this error does not trigger, only these newer ones.

Like
(1)
(2)
>
Leith Tussing
's comment
2019-02-13 09:49:07
2019-02-13 09:49:07
>
Leith Tussing
's comment

Leith,

Did you try to install the update from the CF administrator? Or is that not an option in your environment?

I gather from your comment that you have not been able to launch the updater process manually from the windows command line, even with elevated privileges. Can you check to see if there are any update logs in <cf_root>/cfusion/hf-updates?  What is the windows user account CF service is using?

You may reach out to our support team at cfsup@adobe.com for help with this.

Like
(1)
>
PiyushN
's comment
2019-02-13 14:14:46
2019-02-13 14:14:46
>
PiyushN
's comment

I will be posting my reply with details to Charlie Arehart’s reply to me above with all my details so it’s just in one place.

Like
(1)
2019-02-12 22:11:21
2019-02-12 22:11:21

When I run the Java 8 installer it appears to want to install both the JRE and JDK – the installer keeps prompting me for an empty directory to install to.

Update Java (v8), install Update 8 and now my application dies with weird errors:

(class: cfprogramtypeServices2ecfc478410578$funcISPROGRAMTYPEAPPROVED, method: runFunction signature: (Lcoldfusion/runtime/LocalScope;Ljava/lang/Object;Lcoldfusion/runtime/CFPage;Lcoldfusion/runtime/ArgumentCollection;)Ljava/lang/Object;) Incompatible object argument for function call

App runs fine if I roll back the update.

Any ideas?

Like
(3)
>
Jim Priest
's comment
2019-02-13 04:58:13
2019-02-13 04:58:13
>
Jim Priest
's comment

Jim, it’s true that the Java 8 installer Adobe offers on their CF downloads page (pointed to here in the technotes) is a JDK installer, and that includes a JRE (optionally, as a choice during the Java installer).

To be clear, it’s exactly the same file one would get if you downloaded it from Oracle directly, as at https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html.

Perhaps your prior experience was to get a JRE only. Those work in most cases, but various discussions over the years have indicated that we should favor a JDK, rather than just the JRE (again, technically, the JDK includes a JRE).

FWIW, there are arguments against letting that JRE (called the “public JRE”) get installed. I’ve discussed that in a post here:

http://www.carehart.org/blog/client/index.cfm/2016/10/5/why_think_twice_about_Java_JDK_installer_public_JRE_option

But it’s not a critical point, and it certainly should have worked for you.

As for why you are finding that CF is not working after having done the CF and Java updates, I would be willing to bet (from the error message you share) that your failure was during the CF update (but it’s not always obvious). As I have shared in other comments here, I have a post that walks through the challenges of finding, dealing with, and recovering from errors in the CF updates:

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

And in case you may have had a problem applying the Java update, I have a post on that also:

http://www.carehart.org/blog/client/index.cfm/2014/12/11/help_I_updated_CFs_JVM_and_it_wont_start

Let us know if any of this helps.

Like
(1)
>
Jim Priest
's comment
2019-02-13 06:47:51
2019-02-13 06:47:51
>
Jim Priest
's comment

Hi Jim,

Can you clear your cfclasses after applying the update and then run your application? If this does not work can you send the entire stacktrace to suchsing@adobe.com.

Thanks,

Suchika

Like
(1)
>
Charlie Arehart
's comment
2019-02-13 15:19:26
2019-02-13 15:19:26
>
Charlie Arehart
's comment

Yeah – the installer was just weird. It never asked me about the second install.

I’ve installed Java probably a few thousand times so am familiar with the process    This was on Windows 10 fwiw.

I install Java to a different directory so that may have something to do with it.  So I run installer – pick that directory – it runs, installs the JDK – then with no prompts it continues running and asks for another directory.  I initially just pointed this to the new directory it just created but it complains that it’s not empty.  I have to then create a bogus empty directory where it installs the JRE.

It never says “Install JRE? Yes/No”

Like
(1)
2019-02-12 21:53:38
2019-02-12 21:53:38

Thanks for the post, Saurav. I see a few things that others may want to note.

First, Kama makes a good point. Is that an oversight (that this lists new platforms only for CF2018, and not CF2016)?

Also, why is there no mention of this platform difference in the technote for the CF2018 update (which you point to above), nor even in the release note for it (https://helpx.adobe.com/coldfusion/release-note/coldfusion-2016-updates-release-notes.html).

Indeed, it would seem helpful to have a link here to that release note, since it includes some real examples of the new cflooop script statement, and more. (It’s not there as I write this comment. Perhaps it will be added later.)

Finally, the post here does not mention the updates to the CF docker containers, which were also updated today (for CF2018 and 2016):

https://bintray.com/eaps/coldfusion/cf%3Acoldfusion#read

Hope that helps some readers.

Like
(2)
(5)
>
Charlie Arehart
's comment
2019-02-13 09:04:19
2019-02-13 09:04:19
>
Charlie Arehart
's comment

Thanks Charlie for the inputs. We’ll update the release notes.

Like
(1)
>
SauravGhosh
's comment
2019-02-13 09:34:23
2019-02-13 09:34:23
>
SauravGhosh
's comment

Charlie, for the 2016 version, we only have support for MS Exchange 2016.

Like
(1)
>
SauravGhosh
's comment
2019-02-14 14:13:19
2019-02-14 14:13:19
>
SauravGhosh
's comment

To add: Solaris 11.3 also is supported in 2016 since Java 11 mandates the version of Solaris to be 11.3 or higher. As and when we certify other platforms such as Win Server 2019 and Mac OS X 10.14, we will update the support matrix for 2016.

Like
(1)
>
SauravGhosh
's comment
2019-02-19 06:20:46
2019-02-19 06:20:46
>
SauravGhosh
's comment

Saurav, the blog post (and release notes for 2018 or 2016) still make no mention of the Docker container update, which may benefit some readers to know.

And the blog post still doesn’t point to the CF2018 release notes page, that has useful code demos. I mistakenly pointed to the URL for the 2016 one above, but I meant this link that should be added:

https://helpx.adobe.com/coldfusion/release-note/coldfusion-2018-updates-release-notes.html

Like
>
Charlie Arehart
's comment
2019-02-19 06:25:52
2019-02-19 06:25:52
>
Charlie Arehart
's comment

Charlie- Thanks for this. I’ve updated the blog. As far as Docker is concerned, I’ll update it once we also have Performance Monitoring Toolset container is up. I hope to update the blog with info about Docker by end of day.

Like
2019-02-12 20:46:01
2019-02-12 20:46:01

[Subscribed]

Like
(2)
>
Chris Reese
's comment
2019-02-13 09:54:13
2019-02-13 09:54:13
>
Chris Reese
's comment

Chris, you can set options in Settings to receive notifications. Please see https://elearning.adobe.com/2019/01/whats-new-changed-latest-community-portal-update/

Like
(1)
>
SauravGhosh
's comment
2019-02-14 01:10:10
2019-02-14 01:10:10
>
SauravGhosh
's comment

SauravGhosh, same as with Miguel Fernandez’s comment.

Like
2019-02-12 18:05:51
2019-02-12 18:05:51

[subscribe]

Like
(2)
>
Miguel Fernandez
's comment
2019-02-13 09:54:36
2019-02-13 09:54:36
>
Miguel Fernandez
's comment

Miguel,you can set options in Settings to receive notifications. Please see https://elearning.adobe.com/2019/01/whats-new-changed-latest-community-portal-update/

Like
(1)
>
SauravGhosh
's comment
2019-02-14 01:09:14
2019-02-14 01:09:14
>
SauravGhosh
's comment

SauravGhosh,

I believe Miguel made this comment to be able to receive notifications when further comments are made to this blog post.

I am not aware of any other method that allows a user to subscribe to notifications about comments on a post. The only relevant entry in the Settings that I can see is this one:

“Notify me when users comment on a post that I have previously commented upon”

which implies that you have to first make a comment yourself, before you start receiving notifications about other comments.

Am I missing something?

Like
(1)
2019-02-12 17:27:50
2019-02-12 17:27:50

I see that new platforms were added to CF 2018, but not CF 2016. Is it normal to only add new platforms to the latest release? CF 2016 still has a couple years of support left.

Like
(3)
(1)
>
Kama Sama
's comment
2019-02-13 03:09:09
2019-02-13 03:09:09
>
Kama Sama
's comment

We will add more to CF 2016 in the coming updates.

Like
(1)
2019-02-12 16:25:13
2019-02-12 16:25:13

CF2018 U2 gives me an error running on Oracle JDK 11.0.2 when I try to access a cfreport.
Using JDK 10 from CFroot works fine.

Report data binding error Error initializing graphic environment..
class sun.font.CompositeFont cannot be cast to class sun.font.PhysicalFont (sun.font.CompositeFont and sun.font.PhysicalFont are in module java.desktop of loader ‘bootstrap’)

Like
(1)
(2)
>
joergz83561623
's comment
2019-02-14 10:10:01
2019-02-14 10:10:01
>
joergz83561623
's comment

joergz83561623,

we have not been able to reproduce the issue with a simple cfreport workflow. Can you share your OS details (or any other relevant environment details) and a test case with which you can observe the error.

This could be because of a corrupt font in the system as well.. Ref. https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8144703

You may send the files to me at pnayak@adobe.com.

Like
(1)
>
joergz83561623
's comment
2019-02-19 05:37:28
2019-02-19 05:37:28
>
joergz83561623
's comment

joergz83561623, did you ever end up resolving your issue?

Piyush pointed out it could be a font issue. There is more about this in the  known issues documents, such as that for your version, CF2018:

https://helpx.adobe.com/coldfusion/kb/bugs-fixed-coldfusion-2018-update-2.html#knownissues

Note that it refers to the same error you got:
class sun.font.CompositeFont cannot be cast to class sun.font.PhysicalFont

And while it refers to the impact on this for cfdocument, it makes sense that it could apply also to cfreport (and Adobe, you may want to update the known issues docs to reflect that, and other tags that could be affected by that).

Like
Add your comment