Updating the C# solution from VS2013 to VS2017 not working in IIS deployment

Question

1.00/5 (1 vote)

See more:

I have a C# project developed using VS2013 and that solution has been deployed in my IIS. Its working fine without any issues.

I had updated the solution to make use of VS2017.
I have fixed the build issues by adding latest references accordingly.
I am able to debug the solution successfully.
But while I deploy the new solution to IIS, home page is not loading.

I am getting http 401 error.

What I have tried:

<HintPath>..\packages\Microsoft.Web.Infrastructure.2.0.0\lib\net40\Microsoft.Web.Infrastructure.dll</HintPath>

 <Reference Include="System.Net" />
    <Reference Include="System.Web.Helpers, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
      <HintPath>..\packages\Microsoft.AspNet.WebPages.2.0.20710.0\lib\net40\System.Web.Helpers.dll</HintPath>

Posted 12-May-24 23:13pm

Chinnadurai05

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2024-05-12T23:26:00

Start by looking for what http 401 error[^] actually means - it's pretty simple!

Quote:
You may see the “Error code 401” if you try to access an outdated or misspelled URL. It means that the URL is non-existent, and the server may return a server error “401 Unauthorized Access”. Maybe you saved the page address in your browser, but the page address has been changed, or it has been deleted.

I'd start by looking at the Page Load method, and checking all URL's there, and then do the same for all config files.
If they all look right and appear to work, check the folder's you code is using and the user permissions on those folders - remember that websites don't run under your "normal user" account, but a specific account for IIS. If you have migrated this site to a new server (and that's likely given you are probably upgrading the .NET version) then you may have missed some folder permissions.