-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
An assembly specified in the application dependencies manifest (RhWeb.deps.json) was not found #8792
Comments
HI... I am also having the same issue. Does anyone have a fix for this. |
I also hit this. For me, it had to do with the use of
in my .csproj when running in an environment that had installed a dotnetcore 2.0 runtime, but not an SDK. See docs on implicit store. The solution was adding the following to my .csproj:
Although it should be noted that installing the SDK also worked. |
^this. I upgraded to Asp.Net Core 2.0 as well in this week, and I was trying to deploy to my Azure app service. I don't have the option to install the SDK there. |
I have arch linux (not officially supported).
but So perhaps try to specify runtime identifier when you publish your application. |
I get these errors no matter what I do w/AspNetCore 2.0.3. I had to roll back to 2.0.0. |
Having similar issue after upgrading to 2.0.3 and publish to IIS. Was working in 2.0.0
|
@ctrl-brk I find that simply creating a new dotnetcore 2.0 mvc project in VS 2017 and then publishing to Azure results in this error when you try to run the app in Azure. Quite annoying as I did nothing but follow wizards. I did not find a solution yet, even after adding Microsoft.AspNetCore.Antiforgery via NuGet and republishing the project. |
I figured out the issue--I needed to install aspnetcore web hosting 2.0.3. dotnet restore installs aspnetcore 2.0.3, and we aren't doing standalone deployments, so the higher version couldn't find the libraries it needed. |
@cr41g1w OMG. I should've think about it. Thank you. |
@doctorhilarius what do you mean by |
with dotnet 2.0.3, I got the error after I deployed the app onto Azure Web Service. Adding |
I found dotnet/aspnetcore#2254. |
The issue seems to be with using dotnet at the command line to create the project. I originally created a dotnet core mvc project at the command line, then opened it in VS 2017 and published it to Azure. This did not run in Azure. I just tried again but this time I used the VS 2017 wizard to create the project and published it to Azure. This project runs perfectly fine in Azure. I will see if I can find the difference in these two projects as the output looks the same at first glance. |
Hi, same problem here: Error: switched from Now it works without any other changes. |
@alexzaytsev-newsroomly He most likely means this: https://aka.ms/dotnetcore-2-windowshosting This will help you, if you run your own IIS Server. |
sry, forgot to preview.... ;-) |
After a lot more messing about, it seems this dotnetcore 2.0 is very very buggy when you try to deploy to Azure. If you create a dotnet core 1.1 project in VS it will deploy and run perfectly. No matter how you create a 2.0 project, most of the time it will fail to run at all on Azure. |
Also started getting this error after upgrading
The solution was to downgrade |
nuget doesn't install aspnetcore windows server hosting 2.0.3. that has to be installed with: https://aka.ms/dotnetcore-2-windowshosting |
@doctorhilarius What do we need to do for Ubuntu? |
Having the same problem on ubuntu |
I'm also running into this while deploying to azure :\ |
I am also having same problem: Without success I:
can I install web-hosting package on ubuntu? if not what is the solution? |
The details for updating Linux servers running to run 2.0.3 are at https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.3.md#linux. In short, you need to update the same components you installed to get 2.0.0 on to the box, whether it was the .NET Core SDK ( |
A little further detail, this is the default behavior of the That package implicitly publishes your application without any of the ASP.NET Core assemblies, thus requiring that your server has them installed in the runtime store. You can disable this behavior if you wish but it will result in all of the ASP.NET Core runtime assemblies being deployed with your application, which is both quite large, and slower to start, as they assemblies won't be pre-JITed (CrossGen'ed). It is not entirely dissimilar to installing an update to .NET Framework on your dev box, targeting your application to use it, then deploying it to a server that hasn't yet been updated to that version of .NET Framework. The app will fail to start as the required version of the framework is not there. I appreciate this is more complicated than some might have expected, especially given they were offered an update to the package via NuGet and it works locally when you do this. We're currently investigating ways to simplify this in upcoming releases such that getting patches for ASP.NET Core when running on .NET Core will not require any project update at all, you'll simply need to install the patch release in all environments where you want it to be used. Hope that helps. |
@DamianEdwards I don't know do I understand you correctly. |
@maroallegro did you revert the changes to your project? You shouldn't need to install both Can you share your csproj file? Also, did you do a |
@DamianEdwards This is my first test of this app on linux so this bug is not connected with any feature which I implemented, I didn't revert it if you mean reverting to previous version (using git). I did Should i uninstall Sure, here is my .csproj file
I also tried to run
UPDATE |
@maroallegro have you deployed (via |
An update. I resaved my environment variables in azure and redeployed the same code and it appears to be up and running now, but getting lots of errors with jobs. I'm thinking something could have been cached? |
I spoke too soon, static landing page now loads but any other page errors out :... This is really annoying. <div class="content-container">
<fieldset><h4>More Information:</h4>
This error occurs when a CGI application does not return a valid set of HTTP headers, or when a proxy or gateway was unable to send the request to a parent gateway. You may need to get a network trace or contact the proxy server administrator, if it is not a CGI problem.
<p><a href="http://go.microsoft.com/fwlink/?LinkID=62293&IIS70Error=502,5,0x00000000,9200">View more information »</a></p>
<p>Microsoft Knowledge Base Articles:</p> and <div id="content">
<div class="content-container">
<h3>HTTP Error 502.5 - Bad Gateway</h3>
<h4>The specified CGI application encountered an error and the server terminated the process.</h4>
</div>
<div class="content-container">
<fieldset><h4>Most likely causes:</h4>
<ul> <li>The CGI application did not return a valid set of HTTP errors.</li> <li>A server acting as a proxy or gateway was unable to process the request due to an error in a parent gateway.</li> </ul>
</fieldset>
</div>
<div class="content-container">
<fieldset><h4>Things you can try:</h4>
<ul> <li>Use DebugDiag to troubleshoot the CGI application.</li> <li>Determine if a proxy or gateway is responsible for this error.</li> </ul>
</fieldset>
</div> |
@niemyjski check the event log (https://blogs.msdn.microsoft.com/benjaminperkins/2016/07/01/how-to-view-the-event-logs-of-your-azure-app-service/) to see if there's any more detail on what caused the ASP.NET Core IIS Module (ANCM) to crash. You should also enable ANCM logging to disk in the web.config to capture any console output that might provide clues (see https://docs.microsoft.com/en-us/aspnet/core/hosting/aspnet-core-module). You can also try running the application manually in the Kudu console to see if an error is displayed there. |
Had a same problem on vm server debian 8. |
Maybe the section how to use the Docker images should be updated with the instructions mentioned by @DamianEdwards EDIT: I then discovered the Docker images for aspnet core and they work fine on 2.0.3 |
Here's how I adapted the multi-stage build sample DockerFile for asp.net core 2.0.0.3.
|
It seems to me that this problem exists when the published application relies on a runtime store which is not available at the server it was deployed. What's unclear to me is if the hosting package alone should be enough or not. @DamianEdwards mentioned:
I have installed the dotnet-hosting-2.0.3-rhel.7-x64.rpm on CentOS using yum but the problem persists. Would it be correct to say that the only option now if using the metapackage is to install the SDK on the server? |
I experienced this issue because my dotnet SDK version was behind the Microsoft.AspNetCore.All packages version. Making the versions match (either by reverting the package or upgrading the host SDK) fixed my problem. Simple/stupid mistake to make but hopefully it will help someone. |
I also had this error when using the dockerfile generated by Visual Studio. With the docker file below my app is able to start with a nuget reference to Microsoft.AspNetCore.All version 2.0.3 and without the line
|
@alexandervantrijffel me too, do you have a fix for this? |
@faliqulamin the first line wasn't visible in the dockerfile I posted, that is fixed now. You can try that one. |
If there is further discussion necessary on this, please track it at https://github.com/aspnet/Home or some place more appropriate. |
@RussKeldorph which issue do you suggest to track? Why this one is closed? For me the issue is still having place when I build and run in Docker:
for any project with reference:
|
@evil-shrike I don't have another issue. I'm suggesting that this issue doesn't have anything to do with the .NET runtime so dotnet/coreclr is not the right place to track it. It seems to have more to do with ASP.NET or its SDK, so I recommend opening a new issue in an appropriate repo. If I'm mistaken in my assessment, please accept my apologies. |
el2iot2 thanks, your PropertyGroup xml code did it for me. I'm getting into docker and it showed me how to move on to the next phase and use the latest preview code from the insiders code. Thanks again for sharing, awesome. |
Guys, I tried it, really, I wanted to use NET Core because of cross-platform possibility, but I fed up., This chaos with the references, cannot even revive a simple application on another windows machine for hours. Thank you, anyway... |
I upgraded all my dependencies in the project and it solved the problem. |
Error: This happens when i deploy to azure app service .net 5 |
I got a weird error on IIS since I migrate my Asp.Net Core 1.1 to Asp.Net Core 2.0.
I publish with MSBuild interface.
I don't use ApplicationInsights.AspNetCore in my project....
Here is the error message.
The text was updated successfully, but these errors were encountered: