Last post May 04, 2005 04:22 PM by cathal
May 02, 2005 06:54 PM|gjcm|LINK
May 03, 2005 01:39 PM|thedigitalnomad.com|LINK
At which level did they apply the modify perm?
In the /documentation/public/dotnetnuke installation guide.doc is this...
Perhaps cut and paste this and include in your next email???
May 03, 2005 08:03 PM|gjcm|LINK
May 03, 2005 10:39 PM|brian_c|LINK
The best is for a host to clone (so to speak) the NetworkService account and grant that the access ...
Although one host that does this .. it seems both need permissions at times.. somehow one does 99% but the other still does some log writing .. it must be something within DNN .. not sure ...
May 04, 2005 04:22 PM|cathal|LINK
The problem is a missing permission. From the faq:
Q. What permissions are required for DNN to function properly ?
A. The ASPNET account (which is the account used for running the asp.net worker process) must have READ, WRITE and MODIFY permissions on the WEBROOT and all subfolders for the DNN application. There are several conditions where the application writes files
both to the root (e.g. child portal folders) as well as to subfolders (e.g. uploading portal files).
** Important note ** the ASPNET process must also have READ ATTRIBUTE privileges (not read file) on the DRIVE ROOT (e.g. D:\) for the DirectoryInfo class in .NET to work correctly.
NOTE: This is a standard permission granted to the C: drive that your host must replicate if they use alternative drives to host web content.