search

aspnet / Tooling

Issue tracker and info on Visual Studio tooling for ASP.NET
Other
256 stars 124 forks source link

ASP.net Core publish to IIS Application fails (ERROR_USER_UNAUTHORIZED) #786

Open robalexclark opened 8 years ago

robalexclark commented 8 years ago

Trying to publish an asp.net core application from VS2015 update 3 to remote IIS fails with the following errors in the output log:

C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Publishing.targets(408,5): Error : Error Code: ERROR_USER_UNAUTHORIZED C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Publishing.targets(408,5): Error : More Information: Connected to the remote computer ("envigotestiis1") using the Web Management Service, but could not authorize. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Publishing.targets(408,5): Error : Error: The remote server returned an error: (401) Unauthorized. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Publishing.targets(408,5): Error : Error count: 1.

Here is my checklist: ASP.net core 1.0.1 hosting installed on remote IIS machine Publishing to application (not site): "Default Web Site/ExtranetManager" The web site already exists

Username and password ok (double/triple checked) and Validate Connection passes OK User is admin on remote machine Can preview changes OK in the publish tool I can successfully publish Silverlight applications to the same IIS site using VS2013 publish tool Tried using another admin account from a different machine with the same result.

BUT - if I publish to a website (not application) e.g. Default Web Site, it all works ok, which is why I think it is a bug(?)

mlorbetske commented 8 years ago

This looks quite a bit like https://github.com/aspnet/Tooling/issues/523#issuecomment-246324435, could you try adding <AuthType>NTLM</AuthType> to your pubxml to see if that takes care of it?