X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:subject:date:message-id:content-type :content-transfer-encoding:mime-version; q=dns; s=default; b=n+t iwiOYq42NAuMf/w34nBDUzkeGl0pJ7JcqsUjFX/7nr2IrUby4C8dlghSg/bY0IIA ueRqElAiCCPHhQkSDlECVtlueUu23yvTB9Tq8etfqVE4XxklCUCB7oza8TzTuEf/ yiBNswXxKxvLRQOR1PWUE1bnN+mnXxh7uWoBKatI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:subject:date:message-id:content-type :content-transfer-encoding:mime-version; s=default; bh=hCJ2/peBa wuwuubL8hzY0YAwb40=; b=Si3UiClWfLJEaj72BN1ojIOFuDwp8uoupwu4QzupF ga0JLFr73UlIZkFuXSnWb/Rbj0VZeq4PSZUuUY7YZCXoJZH5z9LgrgARgMADb1Gx Vplji4c/7MoanfAgkULwnxvXkVmfLBxYBTHTbiSJsSx19pSXvTNxH3OeuZyCm8lL P8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.0 required=5.0 tests=AWL,BAYES_80,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: smtp-fr.alcatel-lucent.com From: "Kertz, Denis (D)** CTR **" To: "cygwin AT cygwin DOT com" Subject: RE: Unable to run excel via cron Date: Wed, 17 Jun 2015 13:29:00 +0000 Message-ID: <883F2CBBC85A62419E181EB2F0ECF21F45DE3905@US70UWXCHMBA04.zam.alcatel-lucent.com> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t5HDTO6P030350 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). Denis On Tue, Jun 16, 2015 at 9:27 AM, Kertz, Denis (D)** CTR ** 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: > > Dim xlApp > Dim xlWb > Set xlApp = CreateObject("Excel.application") > xlApp.Visible = True > Set xlWb = xlApp.workbooks.Open("c:\Shared\Prospect\Bin\TestExcel.xls") > xlApp.Quit > Set xlWb = Nothing > Set xlApp = Nothing > 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. -- 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