IIS AppPoolIdentity and file system write access permissions
Here’s an issue with IIS 7.5 and ASP.NET that I’ve been researching and getting nowhere with. Any help would be greatly appreciated.
Here’s an issue with IIS 7.5 and ASP.NET that I’ve been researching and getting nowhere with. Any help would be greatly appreciated.
ASP.Net 3.5 running under IIS 7 doesn’t seem to allow this out of the box.
I have an ASP.NET app which needs to save files to a network share (Samba).
Is there a way to access the file-system outside of the current ASP.NET application, without going around giving IIS_IUSRS permissions? For example, if I wanted this line to work:
I’ve been developing an ASP.NET site on an older machine running XP home. I recently got a new Win 7 PC and moved all my project files across. When I try and run the project, I get this error message:
I am trying to upload files and convert them to another format before saving them on my web server, but I get the following error:
System.ComponentModel.Win32Exception (0x80004005): Access is denied at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start()
I have a webserver from where users can download files that are specific for each user. To be sure each user can only download its own files they must authenticate via Basic-Authentication. So for each user there is a windows-account on the server that has read permissions to the user specific folder.
Hey all, I need some advice on this…
We have a rather complicated system of permission handling in our (ASP.NET web) application. Users can have specific permissions on different kinds of objects, some permissions are even packed into groups / roles that are assigned to users. All in all this ends up in a pretty complicated mess where for determining whether a user can do / see something you have to evaluate many different sources of permissions and this is done somehow on-demand and based on specific situations.
I’m using Lucene.Net in an ASP.NET application on a shared host. Got this stack trace shown below. What’s the work around?