Android Device Monitor doesn't open - error on log file

Question

In Android Studio when I try running Android Device Monitor, I get the following error on log file:

    >!SESSION 2014-12-17 09:57:30.625 -----------------------------------------------
    eclipse.buildId=unknown
    java.version=1.8.0_25
    java.vendor=Oracle Corporation
    BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=pt_BR
    Command-line arguments:  -os win32 -ws win32 -arch x86_64 -data @noDefault

    >!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.366
    !MESSAGE Bundle reference:file:org.apache.ant_1.8.3.v201301120609/@4 not found.

    >!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.372
    !MESSAGE Bundle reference:file:org.apache.jasper.glassfish_2.2.2.v201205150955.jar@4

not found.

    >!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.373
    !MESSAGE Bundle reference:file:org.apache.lucene.core_2.9.1.v201101211721.jar@4 not

found.

    >!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.439
    !MESSAGE Bundle reference:file:org.eclipse.help.base_3.6.101.v201302041200.jar@4 not

found.

    >!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.439
    !MESSAGE Bundle reference:file:org.eclipse.help.ui_3.5.201.v20130108-092756.jar@4 not

found.

    >!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:31.440
    !MESSAGE Bundle reference:file:org.eclipse.help.webapp_3.6.101.v20130116-182509.jar@4

not found.

...

    >!ENTRY org.eclipse.osgi 4 0 2014-12-17 09:57:32.218
    !MESSAGE Application error
    !STACK 1
    >java.io.IOException: The folder "C:\Users\SAA%20PC\.android\monitor-workspace\.metadata" is read-only.
    > at org.eclipse.core.runtime.internal.adaptor.BasicLocation.lock(BasicLocation.java:206)
      at org.eclipse.core.runtime.internal.adaptor.BasicLocation.set(BasicLocation.java:164)
      at org.eclipse.core.runtime.internal.adaptor.BasicLocation.set(BasicLocation.java:137)
      at com.android.ide.eclipse.monitor.MonitorApplication.start(MonitorApplication.java:53)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

Anyone know what could it be? Thanks for any help.

Solution 1

If you are on windows try opening your Android Studio in Administrative Mode (Run as administrator)

Solution 2

I encounter this problem before. I fixed this issue by killing or ending "monitior.exe" running process using Taskmanager in Windows. Then click ADM (Android Device Monitor) and it works

Solution 3

This is due to the error that the android device monitor not able to locate the jre so in order to solve this :

please follow the following Steps:

Step 1 : In your android studio find the jdk path, then inside jdk locate the jre and copy it. (In case of Linux jre is located inside android studio folder)

Step 2 : After copying jre paste it inside the (Android/Sdk/tools/lib/monitor-x86_64/) i.e monitor-x86_64 directory

I tried this for linux operating system, Android device monitor started well without any error.

Thanks, Hope this will help to someone!

Solution 4

I had the same issue with Mac OS X.

To solve it:

• Open a terminal window
• Navigate to your SDK
• Locate the 'tools' folder
• cd into it
• run: sudo ./monitor
• Type in your password

Good to go!

Solution 5

This is the problem due to updating SDK tools Android SDK Tools

• close the Android Studio
• open the SDK Manager.exe from SDK folder
• Now install Android SDK tool in my case tool is Rev.24.3.2
• open Android Studio it will show new tool is available install it,install that one and try to restart it.

View more solutions

Comments

[Evgeniy Mishustin]

It worked! Thanks. Can you explain what was the cause of the problem?

[IronBlossom]

@LuciusHipan Administative Mode elevates the process to access and writes on /AppData. From the log it seemed that the process wanted to change data on the /Users folder but couldn't able to because of right privilege.

[Adnan Ali]

@IronBlossom i have installed sdk in d drive and i dont think that it needs any other permission ,although this answer solved my problem

[cdomination]

Welcome to stack overflow! Answers as short as this can be posted in the comments section

[Chris]

Is there any way to do this without running as an admin?

[Rich]

Definitely should be the accepted answer...fixed on mac too just force quit the monitor process

[Adam Cox]

Yep! I had a bunch of these running (because I like to pound on things to get them to work - haha). Killed all of them and then back to VS to "Open Android Device Monitor (DDMS)" in the Android Toolbar. Voila!

[Naitik]

@IronBlossom I am using android studio in linux, what should i do for it.

[IronBlossom]

@Naitik Try opening Android Device Monitor from the sdk with gksu or gksudo cmd.

[Amber]

Awesome, I was trying to start it from the command line and opening the command prompt as admin fixed it!

[Bartosz]

Fixes problem on Win7 + VS 2017

[Deepak Borade]

very nice answer brother.you save my day

[Hong]

Thank you for the tip. This solves multiple problems - unable to start ADM, no debuggable processes...

[D B]

This answer worked for me with Android Studio 3.0.1, Why this is happening, Is it because of my environmental Variables?

[ToolmakerSteve]

@cdomination: I disagree. If it is genuinely a new answer, it should be posted as an answer. "shortness" isn't an issue, though "completeness" often is (many "short" answers don't give enough detail. Not the case here - it truly is that simply.) Benefits: 1) Not buried in comments. 2) If it works for other people, they can vote it up. 3) If it needs improving, it can be improved or commented on.

[dns]

This is the correct answer. In my case, I use OpenJDK 14 and it's not working. But after I installed Oracle JDK 8, it's working!

[Dmitry Dronov]

It help for me. Thank you. I used jdk-11. Reinstall at JDK8 and it work

[Suchith]

you can find jre inside jdk 8: in my case C:\Program Files\Eclipse Foundation\jdk-8.0.302.8-hotspot

[Emil]

@Suchith yea that works as well