0x80004005 iis ошибка

I had the same issue when publishing the web app.
If anybody still has this problem fixed it by changing {AppName}.runtimeconfig.json

    {
  "runtimeOptions": {
    "framework": {
      "name": "Microsoft.NETCore.App",
      "version": "1.1.2"
    },
    "configProperties": {
      "System.GC.Server": true
    }
  }
}

Change the version from «version»: «1.1.2» to «version»: «1.1.1» and everythign worked ok

answered Jun 18, 2017 at 21:53

Had the same issue and all solutions didn’t work. Found this gem and thought I’d pass along if it helps someone else. Install on Server 2012 R2 getting the DLL missing error, try to reinstall VS C++ 2015 and get an error. Fix is to do the following:

Seems the file
C:ProgramDataPackage Cache...packagesPatchx64Windows8.1-KB2999226-x64.msu has problems being installed.
Open admin command prompt do:

c:
mkdir tmp
mkdir tmptmp
move "C:ProgramDataPackage Cache...packagesPatchx64Windows8.1-KB2999226-x64.msu" c:tmp
expand -F:* c:tmpWindows8.1-KB2999226-x64.msu c:tmptmp
dism /online /add-package /packagepath:c:tmptmpWindows8.1-KB2999226-x64.cab

NOTE: replace the «…» with the correct folder name. After this reinstall the VS C++ 2015 package.

answered Dec 14, 2016 at 20:58

I had a similar issue, and to quote Sherlock Holmes:
«when you have eliminated the impossible, whatever remains, however improbable, must be the truth?«

I checked if the .NET framework I was targeting was installed on the server, and it turns out it wasn’t. I installed the 4.6.2 .NET Framework and it worked.

I had the same problem when I updated my dev machine to Core 1.0.1, but forgot to update the server.

I was getting HTTP Error 502.5 while trying to publish my .NET Core 2.0 API to AWS EB, and solved it by adding the following code to the .csproj:

  <PropertyGroup>
    <PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest>
  </PropertyGroup>

answered Jan 15, 2018 at 18:04

I had a same issue . I changed application pool identity to network service account . Then I explicitly set the path to dotnet.exe in the web.config for the application to work properly as @danielyewright said in his github comment . It works after set the path.

Thanks

answered Nov 28, 2016 at 21:07

Sharing that in my case this error was because i forgot to update project.json with:

"buildOptions": {
    "emitEntryPoint": true
  }

answered Dec 9, 2016 at 10:39

I had the same error in question, with the same issues as described by VSG24 in Proposed answer — nasty error message when typing ‘dotnet’ into CMD:

The program can’t start because api-ms-win-crt-runtime-l1-1-0.dll is missing

I solved this by manually installing the following 2 updates on Windows Server 2012 R2 (and the pre-requisites and all the other updates linked — read the installation instructions carefully on the Microsoft website):

1. KB2919355
2. KB2999226

Hope this helps someone.

answered Mar 23, 2017 at 8:39

I faced the same issue when I tried to publish Debug version of my web application. This set of files didn’t contain the file web.config with the proper value of attribute processPath.

I took this file from Release version, value was assigned to the path to my exe file.

<aspNetCore processPath=".My.Web.App.exe" ... />

answered May 12, 2017 at 11:06

answered Jun 2, 2017 at 14:11

Here is what I figured, and this happened recently on Windows 10 after an update was installed. From what I gathered, a Windows Defender update was installed which assumed my «Project.dll»(an asp.net core project) behaved like a virus so it was deleted.

So, one of the first things I suggest you do before you start installing/uninstalling stuffs is to check to confirm your «Project.dll» is where it should be.

Copy it back to the location if it is no longer there.

If you are having difficulty copying the file back add an exclusion to your project folder in windows defender. ( Learn how to do that here. )

This worked for me instantly, and I repeated it across application multiple servers.

answered Oct 10, 2017 at 8:26

answered Apr 17, 2018 at 13:26

answered May 24, 2018 at 16:04

In my case, after installing AspNetCore.2.0.6.RuntimePackageStore_x64.exe and DotNetCore.2.0.6-WindowsHosting.exe , I need to restart server to make it worked without 502 bad gateway and proxy error.

UPDATE:

There is a way you could use it without restart:
https://stackoverflow.com/a/50808634/3634867

answered Apr 12, 2018 at 7:30

Open command prompt with Administrator credentials

Type following command and hit enter

> IISRESET

OR

Open Visual Studio 2017 with Administrator credentials

Type following command in Package Manager Console and hit enter

PM> IISRESET

PM> IISRESET
Attempting stop...
Internet services successfully stopped
Attempting start...
Internet services successfully restarted

answered Dec 13, 2018 at 7:07

I had this problem aswell (The error occurred both on VS 15 and 17). However on VS15 it returned a CONNECTION_REFUSED error and on VS17 it returned ASP.NET Core 1.0 on IIS error 502.5.

FIX

1. Navigate to your project directory and locate the hidden folder .vs (it’s located in the projects folder dir). (Remember to show hidden files/folders)

2. Close VS

3. Delete .vs-folder
4. Start VS as admin (.vs-folder will be recreated by VS)

answered Mar 30, 2017 at 14:44

For me it was that the connectionString in Startup.cs was null in:

services.AddDbContext<ApplicationDbContext>(options => options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection")));

and it was null because the application was not looking into appsettings.json for the connection string.

Had to change Program.cs to:

public static void Main(string[] args)
{
    BuildWebHost(args).Run();
}

public static IWebHost BuildWebHost(string[] args) =>
     WebHost.CreateDefaultBuilder(args)
     .ConfigureAppConfiguration((context, builder) => builder.SetBasePath(context.HostingEnvironment.ContentRootPath)
     .AddJsonFile("appsettings.json").Build())
     .UseStartup<Startup>().Build();

answered Dec 13, 2017 at 10:37

answered Dec 30, 2018 at 8:34

I had a similar issue (Asp.Net Core 2.x) that was caused by trying to run a 32-bit asp.net core app in IIS on a 64-bit windows server. The root cause was that the web.config that is auto-generated (if your project does not explicitly include one, which asp.net core projects do not by default) does not contain the full path to the dotnet executable. When you install the hosting bundle on a 64 bit machine it will install the 64 and 32 bit versions of dotnet, but the path will resolve by default to 64 bit and your 32 bit asp.net core app will fail to load. In your browser you may see a 502.5 error and if you look the server event log you might see error code 0x80004005. If you try to run dotnet.exe from a command prompt to load your asp.net core application dll on that server you may see an error like «BadImageFormatException» or «attempt was made to load a program with an incorrect format». The fix that worked for me was to add a web.config to my project (and deployment) and in that web.config set the full path to the 32-bit version of dotnet.exe.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <location path="." inheritInChildApplications="false">
        <system.webServer>
            <handlers>
                <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
            </handlers>
            <aspNetCore processPath="C:Program Files (x86)dotnetdotnet.exe" arguments=".My32BitAspNetCoreApp.dll" stdoutLogEnabled="false" stdoutLogFile=".logsstdout" />
       </system.webServer>
   </location>
</configuration>

answered Nov 30, 2018 at 18:29

I got the same problem and the reason in my case was that the EF core was trying to read connection string from appsettings.development.json file. I opened it and found the connection string was commented.

//{
//  "ConnectionStrings": {
//    "DefaultConnection": "Server=vaio;Database=Goldentaurus;Trusted_Connection=True;",
//    "IdentityConnection": "Server=vaio;Database=GTIdentity;Trusted_Connection=True;"
//  }
//}

I then uncommitted them like below and the problem solved:

{
  "ConnectionStrings": {
    "DefaultConnection": "Server=vaio;Database=Goldentaurus;Trusted_Connection=True;",
    "IdentityConnection": "Server=vaio;Database=GTIdentity;Trusted_Connection=True;"
  }
}

answered Jan 7, 2019 at 10:50

Answers

• That’s good news.  If it’s asking for authentication, that means the site should be at least working.

  If you go back to the first KB Article we posted (http://support.microsoft.com/kb/934164) there is a section at the bottom that talks about setting up the authentication.  They are steps 7 and 8 under «Install SQL Server 2005 Reporting Services».

  That should clear up the prompt.

• Step #7 should have nothing to do with IIS or SSRS.  That’s just changing site settings in Internet Explorer options.  One thing you may check is the «Require SSL» checkbox in the Trusted sites.  If that’s checked, IE may be redirecting you to port 443, which probably isn’t listening.

  You may also check under Windows Services and make sure that the Reporting Services service is started.  Because if it’s an SSL thing it’s odd, that it would know that «report server» is not responding.  Normally it would be something like a 404 error, or something like that.

Answers

• Hi Coder 206,

  This error occurs mainly because the IIS feature is disabled by default in your computer, you could open it in the control Panel.

  Control Panel ->> Programs ->> Programs and Features ->> Turn Windows features on or off ->> Internent Information Services

  

  If you have any other concern regarding this issue, please feel free to let me know.

  Best regards,
  Youjun Tang

  ---

  We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
  
  Click
  HERE to participate the survey.

  • Marked as answer by

    Thursday, September 18, 2014 2:12 AM