My environment is Windows Server 2012 R2, IIS 8, Active Directory, and a file share. IIS, AD, and the file share are all separate VMs.
I have a website, www.example.com, set up in IIS. The application pool identity is set up as the AD user
IUSR_example, which has "full control" permissions on the folder containing the site files. The site files are on the file share, which IIS references via UNC path.
In general, the site works in that it can serve up PHP, ASP.Net, and ASP Classic pages, and the code can even create new files.
However, I am having a problem that seems specific to PHP
exec(). I've tried calling
ffmpeg, and I get nothing returned from them. Using Sysinternals Procmon I have confirmed that the executable never starts.
Weirdly enough, I am able to make the exact same calls with ASP Classic (using
WScript.Shell), and it works perfectly. I am also able to get PHP
exec() working when the scripts are NOT running over the UNC path.
Here's what I've tried/found:
- When using ASP, procmon reports that w3wp.exe spawns a cmd.exe process, which in turn spawns conhost.exe and (for example) ffmpeg.exe. The output file from ffmpeg successfully appears.
- When using PHP, procmon reports that w3wp.exe spawns a php-cgi.exe process, which in turn creates a cmd.exe and a conhost.exe. A thread for ffmpeg.exe never appears.
- cmd.exe is invoked with a command line that looks like this:
cmd.exe /c ""--the command to be executed--""
- The command line for the cmd.exe process is exactly the same for both ASP Classic and PHP.
- In Procmon, the user is always reported as
- I've tried adding
2>&1to the end of the command
- I've tried giving the IUSR to the "Replace Process-level Token" right
- I've tried turning off FastCGI impersonation and switching between "NamedPipe" and "TCP" under Process Model > Advanced Settings
- There are no errors in the PHP error log
- There are no errors in any of the Windows Event logs
Note that this is not specific to ffmpeg. Any other use of
exec() also fails. Also, I would prefer not to use
WScript.Shell from within PHP because eventually we will be using WordPress plugins that rely on
How can I further troubleshoot this?