My hosting company is upgrading and moving from win2k web server to win2003 web server (the sql server remains the same win2k).
We immediately got errors saying:
DotNetNuke Configuration Error
Could not find a part of the path "D:\".
and then the standard message about configuring permissions properly. The root of the web and all subdirectories _
do_ have read/write/modify [ie delete/create] enabled.
Amongst others I found this posting:
Q. What permissions are required for DNN to
function properly under W2K?
A. The ASPNET account (which is the account used
for running the asp.net worker process) must have FULL 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 ** Under W2K
only, 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.
>>> If you're on W2K, make
sure your administrator understands your asking for READ ATTRIBUTE privileges...
not read file (which would be a security issue).
However, this didn't seem to make a difference either unless my webhost didn't understand my garbled explanation.
Does anyone know if the "Read Attribute" privileges are still required for the ASPNET (or NetworkService) account for the root of the server (ie D:\)?
Or any other suggestions?