Hi Sandeep,
Have you had a chance to have a look at my previous reply ,either? In my
last message, I've listed some suggestion on how to determine the ASP.NET
application's worker process identity or security context. Then, checking
whether that identity/account has sufficient permission to modify the
target directory. In addition, the "filemon" utility I mentioned earlier
is a good tool for tracing file access failure (you can find which account
failed to access which file on the machine). In case you haven't found my
last reply, here is a copy from the former message:
################################################## ###########
Hi Sandeep,
For such file deleting Access_Denied error, it has the following possible
causes:
1. The current ASP.NET application's running security identity doesn't have
the sufficient permission to delete the target file. Genernally if you're
not using impersonate in your ASP.NET application, the current security
context of the application is the worker process's identity. You can check
your ASP.NET application's worker process identity according to the
following MSDN article:
#Configuring ASP.NET Process Identity
http://msdn2.microsoft.com/en-us/library/dwc1xthy.aspx
Also, a simple means to get the current process identity is execute the
following code in your page to printout the current security context:
==========
protected void Page_Load(object sender, EventArgs e)
{
Response.Write("<br/>Security Identity: " +
System.Security.Principal.WindowsIdentity.GetCurre nt().Name);
}
===========
After you've determined the security identity, verify that whether this
identity(account) has the sufficient permission to manipulate the target
files or folder).
BTW, for tracing file access permission issue, the filemon utility is quite
common and useful:
http://www.sysinternals.com/utilities/filemon.html
2. Suppose the security identity has the sufficient permission to
manipulate the target file, it is possible that the file's filehandle is
locked by some other process which make the ASP.NET process fail to acquire
the file handle. To check file handle lock/ownership, the processexplorer
utility is a helpful one:
#How To Determine File Handle Ownership
http://support.microsoft.com/kb/q232830/ http://www.sysinternals.com/Utilitie...sExplorer.html
Please have a look at the above things. If you have anything unclear or if
you meet any further problems, please feel free to post here.
Sincerely,
Steven Cheng
################################################## #########
Please feel free to let me know if you have anything unclear here.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.