DotNetCore 3.0.1 HostingBundle install Error 0x80070643: Failed to install MSI package #17288
Labels
area-infrastructure
Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
feature-installers
Includes: Installers
Needs: Author Feedback
The author of this issue needs to respond in order for us to continue investigating this issue.
Comments
|
Unfortunately this log isn't quite the right one. This is the log from the exe bundle but the exe installs an MSI package (which is what's failing, see @joeloff can you help @petr123321 track that log down? |
|
Should be in %Temp%\dd_dd_DotNetCoreWinSvrHosting__20191121103343_000_AspNetCoreModuleV2_x64.log |
analogrelay
added
the
Needs: Author Feedback
|
Thanks @joeloff ! @petr123321 can you find and post that log file as well? That should have more detail on the specific error. |
|
Hi, log is: |
|
So from what I'm seeing, InstallValidate action is returning 3. This seems to happen since costing is showing that there is insufficient disk space. The properties below expressed as multiples of 512 bytes and they are all set to 0. Property(S): PrimaryVolumeSpaceAvailable = 0 |
There is 45 Gig of space, that's not that. But I don't know what else is. |
|
@petr123321 I figured as much. I'm digging further into the log and will let you know as soon as I find anything else. |
|
Ok, it looks like it's reporting a missing directory, though the name of the directory is empty: MSI (s) (10:88) [11:52:59:890]: Note: 1: 2727 2: that translates to The directory entry '[2]' does not exist in the Directory table. and according to the log, the value for [2] is empty I've been going through the MSI tables and I don't see anything out of the ordinary. 2727 usually indicates that one of the entries in the Directory table failed to resolve correctly. The obvious point of failure is where a directory references needs to be resolved, e.g. the destination of a where a file would be installed (File table traced through the Component table and back to the Directory), a file that needs to be deleted or a registry key that writes something like a path and relies indirectly on obtaining the value from a property in the Directory table, e.g. you refer to a property [Abc] but the Directory table actually has it defined as 'abc'. This is the second time we've come across this issue I think. I'll keep digging |
|
<Comment deleted by @anurse ... this predated our policies around the "Needs: Author Feedback" label and it didn't get updated properly ;). No automated action will be taken on this issue for now> |
analogrelay
removed
Needs: Author Feedback
|
Any news please? :-( |
|
Let's try something else. Based on the logs, the MSI was cached and run from the folder below. C:\ProgramData\Package Cache{621912CF-223F-4C53-8F31-FB83687FD9E4}v13.0.19309.0\aspnetcoremodule_x64_en_v2.msi Could you try the following:
I'm hoping running manually with maximum verbose logging would yield more information. The ancm.log file should just be created in the folder you're running from. Jacques |
analogrelay
added
the
Needs: Author Feedback
|
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate. See our Issue Management Policies for more information. |
|
Hi, I have tried that with no success: |
analogrelay
added
Needs: Attention 👋
|
Thanks for running this manually. The one error I do see is this: Info 2898. For WixUI_Font_Title textstyle, the system created a 'Tahoma' font, in 0 character set, of 14 pixels height. For Repair/Modify, the ChangeButton is usually the default control and it appears that it's disabled. I'm taking a closer look. When run as part of the bundle the UI is never enabled, but the behavior seems contradicting as it thinks it's doing an install and yet want to switch into maintenance mode which means it thinks the product is installed. |
|
So that error seems to be related to having Modify/Repair disabled in ARP. The logs do suggest that the product is already installed. I would suggest trying the following:
|
analogrelay
added
Needs: Author Feedback
|
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate. See our Issue Management Policies for more information. |
ghost
locked as resolved and limited conversation to collaborators
JunTaoLuo
added
the
area-infrastructure
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I cannot install even after reboot ASP.NET Core 3.0.1 Hosting bundle with error:
There is a problem with installation of:
[DCB4:4FB8][2019-11-21T10:33:48]i319: Applied execute package: AspNetCoreModuleV2_x64, result: 0x80070643, restart: None
[DCB4:4FB8][2019-11-21T10:33:48]e000: Error 0x80070643: Failed to execute MSI package.
Full log:
The text was updated successfully, but these errors were encountered: