Forums
>
Users Lounge
>
DNN Creative Articles
No asp.net user account on XP Pro
Last Post 09/05/2007 8:14 PM by
Joseph Craig
. 4 Replies.
Author
Messages
brian
Nuke Newbie
Posts:2
09/05/2007 5:04 AM
Just followed the excellent videos on How to install DotNetNuke 4.5 to Windows XP Professional (Using IIS). Tried it on my XP Pro machine which has .net 1.1 and .net 2.0 but I have no aspnet user account setup. Anybody know how to get round this?
Thanks
Brian
larryreader
Nuke Newbie
Posts:8
09/05/2007 8:18 AM
Hello
I just fixed this problem by navigating to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 in the command prompt and running ASPNET_regiis -r
This seems to do a reinstall of the .net framwork and I got an aspnet user out of the process. Now I am stuck at a screen on the local install copied from the host - The Site is currently unavaliable.
brian
Nuke Newbie
Posts:2
09/05/2007 8:53 AM
Thanks Larry. I have just got round the problem using a similar way to your solution by going to Add/Remove programs and doing a repair for the .Net 2.0 install.
Now I am further into the install and have got a message from the install which is:
Directory "C:\inetpub\wwwroot\site\Portals\_default\Cache" does not exist. Failed to start monitoring file changes
I am going to try 4.5.1 as I have a slightly earlier version.
Brian
Joseph Craig
DNN MVP
Posts:11667
09/05/2007 8:11 PM
You message seems to refer to an IIS issue rather than a DotNetNuke issue. Given that your .Net installation need to be fixed, it's possible that there's something wrong with the IIS installation, too.
Joe Craig,
Patapsco Research Group
Complete DNN Support
Joseph Craig
DNN MVP
Posts:11667
09/05/2007 8:14 PM
larryreader:
Try putting a simple html file in your DotNetNuke directory named app_offline.htm. If IIS is working correctly, it should serve up that page bypassing DotNetNuke.
If that works, rename the file and see if the DotNetNuke error happens again. Assuming it does, you might want to create a fresh/empty database and point your DotNetNuke installation there. Then, browsing to the site should install DotNetNuke in the new database. That, at least will confirm if your DotNetNuke installation is working.
Joe Craig,
Patapsco Research Group
Complete DNN Support
Forums
>
Users Lounge
>
DNN Creative Articles