A User can no longer write report to a Shared Directory
Hint Ref: 021103180002
Hint Date: 18/03/2011
A customer reported that an XML job they ran, which wrote a report to a PDF and stored it in a shared directory, no longer ran - instead reporting a 'Cannot Create File' error.
On checking the directory in question, the group EVERYONE was found to have Full Control and the user had made no changes to any other permissions.
The user was not trying to write the PDF directly to the shared directory, but instead to a subdirectory of the share.
The cause of the issue was found to be that the PC had automatically performed a Microsoft Update and that this Update had changed the rules concerning the access of subdirectories of a shared directory.
The solution was to give the SHARED directory Write Permissions which in turn allowed the user to write to the subdirectory as well.
NOTE: It should be noted that it may be undesirable to give WRITE rights to users to the main share and, in cases such as this, a new share will need to be created, sharing the subdirectory directly.
(Please Note: This Procedure can be destructive and should only be used by Advanced Users. RADical Systems (UK) Limited or its Partners cannot be held responsible, in anyway, for any consequence of using this or any other Database Function, Procedure or SQL command. Responsibility resides solely with the user.
IT IS HIGHLY RECOMMENDED THAT A FULL AND VALID SPACE MANAGER DATABASE BACKUP IS TAKEN AND VERIFIED AS VALID BEFORE MAKING ANY CHANGES TO THE DATABASE.)