Try our conversational search powered by Generative AI!
AI OnAI Off
Read/Write permissions on remote VPP-folders
Hello Marcus,
Check which identity is used to run application pool of your web site. You application pool identity should have permission to access those network locations. If application pool uses some default account like Network Service, you can try to add your machine account to the VPP folder permissions.
Jan 24, 2013 14:15
Thank you for your answer, Sergii!
I finally got it working after our server technician shared (?) a folder.
Instead of \\192.168.X.YY\C$\EPiServer\VPP\elmiaepi\PageFiles I can now write \\192.168.X.YY\EPiServer$\VPP\elmiaepi\PageFiles.
Jan 25, 2013 14:24
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
Hi!
When I'm running our EPiServer-project on my local IIS (version 7.5), I'm trying to access VPP-folders on another remote machine. However, this doesn't work and I get a System.UnauthorizedAccessException.
Does anyone know what group or user I have to add to the VPP-folder to get rid of the exception?
I have the following mappings in the file EPiServer.config (X and Y are dummy values):
\\192.168.X.YY\C$\EPiServer\VPP\PageFiles
\\192.168.X.YY\C$\EPiServer\VPP\Global
\\192.168.X.YY\C$\EPiServer\VPP\Documents
\\192.168.X.YY\C$\EPiServer\VPP\GlobalaFiler
The exception:
Access to the path '\\192.168.X.YY\C$\EPiServer\VPP\PageFiles' is denied.
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.UnauthorizedAccessException: Access to the path '\\192.168.X.YY\C$\EPiServer\VPP\PageFiles' is denied.
ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.
To grant ASP.NET access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
//Marcus