in reply to Re: Excel exe still hanging 'round
in thread Excel exe still hanging 'round

Thanks Ted. Seems like it done the trick. Quick question though: By calling the Win32::OLE->Uninitialize does that or will it affect other simultaneous Excel processes running by other users on that machine? I'll see what I can find but what does the Uninitialize do (i.e. deletions, clears, etc..,)? Thanks so much for the reply. I had noticed some methods listed (including this one) but it wasn't near the top of methods I was going to try so thanks for saving me the trouble.

Rob

Replies are listed 'Best First'.
Re^3: Excel exe still hanging 'round
by TedYoung (Deacon) on Jan 10, 2006 at 13:35 UTC

    I strongly suspect it is mearly a call to the function CoUninitialize(); which uninits COM for the current thread. So, it should not effect other CGI processes.

    Ted Young

    ($$<<$$=>$$<=>$$<=$$>>$$) always returns 1. :-)
[reply]
[d/l]
      Do you happen to know a good doc on-line that lists out some of the methods available (including CoUninitialize)? Thanks for the info as well. Rob
[reply]
      Hi again Ted, Just a quick question hopefully. We have a web site set up whereby remote users log-in (I guess Windows Authenticated or whatever). One user logs in as administrator while the second as a plain user. The administrator can use the perl/cgi script fine. The other user cannot and gets an "Access is Denied" when she hits the code trying to initialize Excel (using GetActiveObject method). We've checked the permissions on the Excel.exe and set the permissions accordingly on the whole Microsoft Office directory but still it gives this error. Should the permissions be checked solely on the Registry key for Excel.Application or are there more things needed to be checked for permissions? Many thanks. Rob
[reply]

        Hi, I hope you can find this all the way down here. May have been a good idea to post this as a second topic.

        Sounds like you are using Windows Authentication under IIS. That means the administrators will have complete access to all COM objects, but, in this case, the "plain user" does not. You can check the DCOM Config and give that "plain user" access to Excel.Application. That is how you are supposed to do it (I don't remember the comand to bring up dcomconfig, you will have to google that). The reality of it is that this may not work. It IS Microsoft afterall. :-) Sorry! Anyway, you may have to change the permissions of the user account being used by "plain user"s to an admin account. Of course, you should realize that there are some potential security implications if you need to do this. But I have had a popular site running this way for 5 years with no problems so far.

        Ted Young

        ($$<<$$=>$$<=>$$<=$$>>$$) always returns 1. :-)
[reply]
[d/l]

In Section Seekers of Perl Wisdom