Solved

Access to the path "E:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\dynamore\4a86abb9\9949d261" is denied.

Posted on 2006-07-04
2
695 Views
Last Modified: 2008-02-01
Hi Experts,

I have been encountering this error since I moved my ASP.NET (Web application using VB.net) code from Windows Xp Professional to Windows Server 2003. It works perfectly on Xp Pro. I then granted ASPNET access to the E:\WINDOWS\Microsoft.NET\Framework folder, even E:\WINDOWS\Microsoft.NET, but the error still exists.

********************************************************************************************************
Server Error in '/Dynamore' Application.
--------------------------------------------------------------------------------

Access to the path "E:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\dynamore\4a86abb9\9949d261" is denied.

********************************************************************************************************

This is my Web.Config:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
         <appSettings>

            <add key="ConnectionString8" value="Provider=Microsoft.Jet.OLEDB.4.0;User ID=Admin;Jet OLEDB:Database Password=6;Data Source=d:\Dynamore\Database\Dynamore.mdb"></add>
            <add key="connectionString1" value="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=Server.MapPath('Database\\directory.mdb')"/>
            <add key="ConnectionString4" value="server=OLMDATA1;User ID=BudgetUser;password=budgetuser;Initial Catalog=Budget"/>
        <add key="ConnectionString2" value="workstation id=LW0009;packet size=4096;user id=411all;integrated security=SSPI;data source=OLMDATA1;persist security info=False;initial catalog=Budget"/>

      </appSettings>
  <system.web>

    <!--  DYNAMIC DEBUG COMPILATION
          Set compilation debug="true" to insert debugging symbols (.pdb information)
          into the compiled page. Because this creates a larger file that executes
          more slowly, you should set this value to true only when debugging and to
          false at all other times. For more information, refer to the documentation about
          debugging ASP.NET files.
    -->
    <compilation defaultLanguage="vb" debug="true"><assemblies><add assembly="CrystalDecisions.CrystalReports.Engine, Version=9.1.5000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>
    <add assembly="CrystalDecisions.ReportSource, Version=9.1.5000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>
    <add assembly="CrystalDecisions.Shared, Version=9.1.5000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>
    <add assembly="CrystalDecisions.Web, Version=9.1.5000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/></assemblies></compilation>

    <!--  CUSTOM ERROR MESSAGES
          Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable.
          Add <error> tags for each of the errors you want to handle.

          "On" Always display custom (friendly) messages.
          "Off" Always display detailed ASP.NET error information.
          "RemoteOnly" Display custom (friendly) messages only to users not running
           on the local Web server. This setting is recommended for security purposes, so
           that you do not display application detail information to remote clients.
    -->
    <customErrors mode="RemoteOnly"/>
      <identity impersonate="true"/>
    <!--  AUTHENTICATION
          This section sets the authentication policies of the application. Possible modes are "Windows",
          "Forms", "Passport" and "None"

          "None" No authentication is performed.
          "Windows" IIS performs authentication (Basic, Digest, or Integrated Windows) according to
           its settings for the application. Anonymous access must be disabled in IIS.
          "Forms" You provide a custom form (Web page) for users to enter their credentials, and then
           you authenticate them in your application. A user credential token is stored in a cookie.
          "Passport" Authentication is performed via a centralized authentication service provided
           by Microsoft that offers a single logon and core profile services for member sites.
    -->
    <authentication mode="Windows"/>


    <!--  AUTHORIZATION
          This section sets the authorization policies of the application. You can allow or deny access
          to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous
          (unauthenticated) users.
    -->
    <authorization>
        <allow users="*"/> <!-- Allow all users -->

            <!--  <allow     users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
                  <deny      users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
            -->
    </authorization>

    <!--  APPLICATION-LEVEL TRACE LOGGING
          Application-level tracing enables trace log output for every page within an application.
          Set trace enabled="true" to enable application trace logging.  If pageOutput="true", the
          trace information will be displayed at the bottom of each page.  Otherwise, you can view the
          application trace log by browsing the "trace.axd" page from your web application
          root.
    -->
    <trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true"/>


    <!--  SESSION STATE SETTINGS
          By default ASP.NET uses cookies to identify which requests belong to a particular session.
          If cookies are not available, a session can be tracked by adding a session identifier to the URL.
          To disable cookies, set sessionState cookieless="true".
    -->
    <sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes" cookieless="false" timeout="20"/>

    <!--  GLOBALIZATION
          This section sets the globalization settings of the application.
    -->
    <globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
   
  </system.web>

</configuration>

********************************************************************************************************

Thanks in advance!

Grace :)
0
Comment
Question by:grace627
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 15

Accepted Solution

by:
deepaknet earned 250 total points
ID: 17041518
Typical indexing server issue. Check out this URL at: http://blogs.wwwcoder.com/deepak/archive/2004/10/14/885.aspx
0
 

Author Comment

by:grace627
ID: 17060037
Hey Deepaknet,

I actually got it solved by adding "NETWORK SERVICE" acccount to that folder.

The ASP.NET process account in Server 2003 isn't ASPNET, it's the NETWORK SERVICE account (unless you changed it).

Thanks,
Grace
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This is an explanation of a simple data model to help parse a JSON feed
Although it can be difficult to imagine, someday your child will have a career of his or her own. He or she will likely start a family, buy a home and start having their own children. So, while being a kid is still extremely important, it’s also …

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question