NexDome Control System Setup - Setup Failed (0x800713ec - Asia)

[donotunplug]

NexDome_Control_System_20191112120136.log

[donotunplug]

Running a PrimaLuce PC with Windows 10 Enterprise LTSB (Build 10240). Installation fails 1/3 of the way through with the following error (attached).

In case it matters, .NET Framework is 4.6.01590 ![Uploading Screen Shot 2019-11-12 at 12.00.04 AM.png…]()

[NameOfTheDragon]

The culprit appears to be that installation of .NET Framework 4.7.2, which is chained from the web as part of the installation process if it is not already installed. The "smoking gun" in the log file is:

[0458:17DC][2019-11-12T12:01:44]i301: Applying execute package: NetFx472Web, action: Install, path: C:\ProgramData\Package Cache\507ECDADC23A27C2283BA130A2AA51650E6BC05B\redist\NDP472-KB4054531-Web.exe, arguments: '"C:\ProgramData\Package Cache\507ECDADC23A27C2283BA130A2AA51650E6BC05B\redist\NDP472-KB4054531-Web.exe" /q /norestart /ChainingPackage "NexDome Control System" /log "C:\Users\PRIMAL~1\AppData\Local\Temp\NexDome_Control_System_20191112120136_000_NetFx472Web.log.html"'
[0458:17DC][2019-11-12T12:02:32]e000: Error 0x800713ec: Process returned error: 0x13ec
[0458:17DC][2019-11-12T12:02:32]e000: Error 0x800713ec: Failed to execute EXE package.
[07D8:1518][2019-11-12T12:02:32]e000: Error 0x800713ec: Failed to configure per-machine EXE package.
[07D8:1518][2019-11-12T12:02:32]i319: Applied execute package: NetFx472Web, result: 0x800713ec, restart: None
[07D8:1518][2019-11-12T12:02:32]e000: Error 0x800713ec: Failed to execute EXE package.
[0458:17DC][2019-11-12T12:02:32]i351: Removing cached package: NetFx472Web, from path: C:\ProgramData\Package 

According to this question on Stack Overflow, some of the possible causes for this are:

• There is a pending restart from a previous setup. Reboot and try again.
• Low hard drive space on the installation volume. Free up some space and try again.

In the SO question, the poster's issue was resolved by freeing up disk space but this is not a conclusive solution as others have commented that it didn't work for them.

My own feeling is that there is some sort of temporary condition that is blocking the install. Note that internet connectivity is required to download the .NET Framework 4.7.2 web installer. My suggestions are to try the following steps, in order:

1. Free up as much disk space as possible. Make sure all your drives have plenty of free space (no red bars under "This PC". Reboot and try the install again.
2. Manually download and install .NET Framework 4.7.2. The installer will detect this and then not try to install it as part of the setup process. After installing .NET 4.7.2 reboot before retrying the NexDome install.

Please report back and let us know how this goes.

[donotunplug]

.NET 4.7.2 appears to be the culprit.

However, 4.7.2 can't be installed on Windows 10 Enterprise LTSB (Build 10240, version 1507). As per https://docs.microsoft.com/en-us/dotnet/framework/install/on-windows-10 the latest .NET that is supported on Windows 10 Enterprise LTSB (Build 10240, version 1507) is .NET 4.6.2 which is what I have installed currently.

Can NexDome controller software be installed with .NET 4.6.2? If not... any other suggestions? Upgrading Widows OS is not an option right now, given the nature of LTSB edition.

[donotunplug]

Update: I upgraded OS to Win 10 Enterprise LTSC 2019. Since then I was able to update the the current .NET platform, and subsequently install NexDome driver. So far all appears to connect and function. Installation issue resolved.

[NameOfTheDragon]

Thanks for the update. I’m sorry it wasn’t possible to support your previous version of Windows.

Best regards, Tim Long

From: Alexander Tardif notifications@github.com Sent: 14 December 2019 07:18 To: nexdome/ASCOM ASCOM@noreply.github.com Cc: Tim Long Tim@tigranetworks.co.uk; Assign assign@noreply.github.com Subject: Re: [nexdome/ASCOM] NexDome Control System Setup - Setup Failed (0x800713ec - Asia) (#12)

Update: I upgraded OS to Win 10 Enterprise LTSC 2019. Since then I was able to update the the current .NET platform, and subsequently install NexDome driver. So far all appears to connect and function. Installation issue resolved.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHubhttps://github.com/nexdome/ASCOM/issues/12?email_source=notifications&email_token=AAJVWCVSW766S5XFLUOIU3TQYSCEJA5CNFSM4JMIMCN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG34HHI#issuecomment-565691293, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAJVWCX47TDVR6U2ZU7Z5ODQYSCEJANCNFSM4JMIMCNQ.