- Posted by Ian Suttle on March 25, 2008
- Filed under .Net Framework | WCF
We're working on our first Windows Communication Foundation (WCF) project hosted in IIS6. Upon deployment we ran into a wall when requesting a .svc file - 404. After hours of chatting with Microsoft on the phone and consulting with Filemon it ended up being a simple issue - the app pool identity was running as Network Services and not a domain account. This was problematic because our files live on a network share, and although we connected to it with a domain account, the app pool account did the executing.
Hmmm... "executing." Interesting it gave a 404 and not some access denied message right? The MS support rep said there are basically two tokens used; one for connecting and one for executing which seems to indicate retrieving of the file as well.
Another lesson learned.
