I'm using 64 bit Windows 8. It was fine yesterday, and it just failed to start. It shows the loading screen, but it just stop right there.
Anyone has the same problem? Any fix? It has happened to me twice with my old pc, which were using 32 bit Windows 7.
While I haven't heard of this issue before, here's something that will hopefully fix the issue:
find a directory called .devcenter in your user directory (that should be \Users\<youruser>)
move this directory to a different location
start DevCenter
If this doesn't work:
in the same \Users\<youruser>\.devcenter\logging folder find the log.txt file; you might be able to see the root error
there is a newer version available (1.1.1)
Some time this can be due to Java version. For me it was failing because I was using Java 9. It worked fine after downgrading to Java8. Confirm compatibility of your devcenter and java
Related
Hey I changed my System from Linux to Windows and I would like to install Node.js via .exe. The problem I have is, that I get an Error Pop-up. How could I fix it?
What I tried:
I checked already the permissions and I got also the confirm-box for the admin and everything seems to be normal.
Install Windows 10 ISO via bootable stick and Rufus in MBR and GPT and also by creating an usb via MediaCreationTool.
Thanking you in anticipation
Yeah, I got in this issue too. There is already an approved bug on the maintainers GitHub: https://github.com/nodejs/node/issues/39224. So assume that a fix will be available in the next days.
Short term solution: Install the version before the latest (e.g. 14.17.1): https://github.com/nodejs/node/issues/39224#issuecomment-872702653. This worked for me
I have found nothing to help me solve this problem, even though similar issue have been described in Stackoverflow, none which solve my problem. So here we go again.
I installed Android Studio in Ubuntu 14.04 (switching over from Windows 10). Followed the instructions as posted on Ubuntu site. Started a blank project and immediately got the following Gradle error:
Gradle sync started
8:54:11 PM Gradle sync failed: Process 'command '/opt/android-studio/jre/bin>/java'' finished with non-zero exit value 2
This is an empty project. All default settings. I'm at a loss. Maybe the ease with which I managed to get projects going in a Windows environment has led me towards unreasonable expectations with this Linux version... dunno.
I had this problem 2 days ago and changing the JDK path worked for me..
I downloaded Oracle jdk..
I hope that helps you
and Happy coding.
I have just solved the problem ,I think there is a problem in the default jre that comes with the android-studio (..../android-studio/jre) you can change it and see if it works for you.
find the java installed directory readlink -f $(which java) will reveal the path, in my case /usr/lib/jvm/java-8-oracle/jre/bin/java
right click on project > open module settings then go to sdk location in the left panel set your jdk location.
if you don't have oracle jdk installed then you can try with openjdk .If it shows the same kind of error ,remove open jdk and install oracle jdk.
Hope it helps.
DevCenter 1.5.0 won't start, even though it was working a few days ago. I have already tried as suggested by the answer to this question : Datastax Devcenter 1.1 fail to start
However it didn't work for me. It did lead me to think it might be due to having updated to Eclipse Mars Yesterday, perhaps?
Any ideas would be great. Thanks in advance.
In response to the comments below I am running windows 7. Also I just realised that even though my JAVA_HOME is set correctly I am gettng this error when I run java -version:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\username>java -version
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
Update : I fixed the java -version issue above by removing java.exe from C:/Windows/System32/ . But DevCenter is still not working.
OS: Windows 10 Pro
Dev Center - 1.6.0 (downloaded as zip. to run, we need to unzip and it's ready to go)
Today I faced a similar problem and was able to resolve by deleting/uninstalling the current Dev Center and re-installing. When you delete manually, make sure you delete the .devcenter folder. You will then have to reconfigure the connection(s) that you were using.
-Regards
This issue occurs on my computer. it's was resolved.
do you make sure setup python 27 and java sdk 8u ? if was set up and it's not running you can check previous version 1.5
I've installed Virtuoso OpenSource 7.2.+ on my Ubuntu 14.04 LTS. When I change virtuoso.ini (any change such as adding a new directory to the DirsAllowed), the server fails to work; when I set the configurations back to its defaults, then it's working. Any idea here?
Yes it is solved!
The problem, as I said, was because of existing a transaction log from an earlier version. It seems this is an old bug in Virtuoso according to Bug286953.
Anyway, I removed virtuoso.trx file and restarted my machine, it's now working.
When i start android device monitor in android studio "Java has started but returned exit code = 13" error with java path files is displayed.
I am using "android studio (beta)0.89"
I fixed this problem on my Windows 7 computer by installing the 64 bit version of Java 8. I did not have to uninstall or downgrade Java.
Be careful when downloading the Java installation. According to this FAQ, you will probably end up with 32 bit if you use the default installation.
Manually select the 'Windows Offline (64-bit)' version here, rather than letting the Java website choose for you.
This has happened to me just now after installing the latest Java version (v8) which for some reason only comes with 32-bit support while my PC is 64-bit.
I fixed the issue by uninstalling the version 8 of Java which automatically downgraded to Java 7 and it works fine.
I have been able to fix this issue by uninstalling the 32-bit Java 8 version I had, and then installing the latest 64-bit Java 8 version instead. (I didn't have to downgrade)
I think you are trying to open the wrong version of the monitor.exe it might have been changed during an upgrade. Under sdk/tools/lib there should be both the 32 and 64 bit versions under the "monitor-x86 or _64" folder. try either one if it works good. If you want to download the 64bit java version you must use a 64 bit browser. example in IExplorer 11 + you can change it back to 32 bit and back to 64 bit when needed. I did try the java upgrade before and was still getting the java error.
Install both 32 and 64 bit of Java 8. That fixed it for me.
Follow the path provided in the error pop-up. Add the java path in the eclipse.ini file located in the monitor folder in android studio.
Add : -vm
C:\Program Files\Java\jre7\bin\java.exe(Path to your current java file)
Before: -vmargs
If you are running win8.X just go to control panel and uninstall the java 8 version and after everything works fine.
I ran into this issue, even though I had the latest x64 build of the Java 8 JDK installed and set to the JAVA_HOME environment variable.
For me at least, the first line of the error popup shows that it is using Oracle's symlink at C:\ProgramData\Oracle\Java\javapath to find the correct location of javaw.exe. In my case, this was actually pointing to the x86 build of the same version of the JRE, which I also had installed for some reason.
I ended up cleaning house and uninstalling all versions of JRE/JDK, and then reinstalling the latest x64 JDK. This realigned the symlinks, and now it's running smoothly.
Most of the other answers should help resolve this same problem, but for diagnostic purposes if you do have the x64 version installed already, it will probably help to check C:\ProgramData\Oracle\Java\javapath.
[SOLUTION]
Go to following file in your android SDK
Sdk\tools\lib\monitor-x86_64\monitor.ini
and add following line, you might have to change the path to your java
-vm C:\Program Files\Java\jre7\bin\java.exe
just before "-vmargs "
Found solution:
Uninstall Java 8 Update (64-bit)
Install Java 7 Update 71 (64 bit)
I also downgraded JDK from 8 to 7, but it might be not required