Copy link to clipboard
Copied
We installed HF 20 on our CF 2021 instance (from HF 19) and saw "Security violation: Scheduled task 'XXX' attempted to execute unauthorized path: F:/Tasks_Logs/xxx.log. To allow it, whitelist the path in cf-root/lib/pathfilter.json against key schedulerexecutionpaths." in the scheduler.log (and consequently the task did not run (actually found the task to be deleted). Anway, based on the release notes, we updated pathfilter.json as such:
"schedulerexecutionpaths": "F:/Tasks_Logs/**."
Restarted CF and then broke our SAML/SSO login altogether to the site, so the site was hard down. Backed out change to pathfilter.json and restarted CF, still hared down. Backed out HF 20, back to HF 19 and restarted, all good (sans deleted scheduled tasks).
Error when hard down, on our consume page (SAML response) looked like:
coldfusion-out.log shows:
Copy link to clipboard
Copied
You followed the right steps. About the cause of the problem, my bet is on one of two things: either (1) ColdFusion hates the fact that your file path ends with a dot or (2) you forgot to restart ColdFusion afterwards.
So, to recap, the steps I suggest are:
"schedulerexecutionpaths": "F:/Tasks_Logs/**"
or
"schedulerexecutionpaths": "F:/Tasks_Logs/xxxx.log"
Copy link to clipboard
Copied
Thanks BKBK! The dot is a typo, shoudl have been a semicolon (because that was in the technote). I did want to note, even thogu we saw those erros in the log, we do nto actually have Publish selected on the the tasks in question (or any for that matter).
Copy link to clipboard
Copied
Thanks for the new information.
Install Update 20 and follow the steps I suggested. I hope there won't be any errors.
Upgrading to Update 20 is the main goal.
Copy link to clipboard
Copied
I think and will look more, but Microsoft June updates, KB5060531, are somehow at play. We have a dev box that has HF 20 fine, sans scheduled tasks working, but our Sys Admin installed the aforementioned Windows update and broke the consume.cfm (login page) above. Now when we did this in production on June 13, the Windows updates were pending and got installed then. Of course I could just be candidate for a Jump to Conclusion mat.
Copy link to clipboard
Copied
Thanks for sharing the information about Microsoft June updates, KB5060531. That aside, I am glad to inform you of the following:
The scheduled task worked as expected, and there were no errors.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now