Bug 32053 - Could not load machine data: monodroid: error XA0000: Unexpected error
Summary: Could not load machine data: monodroid: error XA0000: Unexpected error
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2015-07-16 19:01 UTC by GouriKumari
Modified: 2017-06-29 22:48 UTC (History)
3 users (show)

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

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 on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2015-10-16 14:56:08 UTC
I'm not sure if you might still be hitting this problem with the VM. If you are, then collecting the various information from Bug 17613, Comment 37 might turn up some additional clues.

To make a guess, I think the "Argument cannot be null. Parameter name: s" might be the same result you'll get in the `mandroid-data.err` file.

The most common cause of the "could not load machine data" error that I've seen is the inclusion of non-ASCII characters in some part of the system configuration (username, hard drive volume name, machine name, "Program Files" folder name, etc.).
Comment 2 Bojan Rajkovic [MSFT] 2015-12-02 13:51:13 UTC
This is a client-side bug, not a server-side bug. Reassigning to Android.
Comment 3 Kent Green [MSFT] 2017-06-29 22:48:34 UTC
The `mandroid` program no longer exists, the old standalone Xamarin licenses that used the "load machine data" code path are no longer available for purchase, and it seems the original reporter of the bug was able to proceed past this issue.  I will accordingly mark the bug as RESOLVED NOT_ON_ROADMAP at this time.