The same thing happened to me with IIS a year and a half ago. For security reasons, the web server clamps down on scripts trying to start new processes. Very annoying, especially since the documentation didn't mention it.
Unfortunately I never did find a way to start new processes using IIS. I ended up writing a very simple web server in Perl to solve the problem instead. /Henrik > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Mike > Brzezinski > Sent: Friday, May 24, 2002 6:15 PM > To: '[EMAIL PROTECTED]' > Subject: Running a batchfile from CGI on Win2k server > > > I can't seem to get a batchfile to run on Win2K server from my CGI script: > I've tried various things using both exec() and system(), such as: > > $bfile = "c:/my.bat"; > system($bfile); > > system("cmd.exe /x/c c:/my.bat"); > > system("cmd.exe", '/x/c c:/my.bat'); > > The funny thing is that system($bfile) works just fine on Win2K > professional. I don't notice any other problems running CGI scripts. Any > ideas? > > --- > This email may contain material that is confidential and provided for the > sole use of the intended recipient.� Any forwarding or > distribution of this > email to others or review of this email by others without express > permission > is strictly prohibited.� If you are not the intended recipient, please > contact the sender and delete all copies. > > _______________________________________________ > ActivePerl mailing list > [EMAIL PROTECTED] > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs > _______________________________________________ ActivePerl mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
