If You Trust the Server Connect Again and Allow Untrusted Certificates

Publishing an ASP.Internet Core Web Application to IIS using Visual Studio 2019

I'k a developer at middle, so I'thou constantly keeping up with the latest technologies. currently I'one thousand developing 'Time and Nib', an ASP.NET Core Web Application. The application is based on Microsoft .Internet Cadre 5.0 (5.03 to be exact). Well, developing the awarding is one thing, the other thing is to publish the application on an IIS (net information server). There are some more than posts about this topic, yous can find them by searching or using the tags.

Beneath are some errors and the solutions applied for them. The post is mainly for me, so that the next fourth dimension i try i have a place to read how i solved all the issues i encountered the last time.

Failure I

Severity Code Clarification Project File Line Suppression State
Error Web deployment chore failed. (Connected to the remote calculator ("192.168.177.50") using the specified procedure ("Web Management Service"), but could not verify the server's certificate. If you trust the server, connect again and let untrusted certificates. Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CERTIFICATE_VALIDATION_FAILED.)

Connected to the remote computer ("192.168.177.50") using the specified process ("Web Direction Service"), merely could non verify the server'due south certificate. If y'all trust the server, connect again and let untrusted certificates. Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CERTIFICATE_VALIDATION_FAILED.
The underlying connectedness was closed: Could not institute trust relationship for the SSL/TLS secure channel.
The remote document is invalid according to the validation procedure. TimeAndBill 0

Solution

Adding <AllowUntrustedCertificate> Attribute to IISProfile.pubxml

Failure 2

Severity Code Clarification Project File Line Suppression Land
Error Web deployment task failed. (The SQL provider cannot run because of a missing dependency. Please brand certain that Microsoft SQL Server Management Objects (Version 10 or higher) is installed. Learn more than at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_SMO_NEEDED_FOR_SQL_PROVIDER.) TimeAndBill

Solution

Using Spider web Platform Installer – at the time of the post the version is 5.i

In Web Platform Installer 5.1 -> Install SQL Server Shared Management Objects (2012 on Vista and up) or (2010 on XP or 2003 server)

well, I don't know if information technology'southward a good thought to install a software that was released in 2012. Just what can y'all practice, Microsoft has pulled all the resources/man power for the deject, there will probably exist a more current version of this software component in operation. eat or dice, nosotros say in German.

Failure Iii

This was really a real pain in the .. you know.

Severity Code Description Projection File Line Suppression State
Mistake Web deployment task failed. (Could not connect to the remote computer ("192.168.177.fifty") using the specified process ("Spider web Direction Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Acquire more at: https://become.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.)
Brand certain the site that you are deploying to is a valid site on the destination server. If the outcome is not resolved, delight contact your server administrator.
Error details:
Could not connect to the remote figurer ("192.168.177.50") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Spider web Management Service") is started on the remote figurer. Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.
The remote server returned an error: (550). TimeAndBill 0

If you lot follow the mentioned link you get:

ERROR_COULD_NOT_CONNECT_TO_REMOTESVC

Diagnosis: Web Deploy cannot connect to the remote service.

Resolution: Ensure that:

1. You can ping the remote car
2. That the msdepsvc or wmsvc service is started on the remote server.
3. Your firewall is non blocking incoming connections of your ports on the destination. If you used the default installation, so information technology would be eighty for msdepsvc and 8172 for wmsvc.

To test one & 3 you lot tin can practise in FlowPowerShell:

Exam-NetConnection -ComputerName 192.168.177.50 -Port 8172          

and for 2:

so that wasn't the trouble.
i found this one: https://stackoverflow.com/questions/18739342/web-deploy-results-in-mistake-could-not-connect-to-remotesvc

https://stackoverflow.com/a/20478804/270085

and that solved the problem for the moment -> i had site name: TimeAndBill -> when i inverse it, the web app got published.

Failure IV

HTTP Fault 500.32 – Failed to load .NET Core host

Solution

In IIS -> Default Web Site -> Advanced Settings -> (General) Section -> Application Pool -> Choose DotNetCore as the App Pool

-> if you don't have this option -> Create an App Puddle named DotNetCore

in order to practice that: In IIS -> Application Pools -> Add Application Puddle

Once created the Application pool -> Advanced Settings -> Enable 32-Bit Applications -> True

Well, this shows how complicated publishing an asp.net cadre web app to an IIS is. As always, feel gratuitous to comment.

hatfielditell1953.blogspot.com

Source: https://blog.solvia.ch/2021/03/05/publishing-an-asp-net-core-web-application-to-iis-using-visual-studio-2019/