Bug 24219 - Regarding xamarin android player installation and error during setup
Summary: Regarding xamarin android player installation and error during setup
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Android Player
Classification: Xamarin
Component: Player ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
: 24218 24225 ()
Depends on:
Blocks:
 
Reported: 2014-11-03 01:47 UTC by Parvez
Modified: 2015-01-15 08:42 UTC (History)
5 users (show)

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


Attachments
Xamarin_Android_Player_20141103112507_FatalError (5.81 KB, application/octet-stream)
2014-11-03 01:47 UTC, Parvez
Details
Xamarin_Android_Player_Logs_From_Temp.zip (95.72 KB, application/x-zip-compressed)
2014-11-12 00:10 UTC, Parvez
Details


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:
Status:
RESOLVED FIXED

Description Parvez 2014-11-03 01:47:29 UTC
Created attachment 8590 [details]
Xamarin_Android_Player_20141103112507_FatalError

I had followed all the required steps for installing xamarin android player installation as per the link http://developer.xamarin.com/guides/android/getting_started/installation/android-player/

My PC has all the necessary requirements for android player except graphics card point which I don’t know as per mentioned in the link.

I got fatal error code 0x80070643.

Please help me to get clear with installation part so that I can use new xamarin android player
Comment 1 Parvez 2014-11-03 01:48:30 UTC
Please see the attached error file
Comment 2 Parvez 2014-11-11 00:21:03 UTC
Hi 

Please provide any suggestion or help to install android player.

Thanks & Regards
Parvez
Comment 3 Will Schaller 2014-11-11 10:02:15 UTC
Hi Parvez,

Sorry you're having trouble installing the Player, we're looking in to why this might be now. 

Would you be able to send us some more logs? If you open the folder
C:\Users\[username]\AppData\Local\Temp
You should see a number of logs with names beginning with "Xamarin_Android_Player_" - if you could zip all those logs up and post that here it would really help us out.

Thanks,
Will


(In reply to comment #2)
> Hi 
> 
> Please provide any suggestion or help to install android player.
> 
> Thanks & Regards
> Parvez
Comment 4 Parvez 2014-11-12 00:10:27 UTC
Created attachment 8698 [details]
Xamarin_Android_Player_Logs_From_Temp.zip

Hello Will Schaller,

Thanks for your reply.

As requested i am attaching the logs of xamarin android player from temp folder "C:\Users\parvez.khan\AppData\Local\Temp".

Please find the attached .zip file.

Thanks & Regards
Parvez
Comment 5 Jon Goldberger [MSFT] 2014-11-13 19:03:29 UTC
*** Bug 24218 has been marked as a duplicate of this bug. ***
Comment 9 Parvez 2014-11-14 00:25:14 UTC
Hi Jon,

This means same issue has been reported by others.
Then please give us fix for installing xamarin android player as soon as possible.
Comment 10 Will Schaller 2014-11-14 13:21:06 UTC
We're trying to find a solution for this at the moment, it's not something we can easily replicate so it's a little difficult, but it looks to be an elevation problem. Parvez, could you let me know if you're running as an administrator user?

Also, this is likely a red herring, but could you try renaming the installer to XamarinAndroidPlayerBundle-amd64.exe and running it from the C drive?

Thanks,
Will
Comment 11 Parvez 2014-11-17 00:42:32 UTC
Hell Will Schaller,

No i was not trying to install xamarin android player as administrator.

Ok i will try now by renaming the installer to XamarinAndroidPlayerBundle-amd64.exe.

How to run it from C drive?
Comment 12 Parvez 2014-11-25 05:28:59 UTC
Hello Will Schaller,

Any update on this sir?

I did try to install android xamarin player as administrator but still have the same error on installing.

Below is the log file content
-------------
[1768:0F98][2014-11-03T11:25:07]i001: Burn v3.8.1128.0, Windows v6.3 (Build 9600: Service Pack 0), path: F:\softwares\Xamarin Android Player x64.exe, cmdline: ''
[1768:0F98][2014-11-03T11:25:07]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\PARVEZ~1.KHA\AppData\Local\Temp\Xamarin_Android_Player_20141103112507.log'
[1768:0F98][2014-11-03T11:25:07]i000: Setting string variable 'WixBundleOriginalSource' to value 'F:\softwares\Xamarin Android Player x64.exe'
[1768:0F98][2014-11-03T11:25:07]i000: Setting string variable 'WixBundleName' to value 'Xamarin Android Player'
[1768:0F98][2014-11-03T11:25:07]i100: Detect begin, 3 packages
[1768:0F98][2014-11-03T11:25:07]i000: Setting string variable 'NETFRAMEWORK45' to value '378675'
[1768:0F98][2014-11-03T11:25:08]i052: Condition 'NETFRAMEWORK45 >= 378389' evaluates to true.
[1768:0F98][2014-11-03T11:25:08]i101: Detected package: NetFx45Web, state: Present, cached: None
[1768:0F98][2014-11-03T11:25:08]i101: Detected package: VBoxInstaller_64bits.msi, state: Present, cached: Complete
[1768:0F98][2014-11-03T11:25:08]i101: Detected package: XamarinAndroidPlayer.msi, state: Absent, cached: None
[1768:0F98][2014-11-03T11:25:08]i199: Detect complete, result: 0x0
[1768:04C0][2014-11-03T11:25:10]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1
[1768:0F98][2014-11-03T11:25:10]i200: Plan begin, 3 packages, action: Install
[1768:0F98][2014-11-03T11:25:10]w321: Skipping dependency registration on package with no dependency providers: NetFx45Web
[1768:0F98][2014-11-03T11:25:10]i000: Setting string variable 'WixBundleRollbackLog_XamarinAndroidPlayer.msi' to value 'C:\Users\PARVEZ~1.KHA\AppData\Local\Temp\Xamarin_Android_Player_20141103112507_0_XamarinAndroidPlayer.msi_rollback.log'
[1768:0F98][2014-11-03T11:25:10]i000: Setting string variable 'WixBundleLog_XamarinAndroidPlayer.msi' to value 'C:\Users\PARVEZ~1.KHA\AppData\Local\Temp\Xamarin_Android_Player_20141103112507_0_XamarinAndroidPlayer.msi.log'
[1768:0F98][2014-11-03T11:25:10]i201: Planned package: NetFx45Web, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[1768:0F98][2014-11-03T11:25:10]i201: Planned package: VBoxInstaller_64bits.msi, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: Register
[1768:0F98][2014-11-03T11:25:10]i201: Planned package: XamarinAndroidPlayer.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[1768:0F98][2014-11-03T11:25:10]i299: Plan complete, result: 0x0
[1768:0F98][2014-11-03T11:25:10]i300: Apply begin
[0484:16C8][2014-11-03T11:25:11]i360: Creating a system restore point.
[0484:16C8][2014-11-03T11:25:11]i361: Created a system restore point.
[0484:16C8][2014-11-03T11:25:24]i000: Caching bundle from: 'C:\Users\PARVEZ~1.KHA\AppData\Local\Temp\{5f63cdbe-6d50-4fdf-8efb-add7866fe390}\.be\XamarinAndroidPlayerBundle-amd64.exe' to: 'C:\ProgramData\Package Cache\{5f63cdbe-6d50-4fdf-8efb-add7866fe390}\XamarinAndroidPlayerBundle-amd64.exe'
[0484:16C8][2014-11-03T11:25:24]i320: Registering bundle dependency provider: {5f63cdbe-6d50-4fdf-8efb-add7866fe390}, version: 0.0.24.0
[0484:1548][2014-11-03T11:25:30]i305: Verified acquired payload: XamarinAndroidPlayer.msi at path: C:\ProgramData\Package Cache\.unverified\XamarinAndroidPlayer.msi, moving to: C:\ProgramData\Package Cache\{EFC6F0E7-0E59-452E-84E4-F801048B6D35}v0.0.24\XamarinAndroidPlayer.msi.
[0484:16C8][2014-11-03T11:25:30]i323: Registering package dependency provider: {5632714F-6A48-4BF2-89E0-F8B6CE9FE6D1}, version: 4.3.10, package: VBoxInstaller_64bits.msi
[0484:16C8][2014-11-03T11:25:30]i325: Registering dependency: {5f63cdbe-6d50-4fdf-8efb-add7866fe390} on package provider: {5632714F-6A48-4BF2-89E0-F8B6CE9FE6D1}, package: VBoxInstaller_64bits.msi
[0484:16C8][2014-11-03T11:25:30]i323: Registering package dependency provider: {EFC6F0E7-0E59-452E-84E4-F801048B6D35}, version: 0.0.24, package: XamarinAndroidPlayer.msi
[0484:16C8][2014-11-03T11:25:30]i301: Applying execute package: XamarinAndroidPlayer.msi, action: Install, path: C:\ProgramData\Package Cache\{EFC6F0E7-0E59-452E-84E4-F801048B6D35}v0.0.24\XamarinAndroidPlayer.msi, arguments: ' MSIFASTINSTALL="7" ARPSYSTEMCOMPONENT="1" INSTALL_LOCATION=""'
[0484:16C8][2014-11-03T11:25:56]e000: Error 0x80070643: Failed to install MSI package.
[0484:16C8][2014-11-03T11:25:56]e000: Error 0x80070643: Failed to execute MSI package.
[1768:0F98][2014-11-03T11:25:56]e000: Error 0x80070643: Failed to configure per-machine MSI package.
[1768:0F98][2014-11-03T11:25:56]i319: Applied execute package: XamarinAndroidPlayer.msi, result: 0x80070643, restart: None
[1768:0F98][2014-11-03T11:25:56]e000: Error 0x80070643: Failed to execute MSI package.
[0484:16C8][2014-11-03T11:25:56]i318: Skipped rollback of package: XamarinAndroidPlayer.msi, action: Uninstall, already: Absent
[1768:0F98][2014-11-03T11:25:56]i319: Applied rollback package: XamarinAndroidPlayer.msi, result: 0x0, restart: None
[0484:16C8][2014-11-03T11:25:56]i329: Removed package dependency provider: {EFC6F0E7-0E59-452E-84E4-F801048B6D35}, package: XamarinAndroidPlayer.msi
[0484:16C8][2014-11-03T11:25:56]i351: Removing cached package: XamarinAndroidPlayer.msi, from path: C:\ProgramData\Package Cache\{EFC6F0E7-0E59-452E-84E4-F801048B6D35}v0.0.24\
[0484:16C8][2014-11-03T11:25:56]i330: Removed bundle dependency provider: {5f63cdbe-6d50-4fdf-8efb-add7866fe390}
[0484:16C8][2014-11-03T11:25:56]i352: Removing cached bundle: {5f63cdbe-6d50-4fdf-8efb-add7866fe390}, from path: C:\ProgramData\Package Cache\{5f63cdbe-6d50-4fdf-8efb-add7866fe390}\
[1768:0F98][2014-11-03T11:25:57]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No
Comment 13 Tetsuro Kato 2014-11-25 20:44:14 UTC
It seems that the installation fails when Windows Firewall service is disabled.
Comment 14 Parvez 2014-11-26 00:30:59 UTC
Hello Tetsuro Kato,

Thanks for you reply.

Should i enable Windows Firewall service? If yes then please can you tell me how to enable Windows Firewall service?

Thanks & Regards
Parvez
Comment 15 Tetsuro Kato 2014-11-26 06:44:56 UTC
Hello Parvez,

You can start/stop Windows Firewall service with "Service" window.
Openes "Run" dialog box by pressing the Windows logo key + R, type services.msc, and then press OK button.
Comment 16 Will Schaller 2014-12-17 11:23:17 UTC
Hi Tetsuro, thanks a lot for pointing us towards this, we hadn't been able to reproduce this but disabling the Firewall service does indeed cause the installer to fail. This seems to be due to a bug in WiX, we should be able to fix this for the next update.
Comment 17 Parvez 2014-12-17 23:51:06 UTC
Hello Will Schaller, Tetsuro kato

Thanks for the update regarding the bug.
Waiting for the next update. Hope it be as soon as possible.
But may i know atleast when next update will be release.
Comment 18 Will Schaller 2014-12-18 07:33:15 UTC
(In reply to comment #17)
> Hello Will Schaller, Tetsuro kato
> 
> Thanks for the update regarding the bug.
> Waiting for the next update. Hope it be as soon as possible.
> But may i know atleast when next update will be release.

Hi Parvez, 
The next update will be released around mid January, but in the meantime you should be able to get around this issue by temporarily enabling the Windows Firewall Service, following these instructions:

Open "Run" dialog box by pressing the Windows logo key + R, type
services.msc, and then press OK button. Find the "Windows Firewall" entry,
right click and Start the service. If the Start option is disabled, you may
need to go to the service's Properties and change Startup Type to Automatic.

Let me know if that fixes it for you, 
Thanks
Will
Comment 19 Will Schaller 2014-12-18 07:36:51 UTC
*** Bug 24225 has been marked as a duplicate of this bug. ***
Comment 20 Will Schaller 2015-01-15 08:42:23 UTC
This is fixed in update 0.2.5