IIS7 does not start my Exe file by Process Start

What helped me is this: Setting in Application Pool Identity = LocalSystem

1. Open Application Pools
2. Find your pool (by default DefaultAppPool)
3. Click on "Advanced settings"
4. Change Identity to "LocalSystem"

Hopefully it will help somebody...

Giving Full Control permission to any web users is always a very bad idea. For a better solution, please see Process.Start doesn't work in IIS

Edit:

After a long journey, me and Nasenbaer have found the following. The possible reasons for IIS to fail run an EXE are:

1. Lack of permissions for IIS Users, such as the application pool user, or the Network service (in IIS6).
2. x86 EXE running on x64 machine issues.
3. Typical EXE failure issues such as missing dependencies.

Original answer:

You need to assign FullControl security permissions for the IIS AppPool\DefaultAppPool user, on the directory the EXE is located in. This is the user that is trying to run the process (assuming you are using the DefaultAppPool), and without the proper permissions, it is unable to do so.

When you run the EXE manually, you are using the Windows logged in user. This is why you are able to lunch it manualy. The IIS uses the Application Pool user.

To add permissions just do the following:

1. Go to directory properties
2. Security tab
3. Edit.. -> Add the IIS AppPool\DefaultAppPool
4. Check for it the FullControl

Screenshot: