delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/09/08/16:26:14

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Originating-IP: [66.243.111.27]
X-Originating-Email: [kalina813 AT hotmail DOT com]
X-Sender: kalina813 AT hotmail DOT com
From: "Anna Goldberg" <kalina813 AT hotmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin Cron on Windows 2003 Server Issues
Date: Wed, 08 Sep 2004 15:24:42 -0500
Mime-Version: 1.0
Message-ID: <BAY18-F13XkuiwqfVYJ0003b4c0@hotmail.com>
X-OriginalArrivalTime: 08 Sep 2004 20:24:42.0830 (UTC) FILETIME=[DFCF46E0:01C495E1]

We tried running cron_diagnose.sh, but that didn't produce any usefull 
answers, the output we get is:

$ ./cron_diagnose.sh
cron_diagnose.sh 1.5

Your computer does not appear to have a crontab for <administrator>.
Please generate a crontab for <administrator> using 'crontab -e',
and run this script again.

The version of cron we have is:
# (Cron version -- $Id: crontab.c,v 1.7 2003/04/15 15:13:41 corinna Exp $)

The error that appears in the Event Viewer when trying to run the service 
is:

Event Type:	Error
Event Source:	cron
Event Category:	None
Event ID:	0
Date:		9/8/2004
Time:		2:36:16 PM
User:		<Server Name>\service_cron
Computer:	<Server Name>
Description:
The description for Event ID ( 0 ) in Source ( cron ) cannot be found. The 
local computer may not have the necessary registry information or message 
DLL files to display messages from a remote computer. You may be able to use 
the /AUXSOURCE= flag to retrieve this description; see Help and Support for 
details. The following information is part of the event: cron : PID 2332 : 
starting service `cron' failed: execv: 128, Transport endpoint is not 
connected.


We've created a custom local user account called service_cron and gave it 
the following permissions:
- SeAssignPrimaryTokenPrivilege
- SeCreateTokenPrivilege
- SeIncreaseQuotaPrivilege
- SeServiceLogonRight
and installed the cron service as this user, but we were not able to start 
the service.

Then we removed the cron service and re-installed it under the Local System 
user account, at which time we were able to start the service, but are now 
getting the error listed above when the scheduled task(s) is run.

Let me know if any more information is needed.

Thank you,

~ Anna

_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to 
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019