We updated Coldfusion 2018 from Update 11 to 12 on windows servers and began having permissions issues when trying to read from or write to folders on file servers. ColdFusion can do this for folders on the ColdFusion server but if it is a file server (aka not on the same server), it has issues. Prior to the upgrade the we could perform folder and file related access activities without issue.
We tested this issue with a script which looped over a list of folder paths and performed:
We verified that the ColdFusion service account had read and write permissions to all of the folders involved and were even able to use a non-upgraded ColdFusion instance to write to the destination folder with the account.
We tested with the following types of folders:
The only folder where the actions worked properly were the folders on the same server as the ColdFusion isntance. For all of the other folders:
Once we uninstalled update 12, we performed the same set of tests on the same set of folders (without changing any permissions on the folders) and the script successfully perform all actions on all folders. The issue seems to be related to the update 12.
We are curious if others have encountered similar issues.
Yes, that seems strange. Especially as Update 11 succeeds, but Update 12 fails.
How do you define the paths to the directories and files on the file server? Using the Universal Naming Convention (UNC)? Have a look at the last answer (by Gabriel) to this Stackoverflow UNC question: https://stackoverflow.com/questions/23939271/coldfusion-file-access-using-unc-path-access-denied .
Were there any related error messages in the logs? Please share some examples of your code.
Oh, something to rule out. Is Update 11 running as a domain user, whereas Update 12 ran as Local-System? If so, then that would explain the problem - and the solution.