I have a Windows 2008 box running IIS7. The server hosts an ASP.NET application that absolutely needs to fire up an external process - an executable located in this same machine.
This setup works fine in the ASP.NET development server, but fails thoroughly when IIS is involved. I've tried everything: modifying the machine.config file, changing the app Application Pool's identity, playing around with file and folder permissions, changing the settings in the service's "Log On" tab... nothing works.
It doesn't matter which executable I try to run, either. Even "notepad.exe" fails.
I'm probably missing something, because a task so trivial shouldn't be this hard. Yes, I'm aware of the security implications of what I'm trying to do, but in this case there is just no other way.
Thanks in advance.