Re: Tomcat 7 doesn't start on Windows
On Feb 28, 2013, at 3:46 AM, Stadelmann Josef wrote: Where does CATALINA_HOME point to? Josef Rune reported yesterday that he solved the problem by resetting the registry values. There was some strange garbage in one of the registry values. I'd love to know how it got there, but we probably never will. N -Ursprüngliche Nachricht- Von: André Warnier [mailto:a...@ice-sa.com] Gesendet: Mittwoch, 27. Februar 2013 13:38 An: Tomcat Users List Betreff: Re: Tomcat 7 doesn't start on Windows Giles wrote: On 27 February 2013 11:52, André Warnier a...@ice-sa.com wrote: computer repair centre wrote: On Wed, Feb 27, 2013 at 10:18 AM, Rune Stilling s...@rdfined.dk wrote: Hi again Thanks for your answers. I have given up. I have tried some of the suggestions: * Uninstall all JVM's and Tomcats (and reinstall) * Checked dependcies, yes there were two, that are also present on another machine running Tomcat7 (TCP/IP, ADF) * Tried to use client/jvm.dll instead of server/jvm.dll Nothing helps - I can still only run the service from the command prompt. I find it strange though, that Tomcat isn't able to log anything at all about this, but maybe it's all Windows fault? Hopefully things will work on a new VPS, and I'll quit the old one. /Rune Den 26/02/2013 kl. 13.04 skrev Rune Stilling s...@rdfined.dk: --- -- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Hi Rune, Please can you provide the value of the JAVA_HOME environment variable? That has nothing to do with the matter. The wrapper (tomcat7.exe) takes the path of the JVM to run from the Registry, not from environment variables. Run tomcat7w.exe and check the Java tab. But it is used by service.bat when installing the service. This issue could be caused by using the 64-bit installation with the 32-bit JVM. This would explain why calling the wrapper directly from the command line does execute successfully. I believe that the above statement is false. Whether you run the command tomcat7 //TS/Tomcat7 from a command-line window, or you let the Windows Service Manager run the same command, does not change the fact that tomcat7(.exe) takes its parameters from the same place in the Registry. So if it works one way, and not the other, it is not because of that Registry setting nor bacause the JAVA_HOME environment variable. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org smime.p7s Description: S/MIME cryptographic signature
Re: Tomcat 7 doesn't start on Windows
On 28/02/2013 07:38, Nick Williams wrote: On Feb 28, 2013, at 3:46 AM, Stadelmann Josef wrote: Where does CATALINA_HOME point to? Josef Rune reported yesterday that he solved the problem by resetting the registry values. There was some strange garbage in one of the registry values. I'd love to know how it got there, but we probably never will. Maybe this: https://issues.apache.org/bugzilla/show_bug.cgi?id=54609 Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
On Feb 28, 2013, at 9:40 AM, Mark Thomas wrote: On 28/02/2013 07:38, Nick Williams wrote: On Feb 28, 2013, at 3:46 AM, Stadelmann Josef wrote: Where does CATALINA_HOME point to? Josef Rune reported yesterday that he solved the problem by resetting the registry values. There was some strange garbage in one of the registry values. I'd love to know how it got there, but we probably never will. Maybe this: https://issues.apache.org/bugzilla/show_bug.cgi?id=54609 I stand corrected. That's probably it. Rune reported using 7.0.37, just like in the bug report, and his registry path looked like this: C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\Tomcat7.exe ogs\commons-daemon.2013-02-27.log//RS//Tomcat7 So, yea. That bug appears to be his issue. That is bizarre. I will be following this bug to see what in the world caused it. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org smime.p7s Description: S/MIME cryptographic signature
Re: Tomcat 7 doesn't start on Windows
On Thu, Feb 28, 2013 at 10:46 AM, Nick Williams nicho...@nicholaswilliams.net wrote: On Feb 28, 2013, at 9:40 AM, Mark Thomas wrote: Maybe this: https://issues.apache.org/bugzilla/show_bug.cgi?id=54609 I stand corrected. That's probably it. Rune reported using 7.0.37, just like in the bug report, and his registry path looked like this: C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\Tomcat7.exe ogs\commons-daemon.2013-02-27.log//RS//Tomcat7 So, yea. That bug appears to be his issue. That is bizarre. I will be following this bug to see what in the world caused it. I just searched google for: windows registry tomcat ogs\commons and I saw the following (and more): Chapter 4 Using Object Grouping Services [1] [1] http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.2/north_bound_api/developers/guide/ogs.html
RE: Tomcat 7 doesn't start on Windows
From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] Subject: Re: Tomcat 7 doesn't start on Windows I just searched google for: windows registry tomcat ogs\commons and I saw the following (and more): Chapter 4 Using Object Grouping Services [1] [1] http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.2/ north_bound_api/developers/guide/ogs.html I'll bite; what does this have to do with the topic under discussion? The ogs in the Windows registry is most likely logs with the front end chopped off; certainly nothing to do with a completely separate Cisco box. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
On Thu, Feb 28, 2013 at 11:14 AM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] Subject: Re: Tomcat 7 doesn't start on Windows I just searched google for: windows registry tomcat ogs\commons and I saw the following (and more): Chapter 4 Using Object Grouping Services [1] [1] http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.2/ north_bound_api/developers/guide/ogs.html I'll bite; what does this have to do with the topic under discussion? The ogs in the Windows registry is most likely logs with the front end chopped off; certainly nothing to do with a completely separate Cisco box. Good point and I stand corrected. Thanks! - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
Howard W. Smith, Jr. wrote: On Thu, Feb 28, 2013 at 10:46 AM, Nick Williams nicho...@nicholaswilliams.net wrote: On Feb 28, 2013, at 9:40 AM, Mark Thomas wrote: Maybe this: https://issues.apache.org/bugzilla/show_bug.cgi?id=54609 I stand corrected. That's probably it. Rune reported using 7.0.37, just like in the bug report, and his registry path looked like this: C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\Tomcat7.exe ogs\commons-daemon.2013-02-27.log//RS//Tomcat7 So, yea. That bug appears to be his issue. That is bizarre. I will be following this bug to see what in the world caused it. I just searched google for: windows registry tomcat ogs\commons and I saw the following (and more): Chapter 4 Using Object Grouping Services [1] [1] http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.2/north_bound_api/developers/guide/ogs.html Now I'm even more curious. WTH does this have to do with it ? I admit that the fact that Cisco apparently uses Tomcat, and that there happens to be a piece of common string somewhere, is troubling. But that looks like a red herring in this case, no ? Probably just an l missing in front of ogs\commons-daemon, no ? And commons-daemon.2013-02-27.log (the date of this installation) suspiciously looks like something generated by procrun itself, no ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
On Thu, Feb 28, 2013 at 12:01 PM, André Warnier a...@ice-sa.com wrote: Howard W. Smith, Jr. wrote: On Thu, Feb 28, 2013 at 10:46 AM, Nick Williams nicho...@nicholaswilliams.net wrote: On Feb 28, 2013, at 9:40 AM, Mark Thomas wrote: Maybe this: https://issues.apache.org/**bugzilla/show_bug.cgi?id=54609https://issues.apache.org/bugzilla/show_bug.cgi?id=54609 I stand corrected. That's probably it. Rune reported using 7.0.37, just like in the bug report, and his registry path looked like this: C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\Tomcat7.exe ogs\commons-daemon.2013-02-27.**log//RS//Tomcat7 So, yea. That bug appears to be his issue. That is bizarre. I will be following this bug to see what in the world caused it. I just searched google for: windows registry tomcat ogs\commons and I saw the following (and more): Chapter 4 Using Object Grouping Services [1] [1] http://www.cisco.com/en/US/**docs/net_mgmt/ciscoworks_** common_services_software/3.2/**north_bound_api/developers/** guide/ogs.htmlhttp://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.2/north_bound_api/developers/guide/ogs.html Now I'm even more curious. WTH does this have to do with it ? I admit that the fact that Cisco apparently uses Tomcat, and that there happens to be a piece of common string somewhere, is troubling. But that looks like a red herring in this case, no ? Probably just an l missing in front of ogs\commons-daemon, no ? And commons-daemon.2013-02-27.**log (the date of this installation) suspiciously looks like something generated by procrun itself, no ? All good questions. Thanks for the response/clarification. Definitely, my bad. :) --**--**- To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.orgusers-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
Hi again Thanks for your answers. I have given up. I have tried some of the suggestions: * Uninstall all JVM's and Tomcats (and reinstall) * Checked dependcies, yes there were two, that are also present on another machine running Tomcat7 (TCP/IP, ADF) * Tried to use client/jvm.dll instead of server/jvm.dll Nothing helps - I can still only run the service from the command prompt. I find it strange though, that Tomcat isn't able to log anything at all about this, but maybe it's all Windows fault? Hopefully things will work on a new VPS, and I'll quit the old one. /Rune Den 26/02/2013 kl. 13.04 skrev Rune Stilling s...@rdfined.dk: Hi list I have been trying to get this to work by looking a lot on similar situations around the net but nothing works. My setup is as follows: * Tomcat 7.0.37 installed via the Windows service installer package * Windows 2003 server * Java/JRE 1.7.0_15 * Using C:\Program Files\Java\jre7\bin\server\jvm.dll So the problem is that the Tomcat7 service won't start from the service control panel. I just get a Could not start … and Error 1053: The service did not respond …. There's nothing in the Tomcat logs (both stdout and stderr are empty). The event logs shows a generic service control manager error. But - If I start the service from the command line by typing tomcat7 //TS/Tomcat7 the thing works fine. Also if I change the service user account to the Administrator account I get a different error by startup Error 1068: The dependency service or group failed to start. Any ideas? /Rune - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
On Wed, Feb 27, 2013 at 6:37 AM, computer repair centre computer.support.cen...@googlemail.com wrote: Please can you provide the value of the JAVA_HOME environment variable? Excellent question. That question has been wondering in my mind since yesterday, since Rune stated following in 2 separate emails: * Using C:\Program Files\Java\jre7\bin\server\jvm.dll * Tried to use client/jvm.dll instead of server/jvm.dll Also, might check PATH. I really hope 'multiple' JVMs are not included in the Windows system PATH as well. It is very common for Windows users to just append 'stuff' on to Windows system PATH variable, and may forget to update/remove obsolete 'stuff' from the PATH variable. When I update to latest Java 7 version, it is always standard procedure for me to make sure I update JAVA_HOME and PATH.
Re: Tomcat 7 doesn't start on Windows
computer repair centre wrote: On Wed, Feb 27, 2013 at 10:18 AM, Rune Stilling s...@rdfined.dk wrote: Hi again Thanks for your answers. I have given up. I have tried some of the suggestions: * Uninstall all JVM's and Tomcats (and reinstall) * Checked dependcies, yes there were two, that are also present on another machine running Tomcat7 (TCP/IP, ADF) * Tried to use client/jvm.dll instead of server/jvm.dll Nothing helps - I can still only run the service from the command prompt. I find it strange though, that Tomcat isn't able to log anything at all about this, but maybe it's all Windows fault? Hopefully things will work on a new VPS, and I'll quit the old one. /Rune Den 26/02/2013 kl. 13.04 skrev Rune Stilling s...@rdfined.dk: - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Hi Rune, Please can you provide the value of the JAVA_HOME environment variable? That has nothing to do with the matter. The wrapper (tomcat7.exe) takes the path of the JVM to run from the Registry, not from environment variables. Run tomcat7w.exe and check the Java tab. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
On 27 February 2013 11:52, André Warnier a...@ice-sa.com wrote: computer repair centre wrote: On Wed, Feb 27, 2013 at 10:18 AM, Rune Stilling s...@rdfined.dk wrote: Hi again Thanks for your answers. I have given up. I have tried some of the suggestions: * Uninstall all JVM's and Tomcats (and reinstall) * Checked dependcies, yes there were two, that are also present on another machine running Tomcat7 (TCP/IP, ADF) * Tried to use client/jvm.dll instead of server/jvm.dll Nothing helps - I can still only run the service from the command prompt. I find it strange though, that Tomcat isn't able to log anything at all about this, but maybe it's all Windows fault? Hopefully things will work on a new VPS, and I'll quit the old one. /Rune Den 26/02/2013 kl. 13.04 skrev Rune Stilling s...@rdfined.dk: - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Hi Rune, Please can you provide the value of the JAVA_HOME environment variable? That has nothing to do with the matter. The wrapper (tomcat7.exe) takes the path of the JVM to run from the Registry, not from environment variables. Run tomcat7w.exe and check the Java tab. But it is used by service.bat when installing the service. This issue could be caused by using the 64-bit installation with the 32-bit JVM. This would explain why calling the wrapper directly from the command line does execute successfully. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
Ok - So I did: * uninstall Tomcat * only one jvm present on the system (64 bit) * setting CATALINA_HOME, JAVA_HOME and JRE_HOME: CATALINA_HOME=C:\Progra~1\APACHE~1\TOMCAT~1.0 JAVA_HOME=C:\Progra~1\Java JRE_HOME=C:\Progra~1\Java\jre7 * restarting server * reinstalling Tomcat7 (using the service installer, not the service.bat file, that I can't locate anyway) * checking Java Virtual Machine in Java tab in Tomcat7w.exe: C:\Program Files\Java\jre7\bin\server\jvm.dll * checking PATH: Path=C:\PARALL~1\Plesk\ADDITI~1\Perl\bin\;C:\Parallels\Plesk\Additional\Python\;C:\Parallels\Plesk\Mail Servers\Mail Enable\BIN;C:\PARALL~1\Plesk\ADDITI~1\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\MySQL\MySQL Server5.5\bin;C:\Program Files(x86)\IDM Computer Solutions\UltraEdit\ But - Problem persists. Is there some registry key I could check related to the installation process? \Rune Den 27/02/2013 kl. 12.57 skrev Giles computer.support.cen...@googlemail.com: On 27 February 2013 11:52, André Warnier a...@ice-sa.com wrote: computer repair centre wrote: On Wed, Feb 27, 2013 at 10:18 AM, Rune Stilling s...@rdfined.dk wrote: Hi again Thanks for your answers. I have given up. I have tried some of the suggestions: * Uninstall all JVM's and Tomcats (and reinstall) * Checked dependcies, yes there were two, that are also present on another machine running Tomcat7 (TCP/IP, ADF) * Tried to use client/jvm.dll instead of server/jvm.dll Nothing helps - I can still only run the service from the command prompt. I find it strange though, that Tomcat isn't able to log anything at all about this, but maybe it's all Windows fault? Hopefully things will work on a new VPS, and I'll quit the old one. /Rune Den 26/02/2013 kl. 13.04 skrev Rune Stilling s...@rdfined.dk: - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Hi Rune, Please can you provide the value of the JAVA_HOME environment variable? That has nothing to do with the matter. The wrapper (tomcat7.exe) takes the path of the JVM to run from the Registry, not from environment variables. Run tomcat7w.exe and check the Java tab. But it is used by service.bat when installing the service. This issue could be caused by using the 64-bit installation with the 32-bit JVM. This would explain why calling the wrapper directly from the command line does execute successfully. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
On Wed, Feb 27, 2013 at 7:11 AM, Rune Stilling s...@rdfined.dk wrote: Ok - So I did: CATALINA_HOME=C:\Progra~1\APACHE~1\TOMCAT~1.0 * reinstalling Tomcat7 (using the service installer, not the service.bat file, that I can't locate anyway) * checking Java Virtual Machine in Java tab in Tomcat7w.exe: TOMCAT~1.0 ? interesting, never seen a tomcat7 install to folder like that. See [1] below. using the service installer = 'sc ...' at command prompt? you cannot locate service.bat file (in C:\Progra~1\APACHE~1\TOMCAT~1.0)? wow/interesting. I repeat, see [1] below. [1] I download .zip file and extract to D:\ root folder, and it should extract files to D:\apache-tomcat-7.0.37 (or whatever version you are using). I would 'never' install Tomcat to C:\Program Files or D:\Program Files.
Re: Tomcat 7 doesn't start on Windows
Giles wrote: On 27 February 2013 11:52, André Warnier a...@ice-sa.com wrote: computer repair centre wrote: On Wed, Feb 27, 2013 at 10:18 AM, Rune Stilling s...@rdfined.dk wrote: Hi again Thanks for your answers. I have given up. I have tried some of the suggestions: * Uninstall all JVM's and Tomcats (and reinstall) * Checked dependcies, yes there were two, that are also present on another machine running Tomcat7 (TCP/IP, ADF) * Tried to use client/jvm.dll instead of server/jvm.dll Nothing helps - I can still only run the service from the command prompt. I find it strange though, that Tomcat isn't able to log anything at all about this, but maybe it's all Windows fault? Hopefully things will work on a new VPS, and I'll quit the old one. /Rune Den 26/02/2013 kl. 13.04 skrev Rune Stilling s...@rdfined.dk: - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Hi Rune, Please can you provide the value of the JAVA_HOME environment variable? That has nothing to do with the matter. The wrapper (tomcat7.exe) takes the path of the JVM to run from the Registry, not from environment variables. Run tomcat7w.exe and check the Java tab. But it is used by service.bat when installing the service. This issue could be caused by using the 64-bit installation with the 32-bit JVM. This would explain why calling the wrapper directly from the command line does execute successfully. I believe that the above statement is false. Whether you run the command tomcat7 //TS/Tomcat7 from a command-line window, or you let the Windows Service Manager run the same command, does not change the fact that tomcat7(.exe) takes its parameters from the same place in the Registry. So if it works one way, and not the other, it is not because of that Registry setting nor bacause the JAVA_HOME environment variable. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
On Wed, Feb 27, 2013 at 7:34 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: On Wed, Feb 27, 2013 at 7:11 AM, Rune Stilling s...@rdfined.dk wrote: Ok - So I did: CATALINA_HOME=C:\Progra~1\APACHE~1\TOMCAT~1.0 * reinstalling Tomcat7 (using the service installer, not the service.bat file, that I can't locate anyway) * checking Java Virtual Machine in Java tab in Tomcat7w.exe: TOMCAT~1.0 ? interesting, never seen a tomcat7 install to folder like that. See [1] below. using the service installer = 'sc ...' at command prompt? you cannot locate service.bat file (in C:\Progra~1\APACHE~1\TOMCAT~1.0)? wow/interesting. I repeat, see [1] below. [1] I download .zip file and extract to D:\ root folder, and it should extract files to D:\apache-tomcat-7.0.37 (or whatever version you are using). I would 'never' install Tomcat to C:\Program Files or D:\Program Files. Add to [1] above... service.bat is located in D:\apache-tomcat-7.0.37\bin, after extracting 'all' files from the .zip file, and if 'Use folder names' was checked/selected prior to extracting files via WinZip.
Re: Tomcat 7 doesn't start on Windows
As I wrote I'm using the service installer 32-bit/64-bit Windows Service Installer. This is an exe file and not a zip-archive. Regarding the paths - I have used windows short paths to avoid eventual troubles with spaces in path names. \Rune Den 27/02/2013 kl. 13.54 skrev Howard W. Smith, Jr. smithh032...@gmail.com: On Wed, Feb 27, 2013 at 7:34 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: On Wed, Feb 27, 2013 at 7:11 AM, Rune Stilling s...@rdfined.dk wrote: Ok - So I did: CATALINA_HOME=C:\Progra~1\APACHE~1\TOMCAT~1.0 * reinstalling Tomcat7 (using the service installer, not the service.bat file, that I can't locate anyway) * checking Java Virtual Machine in Java tab in Tomcat7w.exe: TOMCAT~1.0 ? interesting, never seen a tomcat7 install to folder like that. See [1] below. using the service installer = 'sc ...' at command prompt? you cannot locate service.bat file (in C:\Progra~1\APACHE~1\TOMCAT~1.0)? wow/interesting. I repeat, see [1] below. [1] I download .zip file and extract to D:\ root folder, and it should extract files to D:\apache-tomcat-7.0.37 (or whatever version you are using). I would 'never' install Tomcat to C:\Program Files or D:\Program Files. Add to [1] above... service.bat is located in D:\apache-tomcat-7.0.37\bin, after extracting 'all' files from the .zip file, and if 'Use folder names' was checked/selected prior to extracting files via WinZip. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
And BTW - I have several running Tomcat7-instances on other servers that run in Program Files-folders. \Rune Den 27/02/2013 kl. 13.54 skrev Howard W. Smith, Jr. smithh032...@gmail.com: On Wed, Feb 27, 2013 at 7:34 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: On Wed, Feb 27, 2013 at 7:11 AM, Rune Stilling s...@rdfined.dk wrote: Ok - So I did: CATALINA_HOME=C:\Progra~1\APACHE~1\TOMCAT~1.0 * reinstalling Tomcat7 (using the service installer, not the service.bat file, that I can't locate anyway) * checking Java Virtual Machine in Java tab in Tomcat7w.exe: TOMCAT~1.0 ? interesting, never seen a tomcat7 install to folder like that. See [1] below. using the service installer = 'sc ...' at command prompt? you cannot locate service.bat file (in C:\Progra~1\APACHE~1\TOMCAT~1.0)? wow/interesting. I repeat, see [1] below. [1] I download .zip file and extract to D:\ root folder, and it should extract files to D:\apache-tomcat-7.0.37 (or whatever version you are using). I would 'never' install Tomcat to C:\Program Files or D:\Program Files. Add to [1] above... service.bat is located in D:\apache-tomcat-7.0.37\bin, after extracting 'all' files from the .zip file, and if 'Use folder names' was checked/selected prior to extracting files via WinZip. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
As I wrote I'm using the service installer 32-bit/64-bit Windows Service Installer. This is an exe file and not a zip-archive. Regarding the paths - I have used windows short paths to avoid eventual troubles with spaces in path names. And BTW - I have several running Tomcat7-instances on other servers that run in Program Files-folders. Understood all 3 points and with that, I digress. I already shared what works best (and is reliable) for me. :)
Re: Tomcat 7 doesn't start on Windows
Rune Stilling wrote: Is there some registry key I could check related to the installation process? Call up the Registry Editor, and search for tomcat7. You should find essentially 2 places : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7 (under this one, you will find the parameters which Windows needs to know about the service (such as, how to start it) (it being tomcat7.exe) HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\ (under this one, you will find the parameters which tomcat7.exe (the service wrapper) needs to know (such as, which JVM to start and with which parameters) (and remember, tomcat7.exe is a renamed prunsrv.exe, which is one of the 2 modules that are part of procrun). -- Let's step back a bit. 1) you install Tomcat on the machine, using the Windows installer package from tomcat.apache.org. 2) this installer creates the Registry value : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\ImagePath = C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7 (or similar) This Registry value is the one that will be used by the Windows Service Manager, to know which program to launch when you click on Services.. Tomcat7...start. 3) when you login as a user onto the machine, open a command window, and run the above command (C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7), the tomcat7.exe program runs, and starts a JVM which starts Tomcat, as a Service. And that works fine, tomcat logs are produced etc. 4) when instead, you open the Windows Service Manager dialog, and ask Windows to start the Tomcat service, nothing happens. (Tomcat does not start, tomcat7.exe does not run, no logs are produced etc.) So the intuitive conclusions would be : - there is nothing wrong with Tomcat per se. Otherwise, it would not run, no matter how it is started. There is also nothing wrong with the JVM, for the same reasons. - there is nothing wrong with the Registry parameters of tomcat7.exe (the ones found under HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation). Otherwise, in case (3) above, tomcat7.exe would not be able to start the JVM etc.. So there must be something wrong with the parameters used by the Windows Service Manager when it tries to start the Tomcat service. (The ones under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\) What that would be, I couldn't say, and certainly not without access to your Registry. But what I would do at this stage is this : 1) de-install Tomcat again (do not delete the installer.exe file that you downloaded, you'll need it again) 2) using the Registry Editor (carefully), go to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\, and delete it (and everything under it). 3) reboot Windows, and with the Registry Editor, verify that the key is still deleted (I am saying that because who knows what MS will have invented yet to re-instate things that you deleted..) 4) re-install the Tomcat service by re-running the installer 5) try again to start Tomcat and tell us what happens. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
Hi André Thanks for an excellent summary. There's one thing that I haven't been precise enough about I can see. I CANNOT run Tomcat via the RS-parameter: Tomcat7.exe //RS/Tomcat7 If I try the log produces the following: [2013-02-27 14:33:55] [info] [548184] Commons Daemon procrun (1.0.13.0 64-bit) started [2013-02-27 14:33:55] [info] [548184] Running 'Tomcat7' Service... [2013-02-27 14:33:55] [error] [548184] StartServiceCtrlDispatcher for 'Tomcat7' failed [2013-02-27 14:33:55] [error] [548184] The service process could not connect to the service controller. [2013-02-27 14:33:55] [error] [548184] Commons Daemon procrun failed with exit value: 4 (Failed to run service) [2013-02-27 14:33:55] [error] [548184] The service process could not connect to the service controller. What I CAN do is to run it via the TS-parameter: Tomcat7.exe //TS/Tomcat7 But - I'll try what you suggested anyways. /Rune Den 27/02/2013 kl. 14.20 skrev André Warnier a...@ice-sa.com: Rune Stilling wrote: Is there some registry key I could check related to the installation process? Call up the Registry Editor, and search for tomcat7. You should find essentially 2 places : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7 (under this one, you will find the parameters which Windows needs to know about the service (such as, how to start it) (it being tomcat7.exe) HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\ (under this one, you will find the parameters which tomcat7.exe (the service wrapper) needs to know (such as, which JVM to start and with which parameters) (and remember, tomcat7.exe is a renamed prunsrv.exe, which is one of the 2 modules that are part of procrun). -- Let's step back a bit. 1) you install Tomcat on the machine, using the Windows installer package from tomcat.apache.org. 2) this installer creates the Registry value : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\ImagePath = C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7 (or similar) This Registry value is the one that will be used by the Windows Service Manager, to know which program to launch when you click on Services.. Tomcat7...start. 3) when you login as a user onto the machine, open a command window, and run the above command (C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7), the tomcat7.exe program runs, and starts a JVM which starts Tomcat, as a Service. And that works fine, tomcat logs are produced etc. 4) when instead, you open the Windows Service Manager dialog, and ask Windows to start the Tomcat service, nothing happens. (Tomcat does not start, tomcat7.exe does not run, no logs are produced etc.) So the intuitive conclusions would be : - there is nothing wrong with Tomcat per se. Otherwise, it would not run, no matter how it is started. There is also nothing wrong with the JVM, for the same reasons. - there is nothing wrong with the Registry parameters of tomcat7.exe (the ones found under HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation). Otherwise, in case (3) above, tomcat7.exe would not be able to start the JVM etc.. So there must be something wrong with the parameters used by the Windows Service Manager when it tries to start the Tomcat service. (The ones under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\) What that would be, I couldn't say, and certainly not without access to your Registry. But what I would do at this stage is this : 1) de-install Tomcat again (do not delete the installer.exe file that you downloaded, you'll need it again) 2) using the Registry Editor (carefully), go to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\, and delete it (and everything under it). 3) reboot Windows, and with the Registry Editor, verify that the key is still deleted (I am saying that because who knows what MS will have invented yet to re-instate things that you deleted..) 4) re-install the Tomcat service by re-running the installer 5) try again to start Tomcat and tell us what happens. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 7 doesn't start on Windows
-Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Wednesday, February 27, 2013 8:20 AM To: Tomcat Users List Subject: Re: Tomcat 7 doesn't start on Windows Rune Stilling wrote: Is there some registry key I could check related to the installation process? Call up the Registry Editor, and search for tomcat7. You should find essentially 2 places : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7 (under this one, you will find the parameters which Windows needs to know about the service (such as, how to start it) (it being tomcat7.exe) HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\ (under this one, you will find the parameters which tomcat7.exe (the service wrapper) needs to know (such as, which JVM to start and with which parameters) (and remember, tomcat7.exe is a renamed prunsrv.exe, which is one of the 2 modules that are part of procrun). -- Let's step back a bit. 1) you install Tomcat on the machine, using the Windows installer package from tomcat.apache.org. 2) this installer creates the Registry value : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\ImagePath = C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7 (or similar) This Registry value is the one that will be used by the Windows Service Manager, to know which program to launch when you click on Services.. Tomcat7...start. 3) when you login as a user onto the machine, open a command window, and run the above command (C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7), the tomcat7.exe program runs, and starts a JVM which starts Tomcat, as a Service. And that works fine, tomcat logs are produced etc. 4) when instead, you open the Windows Service Manager dialog, and ask Windows to start the Tomcat service, nothing happens. (Tomcat does not start, tomcat7.exe does not run, no logs are produced etc.) So the intuitive conclusions would be : - there is nothing wrong with Tomcat per se. Otherwise, it would not run, no matter how it is started. There is also nothing wrong with the JVM, for the same reasons. - there is nothing wrong with the Registry parameters of tomcat7.exe (the ones found under HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation). Otherwise, in case (3) above, tomcat7.exe would not be able to start the JVM etc.. So there must be something wrong with the parameters used by the Windows Service Manager when it tries to start the Tomcat service. (The ones under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\) What that would be, I couldn't say, and certainly not without access to your Registry. But what I would do at this stage is this : 1) de-install Tomcat again (do not delete the installer.exe file that you downloaded, you'll need it again) 2) using the Registry Editor (carefully), go to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\, and delete it (and everything under it). 3) reboot Windows, and with the Registry Editor, verify that the key is still deleted (I am saying that because who knows what MS will have invented yet to re-instate things that you deleted..) 4) re-install the Tomcat service by re-running the installer 5) try again to start Tomcat and tell us what happens. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org You might also want to download process monitor (not process explorer) from live.sysinternals.com, and have that running when you try and start the service. Filter out unrelated processes (explorer, iexplorer, csrss, etc.) and look for results that are not success (although if you actually filter on result is not success, you will probably see some false indicators, for example, Windows looks in the local directory and the Path for system DLLs, and will report a failure finding them until it does find them in the %windir%\system32 folder). Generally, the fatal errors occur towards the end of the run history of the applicable process. Have you looked in Event Viewer for any additional error messages in the System or Application logs? Increased Tomcat logging to try and identify the source of the problem? I know you have used the command line, but if you start the Tomcat monitor (tomcatw.exe) and start the service from the monitor in the system tray, does that work? Finally, do you have any unusual restrictions on your server? Are any other services failing to start? Based on your last posting, I would guess that it is a permissions issue. Does the system account have full permissions on the Tomcat directory? This e-mail and any attachments are intended only for the use of the addressee(s) named herein and may contain proprietary information. If you are not the intended recipient of this e-mail or believe that you received
Re: Tomcat 7 doesn't start on Windows
Problem solved!! Ah finally :) I did as you suggested below and it didn't help, but then I looked a bit on the registry values. I found that the ImagePath key looked a bit strange. It contained the following value: C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\Tomcat7.exe ogs\commons-daemon.2013-02-27.log//RS//Tomcat7 I tried to replace it with: C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin\Tomcat7.exe //RS//Tomcat7 And voliá the service would start. I have no idea where the ogs\commons-daemon.2013-02-27.log comes from, but it must be something the installer added, and for some reason the service won't start using this value? Thanks for all the help, Rune Den 27/02/2013 kl. 14.20 skrev André Warnier a...@ice-sa.com: Rune Stilling wrote: Is there some registry key I could check related to the installation process? Call up the Registry Editor, and search for tomcat7. You should find essentially 2 places : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7 (under this one, you will find the parameters which Windows needs to know about the service (such as, how to start it) (it being tomcat7.exe) HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\ (under this one, you will find the parameters which tomcat7.exe (the service wrapper) needs to know (such as, which JVM to start and with which parameters) (and remember, tomcat7.exe is a renamed prunsrv.exe, which is one of the 2 modules that are part of procrun). -- Let's step back a bit. 1) you install Tomcat on the machine, using the Windows installer package from tomcat.apache.org. 2) this installer creates the Registry value : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\ImagePath = C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7 (or similar) This Registry value is the one that will be used by the Windows Service Manager, to know which program to launch when you click on Services.. Tomcat7...start. 3) when you login as a user onto the machine, open a command window, and run the above command (C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7), the tomcat7.exe program runs, and starts a JVM which starts Tomcat, as a Service. And that works fine, tomcat logs are produced etc. 4) when instead, you open the Windows Service Manager dialog, and ask Windows to start the Tomcat service, nothing happens. (Tomcat does not start, tomcat7.exe does not run, no logs are produced etc.) So the intuitive conclusions would be : - there is nothing wrong with Tomcat per se. Otherwise, it would not run, no matter how it is started. There is also nothing wrong with the JVM, for the same reasons. - there is nothing wrong with the Registry parameters of tomcat7.exe (the ones found under HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation). Otherwise, in case (3) above, tomcat7.exe would not be able to start the JVM etc.. So there must be something wrong with the parameters used by the Windows Service Manager when it tries to start the Tomcat service. (The ones under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\) What that would be, I couldn't say, and certainly not without access to your Registry. But what I would do at this stage is this : 1) de-install Tomcat again (do not delete the installer.exe file that you downloaded, you'll need it again) 2) using the Registry Editor (carefully), go to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\, and delete it (and everything under it). 3) reboot Windows, and with the Registry Editor, verify that the key is still deleted (I am saying that because who knows what MS will have invented yet to re-instate things that you deleted..) 4) re-install the Tomcat service by re-running the installer 5) try again to start Tomcat and tell us what happens. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
On Feb 27, 2013, at 7:36 AM, Rune Stilling wrote: Hi André Thanks for an excellent summary. There's one thing that I haven't been precise enough about I can see. I CANNOT run Tomcat via the RS-parameter: Tomcat7.exe //RS/Tomcat7 If I try the log produces the following: [2013-02-27 14:33:55] [info] [548184] Commons Daemon procrun (1.0.13.0 64-bit) started [2013-02-27 14:33:55] [info] [548184] Running 'Tomcat7' Service... [2013-02-27 14:33:55] [error] [548184] StartServiceCtrlDispatcher for 'Tomcat7' failed [2013-02-27 14:33:55] [error] [548184] The service process could not connect to the service controller. [2013-02-27 14:33:55] [error] [548184] Commons Daemon procrun failed with exit value: 4 (Failed to run service) [2013-02-27 14:33:55] [error] [548184] The service process could not connect to the service controller. This is expected. Per Microsoft's website [1] you cannot run services interactively from the command line. (You can start them from the command line, i.e. with `sc start`, but you cannot run them from the command line, i.e. with `Tomcat7.exe //RS/Tomcat7`.) This is why from the command line it works with `Tomcat7.exe //TS/Tomcat7` ... that command tells Tomcat to not attempt to connect to the service controller. The service process could not connect to the service controller in this case is unrelated to the fact that you can't start the Tomcat service from the service controller. If you got this message when you tried to start the Tomcat service normally, then I would be worried. One thing I would point out is that your JAVA_HOME environmental variable is not correct. This should NOT affect Tomcat when it is running as a service, as far as I know. JAVA_HOME should be the home directory of a JDK (e.g., C:\Program Files\Java\jdk7) and JRE_HOME should be the home directory of a JRE (e.g., C:\Program Files\Java\jre7). Your JRE_HOME is correct, but your JAVA_HOME is C:\Program Files\Java. Again, this doesn't matter when Tomcat is run as a service. Also, Tomcat only NEEDS a JRE_HOME (and only when running not as as service), it does not NEED a JAVA_HOME. But if you have a JAVA_HOME, it should be correct. I've encountered and solved hundreds of Tomcat-as-a-Windows-Service problems before, but I have never seen Tomcat not log anything. If you don't mind, could you run Tomcat7w.exe, screenshot each tab (Alt + Print Screen gets a screenshot for just the window instead of the whole thing), put the screenshots online somewhere public, and then post links to the screenshots here? My money is on finding something amiss there. Question: When you run the service installer, it installs Tomcat at C:\Program Files\Apache Software Foundation\Tomcat 7.0, correct? (Unless, of course, you changed it at install time.) Question: I know at some point you said this, but I can't find the email anymore. Can you remind me what version of Windows you are running on? [1] http://msdn.microsoft.com/en-us/library/ms686324(VS.85).aspx What I CAN do is to run it via the TS-parameter: Tomcat7.exe //TS/Tomcat7 But - I'll try what you suggested anyways. /Rune Den 27/02/2013 kl. 14.20 skrev André Warnier a...@ice-sa.com: Rune Stilling wrote: Is there some registry key I could check related to the installation process? Call up the Registry Editor, and search for tomcat7. You should find essentially 2 places : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7 (under this one, you will find the parameters which Windows needs to know about the service (such as, how to start it) (it being tomcat7.exe) HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\ (under this one, you will find the parameters which tomcat7.exe (the service wrapper) needs to know (such as, which JVM to start and with which parameters) (and remember, tomcat7.exe is a renamed prunsrv.exe, which is one of the 2 modules that are part of procrun). -- Let's step back a bit. 1) you install Tomcat on the machine, using the Windows installer package from tomcat.apache.org. 2) this installer creates the Registry value : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat7\ImagePath = C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7 (or similar) This Registry value is the one that will be used by the Windows Service Manager, to know which program to launch when you click on Services.. Tomcat7...start. 3) when you login as a user onto the machine, open a command window, and run the above command (C:\apache-tomcat-\bin\tomcat7.exe //RS//Tomcat7), the tomcat7.exe program runs, and starts a JVM which starts Tomcat, as a Service. And that works fine, tomcat logs are produced etc. 4) when instead, you open the Windows Service Manager dialog, and ask Windows to start the Tomcat service, nothing happens. (Tomcat does not start, tomcat7.exe does not run, no logs are produced etc.) So
RE: Tomcat 7 doesn't start on Windows
From: Rune Stilling [mailto:s...@rdfined.dk] Subject: Re: Tomcat 7 doesn't start on Windows Hi André Stop top-posting. Be considerate of others. I have duplicated the service not starting problem on my Windows 7 box; it's looking like a procrun parameter parsing problem, but I'm still chasing it. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
I've encountered and solved hundreds of Tomcat-as-a-Windows-Service problems before, but I have never seen Tomcat not log anything. If you don't mind, could you run Tomcat7w.exe, screenshot each tab (Alt + Print Screen gets a screenshot for just the window instead of the whole thing), put the screenshots online somewhere public, and then post links to the screenshots here? My money is on finding something amiss there. http://rdfined.fastmail.fm/diverse/Tomcat7w.zip Question: When you run the service installer, it installs Tomcat at C:\Program Files\Apache Software Foundation\Tomcat 7.0, correct? (Unless, of course, you changed it at install time.) Yes - It creates that exact path and install files into the Tomcat 7.0 folder. Question: I know at some point you said this, but I can't find the email anymore. Can you remind me what version of Windows you are running on? Microsoft Windows 2003 R2 - Datacenter x64 edition - Service Pack 2 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
On Tue, Feb 26, 2013 at 7:04 AM, Rune Stilling s...@rdfined.dk wrote: Hi list I have been trying to get this to work by looking a lot on similar situations around the net but nothing works. My setup is as follows: * Tomcat 7.0.37 installed via the Windows service installer package * Windows 2003 server * Java/JRE 1.7.0_15 * Using C:\Program Files\Java\jre7\bin\server\jvm.dll I'm currently running tomcat7.0.37 (since I'm running TomEE 1.6.0-snapshot) on Windows Server 2008 R2 64bit, but when I was running tomcat7/tomee on Windows Server 2003 32-bit, I was running Client JVM instead of Server JVM (I wish I knew about Server JVM back in those days...2 or 3 months ago), but myself and endusers were satisfied with the performance of the web app running via tomcat7/tomee. So the problem is that the Tomcat7 service won't start from the service control panel. I just get a Could not start … and Error 1053: The service did not respond …. I experienced that Error 1053 last night (early this morning), but it was due to my attempt trying to get OpenOffice.org running as a service 'without' AlwaysUp software, but AlwaysUp software will definitely keep that software up and running. So, with that said, I will share my experience. tomcat7 (for windows) come bundled with tomcat7/bin/tomcat7w.exe, which is all you need (and which may be recommended by all/others) to start/stop and to configure the windows service. When installing tomcat7 as windows service for the first time, I have found success doing the following: 1. open Command Prompt window 2. cd \tomcat7\bin 3. service.bat install tomcat7 4. Create a shortcut to tomcat7w.exe, and copy the shortcut to your desktop (or Start menu, that's my preference) 5. Open tomcat7w.exe via your shortcut, Command Prompt, or whatever your preference, and go to Java tab, and configure the java options for the windows service, accordingly. There's nothing in the Tomcat logs (both stdout and stderr are empty). The event logs shows a generic service control manager error. But - If I start the service from the command line by typing tomcat7 //TS/Tomcat7 the thing works fine. Also if I change the service user account to the Administrator account I get a different error by startup Error 1068: The dependency service or group failed to start. It is not necessary (at all) to set Administrator. I always accept the default 'login' settings for tomcat7 windows service. I'm sure you can do the same, unless you have specific requirement to change service user account to Administrator. Any ideas? /Rune - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org I saw your email earlier this morning, but waited to see if anyone else would respond. No response, so I took the liberty to offer/share my experience/opinion/recommendation.
Re: Tomcat 7 doesn't start on Windows
Rune Stilling wrote: Hi list I have been trying to get this to work by looking a lot on similar situations around the net but nothing works. My setup is as follows: * Tomcat 7.0.37 installed via the Windows service installer package * Windows 2003 server * Java/JRE 1.7.0_15 * Using C:\Program Files\Java\jre7\bin\server\jvm.dll So the problem is that the Tomcat7 service won't start from the service control panel. I just get a Could not start … and Error 1053: The service did not respond …. There's nothing in the Tomcat logs (both stdout and stderr are empty). The event logs shows a generic service control manager error. But - If I start the service from the command line by typing tomcat7 //TS/Tomcat7 the thing works fine. Also if I change the service user account to the Administrator account I get a different error by startup Error 1068: The dependency service or group failed to start. Any ideas? Hi. Running Tomcat as a Service under Windows, starting from the standard tomcat.apache.org Windows installer package, is something that just works for everyone, all the time. So it is probable that you are not getting any answers here, because nobody really has any idea why Tomcat would not start as a Service in your case in particular. Are you really running Tomcat as is, or did you fiddle with the configuration, or add some non-Tomcat component before you tried to start it ? Also your error The dependency service or group failed to start is rather puzzling, because to my knowledge the Tomcat Service does not depend on any other. It is easy to check, at least under Window XP. Unfortunately the location of this is something that the MS geniuses seem to take a vicious delight in changing in each new Windows version; but to get back to Windows XP at least : click Start..Run and enter services.msc. You will see a list of services. Find Tomcat, right-click on it a choose Properties. There should be a tab dependencies. In my case it's empty - and I believe that is how it should be. If in your case it isn't, that might give you a first idea of what is going on. A second source of ideas for what is going on may come from this Tomcat FAQ article : http://wiki.apache.org/tomcat/FAQ/Windows#Q11 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 doesn't start on Windows
On 2/26/2013 6:04 AM, Rune Stilling wrote: Hi list I have been trying to get this to work by looking a lot on similar situations around the net but nothing works. My setup is as follows: * Tomcat 7.0.37 installed via the Windows service installer package * Windows 2003 server * Java/JRE 1.7.0_15 * Using C:\Program Files\Java\jre7\bin\server\jvm.dll So the problem is that the Tomcat7 service won't start from the service control panel. I just get a Could not start … and Error 1053: The service did not respond …. There's nothing in the Tomcat logs (both stdout and stderr are empty). The event logs shows a generic service control manager error. But - If I start the service from the command line by typing tomcat7 //TS/Tomcat7 the thing works fine. Also if I change the service user account to the Administrator account I get a different error by startup Error 1068: The dependency service or group failed to start. Any ideas? /Rune Hi, Rune- I ran into something similar a while back on, I believe, Server 2008 R2. I ended up uninstalling Tomcat and all JVMs, manually removing all traces of the JVMs from the registry, and then re-installing a single JVM followed by Tomcat. -Terence Bandoian - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
