Good Day Jan,
I am running into an issue with OUTLOOK and the OFFLB.EXE and I am unsure of the cause, but I was executing PERL scripts using WIN32::OLE to execute Excel. Do you have any recommendations for the best practice to have the PERL script cleanly close/exit WIN32::OLE and EXCEL? Do you know and/or have seen issues with PERL and WIN32::OLE causing issues to have OFFLB.EXE kick in?
Thanks,
gary
not a bug in Win32::OLE
On Thu, 01 Sep 2011, gary sachs via RT wrote:
> I am running into an issue with OUTLOOK and the OFFLB.EXE and I am
> unsure of the cause, but I was executing PERL scripts using WIN32::OLE
> to execute Excel. Do you have any recommendations for the best
> practice to have the PERL script cleanly close/exit WIN32::OLE and
> EXCEL? Do you know and/or have seen issues with PERL and WIN32::OLE
> causing issues to have OFFLB.EXE kick in?
offlb.exe is the "Office Lifeboat" program. It starts up when one of the
Office application seems to be hanging. So maybe the way you are accessing
Excel is hitting a bug in the Excel Automation model. There is nothing
in Win32::OLE that can be done about this; I would suggest that you
ask for help with your application in a general Perl on Windows help
forum, e.g. the perl-win32-users mailing list. You will need to
post a sample program that reproduces the issue though, otherwise
nobody will be able to help you there either.
Cheers,
-Jan
Jan,
thank you. I am just covering bases at this point I am also exploring that OUTLOOK may have an issue since the problem did occur when I had not used the PERL script that uses EXCEL.
Thank you again,
gary
--- On Thu, 9/1/11, ja...@ActiveState.com via RT <bug-Wi...@rt.cpan.org> wrote: