Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 689C3DD22 for ; Fri, 28 Dec 2012 07:18:14 +0000 (UTC) Received: (qmail 94156 invoked by uid 500); 28 Dec 2012 07:18:13 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 94021 invoked by uid 500); 28 Dec 2012 07:18:13 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 93977 invoked by uid 99); 28 Dec 2012 07:18:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Dec 2012 07:18:12 +0000 Date: Fri, 28 Dec 2012 07:18:12 +0000 (UTC) From: "Wallace (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DAEMON-273) Fail to start service in 32-bit Windows MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DAEMON-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wallace updated DAEMON-273: --------------------------- Description: When using latest version (1.0.11) of prunsrv.exe, the service failed to start (//ES) with the following error: *** [2012-12-28 11:47:31] [error] Commons Daemon procrun failed with exit value: 5 (Failed to start service) [2012-12-28 11:47:31] [error] The service did not respond to the start or control request in a timely fashion. *** After checking the code change, it is found that the problem was caused by the change in revision 1412017 (DAEMON-261: Allow services names with spaces). Problem solved by using 1.0.11 source code with the above change reverted, and compiled under Windows XP 32-bit with VC6 SP6 and Platform SDK for Windows Server 2003 R2. ### The //RS option still runs the service well. ### Without reverting the source code but just recompiled it with Visual C++ 2010 and installed was: When using latest version (1.0.11) of prunsrv.exe, the service failed to start with the following error: *** [2012-12-28 11:47:31] [error] Commons Daemon procrun failed with exit value: 5 (Failed to start service) [2012-12-28 11:47:31] [error] The service did not respond to the start or control request in a timely fashion. *** After checking the code change, it is found that the problem was caused by the change in revision 1412017 (DAEMON-261: Allow services names with spaces). Problem solved by using 1.0.11 source code with the above change reverted, and compiled under Windows XP 32-bit with VC6 SP6 and Platform SDK for Windows Server 2003 R2. > Fail to start service in 32-bit Windows > --------------------------------------- > > Key: DAEMON-273 > URL: https://issues.apache.org/jira/browse/DAEMON-273 > Project: Commons Daemon > Issue Type: Bug > Components: Procrun > Affects Versions: 1.0.11 > Environment: 32-bit Windows > Reporter: Wallace > > When using latest version (1.0.11) of prunsrv.exe, the service failed to start (//ES) with the following error: > *** > [2012-12-28 11:47:31] [error] Commons Daemon procrun failed with exit value: 5 (Failed to start service) > [2012-12-28 11:47:31] [error] The service did not respond to the start or control request in a timely fashion. > *** > After checking the code change, it is found that the problem was caused by the change in revision 1412017 (DAEMON-261: Allow services names with spaces). > Problem solved by using 1.0.11 source code with the above change reverted, and compiled under Windows XP 32-bit with VC6 SP6 and Platform SDK for Windows Server 2003 R2. > ### > The //RS option still runs the service well. > ### > Without reverting the source code but just recompiled it with Visual C++ 2010 and installed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira