X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=AWL,BAYES_40,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Message-Id: <1338905409.23655.140661085234789.6455A2A0@webmail.messagingengine.com> From: Ronald Fischer To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Subject: Can not install cron (authorization problem) Date: Tue, 05 Jun 2012 16:10:09 +0200 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 I'm on Windows 7 (64Bit), with local admin rights. My first attempt to install the cron services, failed like this: .... Do you want the cron daemon to run as yourself? (yes/no) yes Error in openPolicy (LsaOpenPolicy returned 0xc0000022=STATUS_ACCESS_DENIED)! .... I thought that maybe I have to do this as administrator. I therefore opened a mintty by running it as administrator, and executed cron-config again. This time, indeed, the error message does not occur anymore. However, after entering my user id and Windows password, I got the error message: .... Do you want the cron daemon to run as yourself? (yes/no) yes Please enter the password for user 'rofischx': Reenter: cygrunsrv: Error installing a service: CreateService: Win32 error 1057: The account name is invalid or does not exist, or the password is invalid for the account name specified. .... Now I'm absolutely sure that I entered my password correctly (I tried several times, always the same effect), and the user name is also correct. What else could be the problem? BTW, the command 'id' shows: uid=437575(rofischx) gid=10513(Domain Users) groups=10513(Domain Users),0(root),544(Administrators),545(Users) Ronald -- Ronald Fischer + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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