Bug 35729 - [XAP] Device Manager does not launch VM
Summary: [XAP] Device Manager does not launch VM
Alias: None
Product: Xamarin Android Player
Classification: Xamarin
Component: Device Manager ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-11-10 06:13 UTC by Al Clark [MSFT]
Modified: 2015-11-19 06:20 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

XAP Logs (115.48 KB, application/zip)
2015-11-10 06:13 UTC, Al Clark [MSFT]

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 35729 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Al Clark [MSFT] 2015-11-10 06:13:00 UTC
Created attachment 13755 [details]
XAP Logs

Steps to Reproduce

1. Open XAP Device Manager.
2. Select 'play\ button for required device.

Expected Behaviour

Selected VM should launch.

Actual Behaviour

VM does not launch.

Windows 7
Using Active Directory

Logs attached
Comment 1 ben.brown 2015-11-19 06:20:45 UTC
Taking a look at the logs, it appears an exception is being thrown when trying to get the path to the running instance of adb.  It's possible this is due to the process being owned by another user, and as the current user you don't have rights to access the process.

We have a fix in review for this at the moment.  You may be able to get past this if there are no existing "adb" processes running at the time you launch a Xamarin Android Player device.