Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...HELP! Major error in 4.3.1HELP! Major error in 4.3.1
Previous
 
Next
New Post
7/6/2006 7:01 AM
 

I don't know if we're supposed to report bugs or not, but this one's a real doozie. If nobody has a quick fix on this, then I'll just downgrade from the RC to the earlier version.

My setup:
Server 2K3, connecting to SQL Server 2000.

The issue:

Trying to access the root of my portal (or any page thereof) after setting up a few core modules (FAQ, Blog, and IFrame) gives me the following:

Server Error in '/portal' Application.
--------------------------------------------------------------------------------

The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace:


[HttpException (0x80004005): The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
   System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection) +3474123
   System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags) +226

[HttpException (0x80004005): The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3426855
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +149


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42  

The symptoms:

First time, it happened right after I installed the blog. After installation, I navigated to the "Home" tab, and promptly got a debug option for Visual Studio 2005, but nothing apparent was "broken" on the page. I dropped my portal database, deleted all files, and started fresh. This time, I tried to install the events module, and as soon as the page refreshed, it told me the module was not available and that an exception had occured. The Visual Studio debug dialog popped, I opted not to debug, exited Explorer, and came back. This is all that will show up. I cannot reach any DNN page.

What I've tried:

* Giving "Network Service" full control recursive access to the 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727' folder. An effective permissions audit confirmed that Network Service had full control access rights to the 'Temporary ASP.NET Files' directory. Problem did not resolve.

 

 
New Post
7/8/2006 9:12 PM
 
I recently had to do a repair on my OS (Windows XP Pro). And I am getting the same error, however DNN was working before
 
New Post
7/8/2006 9:47 PM
 

4.3.2 is out. Maybe that'll help!

4.3.1 is fine for me. Perhaps try full reinstall ('upgrade' by unzipping a current Install over top of your current) in case that helps. I've had problems before with bad/incomplete copies.

- J 

 
New Post
7/8/2006 10:27 PM
 
What you can do before the upgrade to 4.3.2 is to reboot the server (I am assuming this is your owner server), remove all files and folders under
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files and start DNN again.

This may not be a DNN issue but rather just a file lock in the ASP.NET temp folder.


Enterprise Forms for DotNetNuke

Version Control, Forms and Workflow Suite

 
New Post
7/9/2006 12:11 PM
 
I've had that happen to me before as well (taking the steps Ethungmai described was necessary to make those changes you describe "take affect").  Several times on different machines I've had that happen, in fact.  I guess it's fairly common.


Shane Miller
Call Centers 24x7
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...HELP! Major error in 4.3.1HELP! Major error in 4.3.1


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out