search

wsharba / opendatakit

Automatically exported from code.google.com/p/opendatakit
0 stars 1 forks source link

ODK Aggregate setup fails with Java 8 runtime - hangs on Windows 8 machine on running the .hta script on mshta.exe #989

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install the ODK aggregate on Windows 8 machine.
2. While finishing installation and running the HTA script, After entering the 
email and app-specific password the setup hangs
3. The setup says "Using JAVA_HOME and updating path" and hangs there. I am 
waiting from past 1 hour.
4) The JAVA_HOME variable is set to JDK directory(Not the bin path, but native 
JDK directory). The JDK version I am using is JDK-8

What version of the product are you using? On what operating system?
-- I am using ODK Aggregate v1.4.2 windows-installer

What could be the issue???

Original issue reported on code.google.com by writetob...@gmail.com on 28 Mar 2014 at 10:12

Attachments:

GoogleCodeExporter commented 9 years ago 
There is something broken with Java 8.

Uninstall and use Java 7.

These issues are best debugged via our e-mail list opendatakit@

Original comment by mitchellsundt@gmail.com on 28 Mar 2014 at 5:54

GoogleCodeExporter commented 9 years ago 
As per your instructions, I used Java 7 Update 51.
Pretty same results? Is it because I am using an Windows 8 machine?

Original comment by writetob...@gmail.com on 29 Mar 2014 at 9:52

GoogleCodeExporter commented 9 years ago 
Other things to try -- when you specify the location in which to create the ODK 
Aggregate directory for the installer, specify a location under your "My 
Documents" or "Documents" folder.

If you are comfortable working with scripting files, when it hangs, there will 
be several files in the directory containing the uploadAggregateToAppEngine.hta 
file:

action.cmd 
userpass.txt

These might be removed when you kill the script window, so you might need to 
save them off somewhere then put them back after you kill the script window.

You can open a cmd window and run the action.cmd file from that via:

.\action.cmd

The output will either be into the cmd window, or it will be saved in a file 
called:

output.log

Does any error get reported in the cmd window?

Is there any error reported in the output.log?

Original comment by mitchellsundt@gmail.com on 29 Mar 2014 at 11:50

GoogleCodeExporter commented 9 years ago 
Closing this issue, as user is not responsive.

Original comment by mitchellsundt@gmail.com on 19 Apr 2014 at 1:45