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=SkK I8oEBkUxG3+ges9TxINtxHNJCprfv3Y9mbxlzIL0Jn6pJOzqdc1yGebsEGIRg7Fg HXIbbrlMp5OsJ3o2KQYpgEuCS1v7iXN/Z5V5xmNBl1Pzw2/WtADpqKTF4llxj85p B8YDcBq/FTXjhi2bxZwsnAWBwoMx73CmOkdu/0WA= 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=H9PyGT0j7 ihjq/GZQ/b+sDHbodc=; b=s2V2u9cVhZwlxwLaJKKRBJoUIveapYavvyYSXMoDC ev4B0Weaaby22/a4yAD9T3Mu7Oi7TdP6Wuwzbv2KK7Qnd+Fla+wDdlo3jcqJX278 Ax2HIfO61n1AmAknl7vkVdxIEfRo6DvjbSqfQNRfyqXYPSPOAUdAaBXvU7gESneC 2k= 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=2.7 required=5.0 tests=AWL,BAYES_50,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: Thu, 18 Jun 2015 15:55:55 +0000 Message-ID: <883F2CBBC85A62419E181EB2F0ECF21F45DE3E87@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 t5IFuEGB016620 Well, not so lucky anymore. Last night I re-ran my Excel test on the Win7 PC that worked previously and now it doesn't work. So I guess some Win7 patch must have come along and "fixed" something. Denis Larry Hall wrote: On 06/17/2015 12:55 PM, Kertz, Denis (D)** CTR ** wrote: > We are running cron under the specific cygwin login (not cyg_server). > Presumably there is a solution to this problem. We have 3 Win7 Pro PCs > and this works on one of the PCs (unfortunately, not the one where we need it to > work) and fails on the other two PCs. The behavior here has always been somewhat unpredictable. Some have luck getting this to work post-XP, some don't. Some, like you, sometimes have luck. It's not clear why. But it is clear that MS changed the behavior in Vista and beyond for security reasons. They are trying to make this difficult if not impossible to do. As Corinna mentioned, getting an Windows authenticated token for the user running the server may help. Or not. ;-) -- Larry -- 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