Forums: Troubleshooting and Problems
First, check with your company IT team if you have any user account restrictions on your computer.
Hi,
Additionally, you can download and save this debug file in the Validator's main directory and when you run it it should print out the full reason why the Java Virtual Machine could not be created. The issue is likely due to environment restrictions like Sergiy suggested, or because of limitations of your hardware (Not enough free RAM to support both the Validator with its default settings and the processes you currently have running, for example).
Once we determine what the specific problem is, we'll help you find a solution so you can get everything up and running.
Regards,
Tim
Thanks,
I did check with IT first and they were pretty stumped. I ran the program you sent after saving it to the location with the other files and it says "Unable to access jarfile lib/validator-gui-1.1.jar".
The only thing I could think of is that I downloaded the newest version of Java but didn't install it (since i don't have admin privaleges). Then when I checked the path with the IT guy, I think I entered the path for the newest uninstalled version of java.
Thanks for your help!
Maria
Hi Maria,
Based on that message, it sounds like the client.bat is not resolving the current directory correctly. There is a manual fix for this that we've suggested to a few people in the past, but I'd like to see if it's a situation we can accommodate for on our end. When you get a chance, please try downloading this new batch file and seeing if running it will correctly launch the Validator.
If that fixes the problem, we'll update the client.bat file in future releases accordingly.
Regards,
Tim
Hi Tim,
The new batch file didn't work -- it gave the same error message. I am trying to get in touch with IT so I can have admin access to the path thing - I think there is a mistake there. After I get that fixed, I will let you know if it is not working.
Thanks,
Maria
I had this same problem and resolved it by removing the -XX:+HeapDumpOnOutOfMemoryError option from the client.bat file.
I also got the "Unable to access jarfile..." error when I downloaded the client-correcting.bat file, but that's because I was still working with version 1.0.1. Downloading v1.1 (or changing the name of the referenced jarfile from validator-gui-1.1.jar to validator-gui.1.0.1.jar) fixed that problem
First off, thank you to Richard for spotting that problem, because it's certainly something I hadn't thought about.
Since this issue may arise for others as well, I'll briefly explain what's going on. The -XX:+HeapDumpOnOutOfMemoryError option was not added to the JRE until Java 1.5.0_07, so users with an older version will get a "Could not create the Java virtual machine" message when trying to launch the desktop client.
This can be resolved in two ways:
- The first is to update your client.bat file, as Richard suggested. For convenience, you can copy the code below and replace what's in the file (The code assumes you have the 1.1 release):
START /B javaw -Xms256m -Xmx1024m -jar lib/validator-gui-1.1.jar
- The other way is to update your Java runtime to a newer version, which you can do from the Java website.
- Tim
Thanks Richard and Tim. Deleting that line in the client.bat file worked. Thank you for all your help!!
Maria
Great! We're glad to hear that you got it working. Please let us know if you have any more comments or questions.
Regards,
Tim
Hello,
I'm having a similar problem. When I double-click on client.bat the Command Shell window opens and closes so quickly I can't see an error message and the GUI fails to open. Should the javaw.exe file be in the same directory as client.bat?
Many thanks,
Steve
Hi Steve,
Sorry to hear that you're having trouble, but hopefully we can get things working for you. Please download the debug client.bat file into your Validator folder and see if it allows you to view the error. As far as javaw.exe goes, you don't need to have that in the same directory (it should be somewhere else).
Regards,
Tim
I have the same problem with javaw... The error message tells me that 'Windows cannot find 'javaw'." I have java 1.5_0_22 on my system and of course javaw.exe is in Java folders...
I tried the debug file posted by Tim, and changed client.bat as Tim suggested. I'm getting 'Windows' cannot find java" error. We just migrated to Windows 7, can this be a problem?
Thanks
Ted
Hi,
I downloaded the new validator and checked my version of Java, which is 1.5.0_06. When I double click on client.bat, I get a pop-up message saying "Could not create the Java virtual machine." I tried modifying the "path" to include the java location and I am still unable to get it to work. Please help!