portal entry

select a category, or use search below
(searches all categories and all time range)

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

| View in Portal
February 12, 2019 03:29:31 PM GMT
<p>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: ColdFusion (2018 release) Update […]</p>
<p>The post <a rel="nofollow" href="https://coldfusion.adobe.com/2019/02/coldfusion-2018-release-update-2-coldfusion-2016-release-update-8-coldfusion-11-update-16-released/">ColdFusion (2018 release) Update 2, ColdFusion (2016 release) Update 8, and ColdFusion 11 Update 16 released</a> appeared first on <a rel="nofollow" href="https://coldfusion.adobe.com">ColdFusion</a>.</p>
Labels: Adobe ColdFusion 11, Adobe ColdFusion 2016, Adobe ColdFusion 2018, CFFiddle, ColdFusion Builder, new features, Performance Monitoring Toolset, ColdFusion (2016 release) Update 8, ColdFusion (2018 release) Update 2, ColdFusion 11 Update 16, ColdFusion 11 updates, ColdFusion 2016 updates, ColdFusion 2018 updates, coldfusion builder updates, ColdFusion security updates, ColdFusion updates, Performance Monitoring Toolset updates, Server Auto-Lockdown updates


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.
Comment by Piyush Nayak
1762 | February 13, 2019 06:23:26 PM GMT
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!!
Comment by gstboces1
1761 | February 13, 2019 06:44:28 PM GMT
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.
Comment by Charlie Arehart
1759 | February 13, 2019 07:00:01 PM GMT
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: <strong>Problem 1 – Coldfusion Admin Update page blew up</strong> 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:/(<strong>redacted</strong>)/cfusion/wwwroot/CFIDE/administrator/updates/_settings.cfm: line 345 Called from C:/(<strong>redacted</strong>)/cfusion/wwwroot/CFIDE/administrator/updates/_settings.cfm: line 135 Called from C:/(<strong>redacted</strong>)/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   <strong>Problem 2 – Installation was unable to create/copy files</strong> 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:\(<strong>redacted</strong>)\cfusion\lib\updates\chf20160007.jar to the backup location C:\ (<strong>redacted</strong>)\cfusion\hf-updates\hf-2016-00008-313934\backup\lib\updates\chf20160007.jar   <strong>Problem 3 – Services are gone</strong> 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.    
Comment by Vincent Krist
1758 | February 13, 2019 07:00:24 PM GMT
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.
Comment by Leith Tussing
1757 | February 13, 2019 07:10:55 PM GMT
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.  
Comment by Leith Tussing
1754 | February 13, 2019 07:43:15 PM GMT
Manually recreating your schedule tasks in cfadmin, it worked for me.
Comment by Chris Reese
1752 | February 13, 2019 09:12:12 PM GMT
Ok did the following: Explicit Full Control to my Domain admin on CF Folder.  No Joy. <span>Explicit </span>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.  
Comment by Darren Gavin
1751 | February 13, 2019 09:44:03 PM GMT
<p>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.</p>
Comment by Leith Tussing
1750 | February 13, 2019 09:47:39 PM GMT
<p>Reboot fix the services restarting, however the ColdFusion Add-On Service is now failing with 1067: The Process Terminated Unexpectedly</p><p>Not finding anything in log files or windows events to help on this one.</p>
Comment by Darren Gavin
1749 | February 13, 2019 10:10:56 PM GMT
Thanks! The manual installation process from the command prompt worked for me.
Comment by Vincent Krist
1748 | February 13, 2019 10:27:03 PM GMT
Great news on the Windows Server 2019 support for CF2018. When will the <a href="https://helpx.adobe.com/pdf/coldfusion2018-support-matrix.pdf" rel="nofollow">support matrix</a> be updated to match?
1747 | February 13, 2019 11:43:13 PM GMT
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 <span>Additional Third Party Installers<span> there is a Terms of Use entry with two links:</span></span> <a href="https://www.adobe.com/legal/licenses-terms.html" rel="nofollow">https://www.adobe.com/legal/licenses-terms.html</a>, which is just the general licence terms for various Adobe products. <a href="http://www.adobe.com/go/thirdparty" rel="nofollow">http://www.adobe.com/go/thirdparty</a>, 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).  
Comment by Legorol San
1746 | February 14, 2019 01:02:58 AM GMT
Will there be an update for ColdFusion Builder 2016 too?
Comment by Legorol San
1745 | February 14, 2019 01:03:54 AM GMT
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?
Comment by Legorol San
1744 | February 14, 2019 01:09:14 AM GMT
SauravGhosh, same as with Miguel Fernandez's comment.
Comment by Legorol San
1743 | February 14, 2019 01:10:10 AM GMT
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>
Comment by Leith Tussing
1742 | February 14, 2019 01:20:42 AM GMT
We'll update it shortly.
Comment by SauravGhosh
1741 | February 14, 2019 06:54:28 AM GMT
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    
Comment by Suchika Singh
1740 | February 14, 2019 09:15:25 AM GMT
<p>joergz83561623,</p><p>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.</p><p>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</p><p>You may send the files to me at <a href="mailto:pnayak@adobe.com" rel="nofollow">pnayak@adobe.com</a>.</p>
Comment by Piyush Nayak
1739 | February 14, 2019 10:10:01 AM GMT
No plan for the same as of now.
1737 | February 14, 2019 01:43:03 PM GMT
<p>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.</p>
Comment by Leith Tussing
1736 | February 14, 2019 01:48:43 PM GMT
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.
1734 | February 14, 2019 02:13:19 PM GMT
Great find Leith, was able to resurrect all tasks. Thanks for your help
Comment by Chris Reese
1733 | February 14, 2019 02:45:43 PM GMT
Issues with workarounds to problems I've experienced with these updates on CF11 and CF2016 in one post instead of all over the place. <strong>Issue 1 - No Administrative Privilege during manual installation (CF11 & CF2016)</strong> <strong>Cause</strong> - 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. <strong>Workaround</strong> - Add your logged in account to the local administrators group.   <strong>Issue 2 - ColdFusion 11 ODBC Server service fails to start (CF11)</strong> <strong>Cause</strong> - 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. <strong>Workaround</strong> - Backup the file before installing and then restore after updating.  You can grab the file from another installation or previous backup.   <strong>Issue 3 - Scheduled Tasks are gone (CF11 & CF2016)</strong> <strong>Cause</strong> - 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. <strong>Workaround</strong> - 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.
Comment by Leith Tussing
1732 | February 14, 2019 02:48:43 PM GMT
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?
Comment by Legorol San
1729 | February 14, 2019 04:46:12 PM GMT
I created a bug report for Issue 3:<a href="https://tracker.adobe.com/#/view/CF-4204021" rel="nofollow">https://tracker.adobe.com/#/view/CF-4204021</a> Lots of people are reporting this: <a href="https://forums.adobe.com/thread/2595082" rel="nofollow">https://forums.adobe.com/thread/2595082</a> FYI Adobe is apparently aware of this issue.
Comment by Peter Freitag
1728 | February 14, 2019 04:46:18 PM GMT
We have noticed the same loss of all scheduled tasks after the CF2016 update 8 on RHEL 7.
Comment by jbrock777
1727 | February 14, 2019 06:26:11 PM GMT
<a href="https://coldfusion.adobe.com/profile/Legorol" target="_blank" rel="noopener">Legorol</a> Take a look at this blog post clarifying the usage of Java: <a href="https://coldfusion.adobe.com/2019/01/oracle-java-support-adobe-coldfusion/">https://coldfusion.adobe.com/2019/01/oracle-java-support-adobe-coldfusion/</a>  
Comment by Rakshith Naresh
1725 | February 15, 2019 03:58:16 AM GMT
@Legoral - We can evaluate porting back some critical bug fixes to CFB 2016.
1724 | February 15, 2019 04:04:42 AM GMT
<p>Joshua,</p><p>We’ve updated the matrix.</p><p><a href="https://helpx.adobe.com/pdf/coldfusion2018-support-matrix.pdf" rel="nofollow">https://helpx.adobe.com/pdf/coldfusion2018-support-matrix.pdf</a></p>
Comment by SauravGhosh
1722 | February 15, 2019 07:10:30 AM GMT
Very, very helpful. Thanks, Leith (and Pete).
Comment by Charlie Arehart
1720 | February 15, 2019 12:53:07 PM GMT
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.
Comment by Jim Priest
1716 | February 15, 2019 05:59:23 PM GMT
Could you please elaborate on this known issue: <blockquote> <strong>Issue #2</strong> An exception occurs when returning the result of queryExecute from a function in a CFC </blockquote> This sounds like a complete showstopper for a lot of my applications!
Comment by Hemi345
1715 | February 15, 2019 06:24:57 PM GMT
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.
Comment by Vincent Krist
1714 | February 15, 2019 06:25:24 PM GMT
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.
Comment by Leith Tussing
1713 | February 15, 2019 07:18:18 PM GMT
<p>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.</p><p> </p><p>CF/cfusion/db/slserver54/bin/MSVCR100.dll</p><p> </p><p>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.</p>
Comment by Leith Tussing
1712 | February 15, 2019 07:34:55 PM GMT
<strong>Scheduled Tasks are gone (CF11 & CF2016) </strong>Wow! do you not test these things, before release? Is this "Abode" a new startup software company with a completely incompetent staff
Comment by gtbsf81
1709 | February 16, 2019 02:06:10 AM GMT
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.
Comment by Charlie Arehart
1707 | February 16, 2019 05:02:21 AM GMT
<p>Charlie, actually this page, linked from the blog post, has mentioned the installer refresh right from the start: <a href="https://helpx.adobe.com/coldfusion/kb/coldfusion-2018-updates.html" rel="nofollow">https://helpx.adobe.com/coldfusion/kb/coldfusion-2018-updates.html</a></p><p>It is true that it’s not mentioned in the blog post itself, nor are there details about the refresh as you point out.</p>
Comment by Legorol San
1706 | February 16, 2019 11:56:22 AM GMT
<p>I have read that blog post multiple times, i even asked a question in the comments about this, which you responded to.</p><p>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.</p><p>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.</p><p>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.</p>
Comment by Legorol San
1705 | February 16, 2019 12:05:09 PM GMT
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.
Comment by Charlie Arehart
1700 | February 16, 2019 03:25:30 PM GMT
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: <ul> <li>The update may fail if the windows user running cf is not specifically listed in the administrors group</li> <li>Those using the cf odbc services will find those don't start unless the manually copy in the needed mscvr dll</li> </ul> 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.)
Comment by Charlie Arehart
1699 | February 16, 2019 03:33:08 PM GMT
Thank you Charlie. We shall update the blog when we have more information regarding the issues.
Comment by SauravGhosh
1698 | February 16, 2019 04:16:33 PM GMT
@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.
1692 | February 18, 2019 01:22:21 PM GMT
<p>The below bug report has the details:</p><p><a href="https://tracker.adobe.com/#/view/CF-4204027" rel="nofollow">https://tracker.adobe.com/#/view/CF-420402</a></p><p>Also, what version of ColdFusion are you on?</p>
1691 | February 18, 2019 01:39:17 PM GMT
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?
Comment by Charlie Arehart
1690 | February 18, 2019 02:02:05 PM GMT
Comment by Dave Cordes
1688 | February 18, 2019 05:33:33 PM GMT
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).
Comment by Charlie Arehart
1687 | February 18, 2019 07:00:43 PM GMT
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).
Comment by Charlie Arehart
1684 | February 19, 2019 05:37:28 AM GMT
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
Comment by Charlie Arehart
1683 | February 19, 2019 06:20:46 AM GMT
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.
Comment by SauravGhosh
1682 | February 19, 2019 06:25:52 AM GMT
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 (<a href="https://helpx.adobe.com/coldfusion/kb/coldfusion-2018-update-2.html" rel="nofollow">https://helpx.adobe.com/coldfusion/kb/coldfusion-2018-update-2.html</a>) 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.
Comment by Charlie Arehart
1681 | February 19, 2019 06:28:26 AM GMT
Thanks Charlie. I'll update the blog accordingly.
Comment by SauravGhosh
1680 | February 19, 2019 06:33:10 AM GMT
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 <a href="mailto:suchsing@adobe.com?" rel="nofollow">suchsing@adobe.com?</a> Thanks & Regards, Suchika
Comment by Suchika Singh
1679 | February 19, 2019 07:43:50 AM GMT
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.
1678 | February 19, 2019 10:00:55 AM GMT
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
Comment by Suchika Singh
1677 | February 19, 2019 12:38:39 PM GMT
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
Comment by Leith Tussing
1676 | February 19, 2019 01:40:04 PM GMT
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?
Comment by Charlie Arehart
1675 | February 19, 2019 02:22:37 PM GMT
<p>Thanks. So two points:</p><p>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.)</p><p>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.</p><p>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.</p><p>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.</p><p>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.</p><p>(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.)</p><p>Complicating? Perhaps. But it’s due to your having had multiple generations of installers for a given release.</p>
Comment by Charlie Arehart
1674 | February 19, 2019 02:53:48 PM GMT
Comment by Hemi345
1669 | February 20, 2019 06:34:20 PM GMT
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?
Comment by rcasdorph
1668 | February 20, 2019 07:10:15 PM GMT
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?
Comment by Benjamin Reid
1667 | February 21, 2019 01:21:35 AM GMT
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?
Comment by Charlie Arehart
1666 | February 21, 2019 05:31:39 AM GMT
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?
Comment by Charlie Arehart
1665 | February 21, 2019 05:34:41 AM GMT
<p>The current java version is 8_201 – Java HotSpot(TM) 64-Bit Server VM.</p><p>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)</p><p>I selected the version in the administrator so I assume it will correctly enter the path. </p><p>This fails: java.home=C:/Program Files/Java/jdk-11.0.2</p><p>This works: java.home=C:/Program Files/Java/jre1.8.0_201</p><p>Anything else to try?</p>
Comment by rcasdorph
1766 | February 21, 2019 03:12:53 PM GMT
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.
Comment by Charlie Arehart
1767 | February 21, 2019 03:34:14 PM GMT
<p>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. </p>
Comment by rcasdorph
1768 | February 21, 2019 03:44:13 PM GMT
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? <ul> <li>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?</li> <li>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.)</li> <li>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.</li> </ul> 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: <a href="http://www.carehart.org/blog/client/index.cfm/2014/12/11/help_I_updated_CFs_JVM_and_it_wont_start" rel="nofollow">http://www.carehart.org/blog/client/index.cfm/2014/12/11/help_I_updated_CFs_JVM_and_it_wont_start</a> Sure, that's from before Java 11 (or 10 or 9), but the concepts, techniques, mistakes, and solutions do still apply. Hope that helps.
Comment by Charlie Arehart
1769 | February 21, 2019 04:12:16 PM GMT
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: <span>The following information is meant for the website developer for debugging purposes.</span> <span>Error Occurred While Processing Request</span> 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. <h1></h1> The error occurred in scheduletasks.cfm: line 201 -1 : Unable to display error's location in a CFML template.
Comment by Peter Tilbrook
1774 | February 21, 2019 09:29:25 PM GMT
The backup folder for all CF2016 updates appear to NOT nake a backup of the neo-cron.xml file...
Comment by Peter Tilbrook
1775 | February 21, 2019 10:25:01 PM GMT
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 (<a href="https://tracker.adobe.com/#/view/CF-4204021?1" rel="nofollow">https://tracker.adobe.com/#/view/CF-4204021?1</a>), 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: <blockquote>"<em>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??"</em> <em>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.)</em> <em>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.)</em> <em>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).</em>"</blockquote> 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 <a href="https://tracker.adobe.com/#/view/CF-4200009," rel="nofollow">https://tracker.adobe.com/#/view/CF-4200009,</a> and then go view and vote on that as well.
Comment by Charlie Arehart
1791 | February 21, 2019 10:35:01 PM GMT
<p>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.</p><p>Check out:</p><p><a href="https://coldfusion.adobe.com/2019/02/adobe-please-change-portal-working-posts-dozens-comments-5-proposed-enhancements/">https://coldfusion.adobe.com/2019/02/adobe-please-change-portal-working-posts-dozens-comments-5-proposed-enhancements/</a></p><p>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.)</p><p>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!)</p><p>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.</p>
Comment by Charlie Arehart
1776 | February 21, 2019 10:43:27 PM GMT
<p>Peter, the solution is discussed in other comments here, and on the bug ticket:</p><p><a href="https://tracker.adobe.com/#/view/CF-4204021?1" rel="nofollow">https://tracker.adobe.com/#/view/CF-4204021?1</a></p><p>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.</p>
Comment by Charlie Arehart
1778 | February 22, 2019 01:21:39 AM GMT
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: <blockquote>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??"</blockquote> And then I share my answer to that, if it may be of help for you.
Comment by Charlie Arehart
1779 | February 22, 2019 04:07:05 AM GMT
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
Comment by Suchika Singh
1780 | February 22, 2019 12:12:05 PM GMT
<p>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: <a href="https://coldfusion.adobe.com/2019/02/coldfusion-2016-release-update-9-coldfusion-11-update-17-released/">https://coldfusion.adobe.com/2019/02/coldfusion-2016-release-update-9-coldfusion-11-update-17-released/</a></p>
Comment by Charlie Arehart
1785 | February 22, 2019 02:10:27 PM GMT
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.
Comment by Leith Tussing
1787 | February 22, 2019 04:08:49 PM GMT
<p>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”).</p><p>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.</p><p>So Ben, I hope you will let us know whether you had errors or not, as it would influence next steps and further comment.</p>
Comment by Charlie Arehart
1790 | February 22, 2019 04:38:32 PM GMT
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.
Comment by Benjamin Reid
1807 | February 27, 2019 02:02:37 AM GMT
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?
Comment by Benjamin Reid
1806 | February 27, 2019 02:07:57 AM GMT
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.  
Comment by rcasdorph
1815 | February 28, 2019 09:53:01 PM GMT
Has there ever been a clarification on this point, which Legorol and others have raised?
Comment by Charlie Arehart
1845 | March 04, 2019 05:40:20 PM GMT
Actually I found the CF2016 had Update 10 available not Update 9 - but it didn't fark up scheduled tasks...
Comment by Peter Tilbrook
1863 | March 05, 2019 08:43:34 PM GMT
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.
Comment by Benjamin Reid
1864 | March 05, 2019 11:29:30 PM GMT
[editing the comment ate all the formatting, so I reposted it]
Comment by Legorol San
1905 | March 09, 2019 02:42:39 PM GMT
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: <a href="https://www.adobe.com/support/coldfusion/downloads.html" rel="nofollow">https://www.adobe.com/support/coldfusion/downloads.html</a> 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.
Comment by Legorol San
1907 | March 09, 2019 02:50:19 PM GMT
Where can we download an offline installation package for the ColdFusion Builder 2018 Update 1? The update release notes at <a href="https://helpx.adobe.com/coldfusion/kb/coldfusion-builder-2018-update-1.html" rel="nofollow">https://helpx.adobe.com/coldfusion/kb/coldfusion-builder-2018-update-1.html</a> 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
Comment by Legorol San
1908 | March 09, 2019 03:04:06 PM GMT
ColdFusion Builder 2018 installer also seems to have been refreshed.
Comment by Legorol San
1909 | March 09, 2019 05:35:58 PM GMT
Bug: DataSource SSL Encryption broken with CF2016 Update 8/9/10 and CF2018 Update 3 https://tracker.adobe.com/#/view/CF-4204087
Comment by Benjamin Reid
1913 | March 12, 2019 07:44:01 AM GMT