Hmmm numerour errors and spent the day trying to fixc.

Here are the background steps

Installing on VPS Server, Sql Express, IIS 6.0 

Detached the SQL Express database

Deleted the SQL Express database From the SQL management configuration.

Deleted the WEB Site configuration from IIS

C:\websites\xxx is the webroot folder ,

Delete the c:\websites\fantasyquest folder.

Unzipped the Install version of 4.4.1 to c:\websites\fantasyquest.

Set full control for network services starting at c:\websites

Set full control for ASPNET starting at c:\websites (i know, prob not needed)

Opened IIS and highlighted Websites, Set to new Website

Used defaut ip address, port 80 and set host header to www.fantasyquest.org

Set pathcode to c:\websites\fantasyquest

Set to Read, write and script Execute

Set ASP pool to ASP2.0 and verified that default tab for asp.net was 2.0x

ran aspnet_regiis.exe -lk to verify pathcode

C:\>%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis  -lk
W3SVC/  2.0.50727.0
W3SVC/1945515001/root/  2.0.50727.0
W3SVC/1945515001/root/fantasyquest/     2.0.50727.0

At first i was getting an Error "Unrecognized attribute 'requirePermission'" so i deleted the IIS config and rebuilt it and did a IISRESET.

Before i put in a host header , i could do a

http://servername/fantasyquest/install/install.aspx?mode=install

But now, i am getting a page not found no matter whatever i try to utilize as a URL.

I have no idea what i might of done to cause this issue. Anyone see an issue? I've even tried re-enabling the default website and create a virtual directory to see if that made a different and got the same unrecognizeable error.

At this point i am not sure if it is the VPS or me.... HELP!!!

I am not sure why the VPS still thinks i am at NET 1.1 when everything else says it should be 2.x???

Aside from a few differences that should not make a difference, I can build it on my server at home under W2K3, IIS6, SQL 2005 with no issues. Go to a totally different setup in a VPS and.... BLAM!

It seems like everytime i change something to correct it per someone elses error i get another broken error.

There either seems to be to many moving parts outside of DNN to allow for a perm install factor to work properly.

I think i am done ranting for now, this is all very fustrating!

Dean