GAinsworth,

- 4GMT is 4 hours less than Greenwich Meridian Time which is considered 0 hours. I am in the same time zone as Miami (or a difference of one hour tops).

It was no hidden meaning, I was going to ask you to document my step by step instructions and post them here repeatedly for a little while. It was no punishment though, just a pay forward request.

It appears to me that you have gotten confused with the directory permissions and SQL permissions. The information in web.config is used to connect to a Database as if it were a user. In this case the username and password need to match a SQL account. By using windows authorization you need to match the APSNET in SQL and the information in web.config as a trusted connection. ASPNET in SQL needs at a minimum db_datareader, db_datawriter, db_ddladmin, db_securityadmin. This is detailed in the Installation Guide.

File permissions are required for the aspnet worker process user (aspnet in win2000 and winxp, and network service in win2003) to create files in the DNN directory. Unless the permissions for a directory when copied from one machine to another are propagated, the preparation you mention addin network service might be useless. I say this because a directory and items usually inherit from the new parent directory in the destination machine and those can be different than those at the original source directory. In any case just give modify permissions to the aspnet user from the machine where DNN is running (repeat for deployment).

The only changes in web.config  needed for a new standard install are those related to the connectionstring. The rest should be changed only for customized installations and those can vary.

I suspect this new error is from me modifying machine.config to:

<system.web>

<processModel username="ASPNET" password="aspNET_XP"/>

But that was what the event log showed as the file with the invalid ASPNET name/password. 

I really do appreciate the time and information you have provided.  Let me get a few more of my non-DNN issues resolved. 

It's just a pity that 10-15% of the mega-manhours used to reply, re-reply, re-re-reply can not be diverted to creating Installation Guide's for each release, clarification of existing guide information, and creatiing of guide appendicies for IIS, SQL, ASPNET, VB, etc.  with the most common issues addressed.

Everyone would benefit greatly.