Unable to run excel via cron

Kiehl, Horst h.p.kiehl@fz-juelich.de
Wed Jun 17 15:09:00 GMT 2015


(Trying to remove TOFU to make the conversation appear chronological again and with correct attributions.)

Kertz, Denis (D)** CTR ** <d.kertz at alcatel-lucent dot com> wrote:
> > > We need to run some Excel programs via cron and are using vbscript to do this.  We have this running on a WinXP machine but are having trouble running on a Win7 machine, but we don't think it is a Win7 problem.
> > >
> > > Here's the script to run a simple test excel program:
> > >
> > > [...]

Bryan Berns wrote:
> > What bitness of Excel and Cygwin are you running?
> >
> > CreateObject("Excel.application") will attempt to create a 32-bit
> > instance of Excel when launched through the 32-bit version of
> > wscript.exe or a 64-bit instance of Excel when launched through the
> > 64-bit version of Excel.  Which bitness of WScript.exe ends up being
> > run will depend on the bitness of the parent program (which may be
> > different in a command prompt vice Cygwin).  Try changing it to run
> > Wscript.exe in SysWow64 instead of System32 (which is subject to
> > automatic redirection) and see if changes the behavior.  If you're not
> > running a 64-bit OS, then just ignore everything I said.

Kertz, Denis (D)** CTR ** wrote:

> Unfortunately, using the 64-bit wscript.exe didn't change anything - same behavior as before with excel hanging.
>
> We are using 64-bit cygwin and 32-bit Excel (Excel 2007).

Although the aspect Corinna wrote about may be the culprit already,
just in case:

It appears that you, Denis, were misunderstanding Bryan. The consequence
of what he tried to point out might be that you, using 64-bit Cygwin and
32-bit Excel, would have to explicitly use the 32-bit wscript.exe
instead of the 64-bit wscript.exe, to make sure that wscript.exe
(32-bit) will start Excel (32-bit) successfully. In other words, you
might have to use $windir/SysWOW64/wscript.exe (i.e.
%windir%\SysWOW64\wscript.exe) from your 64-bit Cygwin process.

(The reason for the seemingly backwards 32-bitness and 64-bitness of
executables in SysWOW64 and system32, respectively, if viewed from a
64-bit process, is to make code with hardcoded "system32", whether
compiled or interpreted, continue to work in a 64-bit context as well as
in a 32-bit context.)

Horst


------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple



More information about the Cygwin mailing list