PDA

Click to See Complete Forum and Search --> : file server hosted files


carlblanchard
Nov 5th, 2004, 08:17 AM
Hi All

At our datacentre we use file servers and the IIS installations are pointing to the file server like \\machine\share

i can access the file directory fine however when i go to run the application i get this error


Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Required permissions cannot be acquired.

Source Error:


Line 196: <add assembly="System.EnterpriseServices, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 197: <add assembly="System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 198: <add assembly="*"/>
Line 199: </assemblies>
Line 200: </compilation>




anyone lnow whats going on ? kor how to fix it

plenderj
Nov 5th, 2004, 08:24 AM
ASP.NET Applications are executed by the Network Service account. Ensure that the Network Service on the IIS server itself has permissions :)

carlblanchard
Nov 5th, 2004, 03:42 PM
So the network service should be on the file server ?

plenderj
Nov 9th, 2004, 04:34 AM
On the file server ensure that the network service of the IIS system has rights :)

carlblanchard
Nov 9th, 2004, 07:51 AM
Done that however i think the main problem is the fact the application pool is pointing to folders on the local directory and this particular site is outside that application pool

plenderj
Nov 9th, 2004, 08:08 AM
Okay so the source folder for the actual application itself is on \\someserver, but is being executed / 'hosted' by IIS on \\someotherserver ?

carlblanchard
Nov 9th, 2004, 12:27 PM
yes the source files are at \\server\share

plenderj
Nov 9th, 2004, 03:03 PM
Urgh. How about this.
Use DFS, and have the file physically stored on the IIS server (thus getting around any weird issues), but then it'll still appear as though they're in the same location when shared over the AD.