displaying top 100 results
Comment on Nest CFOUTPUT error in hotfix 5 (hf-2018-00005-315699) by Leith T.
Comment on Nest CFOUTPUT error in hotfix 5 (hf-2018-00005-315699) by Leith T.
Comment on Nest CFOUTPUT error in hotfix 5 (hf-2018-00005-315699) by Leith T.
Comment on Nest CFOUTPUT error in hotfix 5 (hf-2018-00005-315699) by Leith T.
Comment on Nest CFOUTPUT error in hotfix 5 (hf-2018-00005-315699) by Leith T.
Leith Tussing 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.
Leith Tussing 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
Comment on ColdFusion (2018 release) Update 2, ColdFusion (2016 release) Update 8, and ColdFusion 11 Update 16 released by Leith Tussing
Charlie Arehart
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
reading above, Dakota, Shirzad, and Leith, to name a few.
So Nimit, are you saying that you have heard from them and their issues are resolved? Or that their issues are so different as to be a different bug? Or is it that they have not replied to you all directly with more detail?
I just want to hear
Charlie Arehart 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