Hello, I'm trying to write a perl CGI (under IIS, using perlIS.dll) that spawns a server process when you click a Submit button. This server process does a whole bunch of stuff, fetches code from source control, runs a build, etc. And this perl CGI runs fine when I run it directly from the console, fetches code, runs build etc. But when I call it thru IIS, it seems to fail to successfully spawn the server process.

I've tried using system(), backticks, Win32::Process::Create ... I'm wondering if there is some weird limitation that IIS imposes on processes that prevents them from spawning child processes. Anyone ever heard of this kind of limitation?

If this really is a limitation, it seems I might try to work around it by having the server process always running, and listening on a port for requests, and having the CGI triggering it to run a task through sockets when requested. Though I'd rather not have to build all that if I don't have to.