Error Failed Creating Java Jre Bin Server Jvm.dll
following appears in the commons-daemon.log (in ConfluenceInstallationDirectory/logs): [2013-02-27 09:44:23] [error] Failed creating java C:\Programme\Atlassian\Confluence\jre\bin\server\jvm.dll [2013-02-27 09:44:23] [error] The specified module could not be found. Cause The path highlighted in the error is not valid. In the example above, there are no jvm.dll in C:\Programme\Atlassian\Confluence\jre\bin\server\ Resolution Edit the path set in your Windows service manually, to point to a valid jvm.dll (normally located in ConfluenceInstallationDirectory\jre\bin\client\jvm.dll), using the steps below: Right click on cmd.exe (Windows Command Prompt) and Run as Administrator cd toConfluenceInstallationDirectory\bin Run the following: tomcat6w //ES//
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign https://confluence.atlassian.com/confkb/unable-to-start-windows-service-due-to-failed-creating-java-jvm-dll-the-specified-module-could-not-be-found-325320860.html up Apache commons daemon “Failed creating Java” error up vote 3 down vote favorite 1 I'm trying to start a Windows service using the Apache commons daemon. It works on Windows XP, but I'm trying to run it on Windows 7 x64. It fails to start and I get the following error in the logs: [2010-12-13 17:21:19] [info] Commons Daemon procrun (1.0.3.0) http://stackoverflow.com/questions/4434217/apache-commons-daemon-failed-creating-java-error started [2010-12-13 17:21:19] [info] Running 'NodeService' Service... [2010-12-13 17:21:19] [info] Starting service... [2010-12-13 17:21:19] [error] Failed creating java [2010-12-13 17:21:19] [error] ServiceStart returned 1 [2010-12-13 17:21:19] [info] Run service finished. [2010-12-13 17:21:19] [info] Commons Daemon procrun finished I set the JAVA_HOME and added the java bin to PATH, just to be sure. I'm not sure why it's not starting, or if it has to do with the x64 operating system. It was designed for a 32-bit system originally. daemon apache-commons procrun share|improve this question asked Dec 13 '10 at 22:44 anom217 3814 add a comment| 4 Answers 4 active oldest votes up vote 5 down vote Just come across the same issue. You can resolve this by changing the JVM path to point to the x64 version as it uses the x32 by default In windows right click the application from the system tray and select configure Click Java tab Set the Java Virtual Machine to/ or use the select path button: C:\Program Files\Java\jdk1.7.0_21\jre\bin\server\jvm.dll share|improve this answer answered Apr 23 '13 at 8:54 Nath 1,8511617 add a comment| up vote 1 down vote Fixed the issue.
MAA Placement Test Suite Möbius - Online Courseware MapleNet Toolboxes & Connectors E-Books & Study Guides Professional Services SOLUTIONS Engineering: Industry Solutions https://www.maplesoft.com/support/faqs/detail.aspx?sid=32756 Machine Design / Industrial Automation Aerospace Vehicle Engineering Robotics Power Industries http://www.artofsolving.com/node/49.html Engineering: Application Areas System Simulation and Analysis Model development for HIL Plant Modeling for Control Design Robotics/Motion Control/Mechatronics Other Application Areas Education Mathematics Education Engineering Education High Schools & Two-Year Colleges Testing & Assessment Students Applied Research Financial Modeling Operations Research High Performance Computing error failed Physics PURCHASE Purchase & Pricing Details Maplesoft Web Store Request a Price Quote Contact Maplesoft Sales Elite Maintenance Program SUPPORT Tech Support & Customer Service Frequently Asked Questions Online Product Help Training Product Documentation Download Product Updates RESOURCES Webinars & Events Live Webinars Recorded Webinars Upcoming Events Community MaplePrimes Maplesoft Blog Maplesoft Membership Maple Ambassador error failed creating Program MapleCloud Publications Technical Whitepapers Application Briefs E-Mail Newsletters Maple Books Math Matters Examples & Applications Application Center MapleSim Model Gallery User Case Studies Exploring Engineering Fundamentals Teaching Concepts with Maple Resources Maplesoft Welcome Center Teacher Resource Center Student Help Center COMPANY About Maplesoft Contact Careers Media Center Partners 25th Anniversary Timeline Explore Customer Support Customer Support Home Frequently Asked Questions Maple Online Help Support Request Form Offline Activation Request Download Product Updates Training Support Policies User Resources Product Manuals and Installation Instructions MaplePrimes Welcome Center Maple Application Center Recorded Webinars Live Webinars
Stay Informed Subscribe to the Maple Reporter Become a Member Home : Support : Frequently Asked Questions : Unable to start Tomcat as a Windows Service Unable to start Tomcat as a Windows Service If Tomcat is installed but not starting, refer to Tomcat's log files to see if there are any errors.Installer just doesn't do what its name implies: it always fails to start Tomcat as a Windows Service. Unless you go and fix things manually. I wanted to test how Tomcat 6.0 can be installed to run automatically as a Windows service, to make life easy for Windows users. I downloaded the Tomcat Windows Service Installer (apache-tomcat-6.0.18.exe), which I used successfully in the past. The installation went fine, except that the service then just refused to start. A minor detail. The Windows error message was very helpful as usual: C:\>net start "Apache Tomcat" The Apache Tomcat service is starting. The Apache Tomcat service could not be started. A service specific error occurred: 0. More help is available by typing NET HELPMSG 3547. C:\>net helpmsg 3547 A service specific error occurred: ***. EXPLANATION A service-specific error occurred. ACTION Refer to the Help or documentation for that service to determine the problem. The Tomcat logs thankfully provided some more details - at least a search string to google for: [2009-05-30 02:52:27] [info] Starting service... [2009-05-30 02:52:28] [174 javajni.c] [error] The specified module could not be found. [2009-05-30 02:52:28] [994 prunsrv.c] [error] Failed creating java C:\Program Files\Java\jdk1.6.0_13\jre\bin\server\jvm.dll [2009-05-30 02:52:28] [1269 prunsrv.c] [error] ServiceStart returned 1 After some searching, I discovered this to be a known issue with Java 6.0 - Bug ID: 6509291 - that Sun kindly dismissed as not a defect. They mention it in the Java SE 6 Release Notes though: Java SE 6 applications that use custom launchers must be installed with msvcr71.dll in the same directory as the launcher executable. This follows the new Windows C runtime distribution model, per http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_CRT_C_Run.2d.Time_Libraries.asp. Tomcat apparently didn't want to take responsibility for the issue either - Bug 41538 has been closed as WORKSFORME. So we're left in this situation where using the latest Java version and the latest Tomcat Windows installer, the Service just doesn't start unless you go and manually perform an obscure additional step. Not exactly what an automated installer is meant for. One way to fix the problem is to copy this msvcr71.dll from the Java bin directory to the Tomcat bin directory. That's basically what Sun is saying, and most other people seem to suggest as well (e.g. Atlassian Confluence). However I think there's at least another - possibly better - option, and that's why I'm writing this blog entry. (EDIT: This is also mentioned by Mladen Turk in the Tomcat bug report, although I only noticed this later.