in reply to Excel Win32::OLE->Uninitialize

I have had similar problems. One thing is to be sure that the problematic installation is a recent versionof Office. OLE automation in some earlier versions was prone to problems like this.

Another thing is to be sure to set the objects associtatd with Excel to undef. The object needs to be RELEASEed. That should be automatic, but I am not sure it always is. I do not know the perl form of the explicit RELEASE.

HTH --traveler

Replies are listed 'Best First'.
Re^2: Excel Win32::OLE->Uninitialize
by Anonymous Monk on Jan 13, 2006 at 20:49 UTC
    Traveller,

    I tried using the undef function on the objects in question... nothing. I was looking at the properties in DCOM and there are a few things in there to set according to user. Would any of these settings disallow the script (the user is running) to not be able to uninitialize but allow it to start up and run fine? Thanks for the info before. Oh, also, the customer machine and the machine I'm running the script on locally are pretty much similar (same OS, same version of perl, etc..,).

    Rob

[reply]
      I have not had any experience with the properties you allude to. I did some reading and some folks have mumbled about not closing excel if program that started it does not exit or clean up well. Sorry, the writers were not too explicit. How are you running it at the client? From DOS? When you run it from the browser, how are you starting it? Is a web server involved?
[reply]
        I tried it both from DOS and the browser (works for both locally and only tried it on the customer's end from the browser and it doesn't). Yes a web server is involved (IIS) in both cases. I'm using Win32::OLE to grab the object is there a way to obtain the process ID and terminate it some other way? Thanks for reply. Rob
[reply]

In Section Seekers of Perl Wisdom