Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to determine location for extracting embedded files #3821

Closed
genifycom opened this issue Oct 30, 2019 · 4 comments
Closed

Failed to determine location for extracting embedded files #3821

genifycom opened this issue Oct 30, 2019 · 4 comments
Milestone

Comments

@genifycom
Copy link

Using single publish file with DotNet 3.0.100 under Windows 10.

Installed machines sometime run under regular command prompt but sometimes we get:

Failure processing application bundle.
Failed to determine location for extracting embedded files
A fatal error was encountered. Could not extract contents of the bundle

In this case, we have to run an Administrative command prompt.

Is this expected behavior or something else? How to debug this?

@vitek-karas
Copy link
Member

@swaroop-sridhar

@vitek-karas
Copy link
Member

You can set COREHOST_TRACE=1 which will produce a lot of diagnostics output to stderr which should contain the underlying reason why it failed. You can also add COREHOST_TRACEFILE=t.log to redirect the diag output to a file.

@swaroop-sridhar
Copy link
Contributor

@genifycom this is definitely not expected behavior.
Can you please check that %TEMP% directory is accessible and writable by all users (the default configuration)?

If you can collect the trace for a failing run (as @vitek-karas pointed out above), it would be helpful to root-cause the problem. Thanks.

@msftgits msftgits transferred this issue from dotnet/core-setup Jan 30, 2020
@msftgits msftgits added this to the 5.0 milestone Jan 30, 2020
@maryamariyan maryamariyan added the untriaged New issue has not been triaged by the area owner label Feb 23, 2020
@jeffschwMSFT jeffschwMSFT removed the untriaged New issue has not been triaged by the area owner label Feb 24, 2020
@agocke
Copy link
Member

agocke commented Aug 17, 2020

Closing this out until we can get a log or repro

@agocke agocke closed this as completed Aug 17, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants