RE: [PHP-WIN] EXEC Problem

IT WORKS!!!!!!! Thanks, Ross. It turns out that the Apache service was running as "LocalAccount". I went into the Service area and set the Apache service to use a local user. I then went into dcomcnfg.exe and made sure that user could access COM objects by default. (Not sure if this was needed.) Thanks for you help, again. Now I am going to re-write this and see if I can take out the PHP-CLI exe. ;-) -- Scott Carr OpenOffice.org Documentation Maintainer http://documentation.openoffice.org/ Quoting Ross Fleming <r.fleming@clara.co.uk>: > Com terminated when I asked it too (technique depended on the com object). > Problem you might be having is that releasing the Com object doesn't > necessarily terminate the program. In the case of Winamp, if I only closed > with: > $winamp->Release(); > then the Winamp program would remain active, only the connection with > apache/php would drop. I had to issue a command to actually kill Winamp > first: > $winamp->sendcommand(WINAMP_FILE_QUIT); > $winamp->Release(); > > Ross > > > -----Original Message----- > > From: Scott Carr [mailto:scarr@progbits.com] > > Sent: 07 August 2002 19:02 > > To: Ross Fleming > > Cc: PHP Windows mailing list > > Subject: RE: [PHP-WIN] EXEC Problem > > > > > > Were you seeing you com object want to stay around like this? > > -- > > Scott Carr > > OpenOffice.org > > Documentation Maintainer > > http://documentation.openoffice.org/ > > > > > > Quoting Ross Fleming <r.fleming@clara.co.uk>: > > > > > Hmm. It's strange that it works from the command line but not through > > > Apache. My COM problems manifested in a similar way. The way > > I fixed it > > > was to meddle with the COM settings under Windows (using XP Pro > > btw). The > > > program dcomcnfg.exe allowed me to set which users were allowed > > to control > > > each registered COM application. Once I'd set Apache as a > > registered user, > > > there weren't any problems. > > > > > > Other than that I'm stumped > > > > > > Ross > > > > > > > -----Original Message----- > > > > From: Scott Carr [mailto:scarr@progbits.com] > > > > Sent: 07 August 2002 18:40 > > > > To: Ross Fleming > > > > Cc: PHP Windows > > > > Subject: RE: [PHP-WIN] EXEC Problem > > > > > > > > > > > > Actually, I am beginning to think it is an Object that is not > > being closed > > > > properly. > > > > > > > > The time the function is hanging is at the ->Release() method. > > > > The wierd thing > > > > is that it works great through PHP-CLI, just not through an > > > > exec() of PHP-CLI. > > > > > > > > I am going to look at the COM object to see if there is any > > > > objects that I can > > > > find not closing properly. > > > > > > > > The biggest problem I had when using COM directly, was that I am > > > > using a VB > > > > ActiveX object. I tried creating a very quick and dirty one > > > > liner that returned > > > > a value. When the object is attached to the APACHE process, > > > > weird things were > > > > happening. I figured using PHP-CLI would separate the process > > > > from the APACHE > > > > process, so it wouldn't be the cause of the problems I was seeing. > > > > > > > > If you have any ideas, i'd be very gratefull. I have to deliver > > > > the site in > > > > about a week. > > > > -- > > > > Scott Carr > > > > OpenOffice.org > > > > Documentation Maintainer > > > > http://documentation.openoffice.org/ > > > > > > > > > > > > Quoting Ross Fleming <r.fleming@clara.co.uk>: > > > > > > > > > One word: permissions :) > > > > > > > > > > What was wrong with COM? If I recall you emailed me when I > > had problems > > > > > with running winamp as a COM object, which I eventually managed > > > > to solve. I > > > > > tried your method of the php-cli stuff and it didn't work (same > > > > problems as > > > > > you're reporting) so tried harder with COM. If you need help > > > > re COM, mail > > > > > me. > > > > > > > > > > Ross > > > > > > > > > > > -----Original Message----- > > > > > > From: Scott Carr [mailto:scarr@progbits.com] > > > > > > Sent: 07 August 2002 18:14 > > > > > > To: PHP Windows > > > > > > Subject: [PHP-WIN] EXEC Problem > > > > > > > > > > > > > > > > > > I have a *VERY* wierd problem. > > > > > > > > > > > > I am running a PHP script through the EXEC command using php-cli > > > > > > from within the > > > > > > Apache PHP script. (I know wierd way of doing things.) Trying > > > > > > to run the COM > > > > > > object inside APACHE did not work too well, not sure why. > > > > > > > > > > > > If I run the php-cli script itself on the command line, > > > > > > everything works fine. > > > > > > The COM object does what it is supposed too. If I run the > > > > php-cli script > > > > > > through the APACHE page, the EXEC never returns. > > > > > > > > > > > > Why would there be a difference between running on the command > > > > > > line and running > > > > > > through EXEC? > > > > > > > > > > > > Any IDEAS? > > > > > > -- > > > > > > Scott Carr > > > > > > OpenOffice.org > > > > > > Documentation Maintainer > > > > > > http://documentation.openoffice.org/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------- > > > > > > This mail sent through IMP: http://horde.org/imp/ > > > > > > > > > > > > -- > > > > > > PHP Windows Mailing List (http://www.php.net/) > > > > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------- > > > > This mail sent through IMP: http://horde.org/imp/ > > > > > > > > > > > > > > > > > -- > > > PHP Windows Mailing List (http://www.php.net/) > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > > > ------------------------------------------------- > > This mail sent through IMP: http://horde.org/imp/ > > > > -- > > PHP Windows Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > -- > PHP Windows Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/