Styjun

We are two immediate neighbors who forged our own powers to form concatenated relationship. Who are we?

Why do Thanos's punches not kill Captain America or at least cause some mortal injuries?

Juery Ui & Autocomplete error

Set a camera to free fall like a Rigid Body?

Early arrival in Australia, early hotel check in not available

Exception propagation: When to catch exceptions?

As programers say: Strive to be lazy

Is there enough time to Planar Bind a creature conjured by a 1-hour-duration spell?

Thesis' "Future Work" section – is it acceptable to omit personal involvement in a mentioned project?

How can I make a vertical rule that extends to the edges of an fbox?

Is the schwa sound consistent?

Does kinetic energy warp spacetime?

Can you book a one-way ticket to the UK on a visa?

How to deal with inappropriate comments during interviews for academic positions?

Was there a contingency plan in place if Little Boy failed to detonate?

find not returning expected files

What does i386 mean on macOS Mojave?

Find all edge self-avoiding path of a graph

Is it a Munchausen Number?

Cannot parse JSON object containing escape characters

Why can't RGB or bicolour LEDs produce a decent yellow?

What is the best way for a skeleton to impersonate human without using magic?

Is it a bad idea to replace pull-up resistors with hard pull-ups?

Renting a house to a graduate student in my department

“Opening and creating websites on iis requires running visual studio under an administrator account”

MSBuild doesn't copy references (DLL files) if using project dependencies in solutionHow to Run Visual Studio as Administrator by defaultError 'LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt' after installing Visual Studio 2012 Release PreviewCan you force Visual Studio to always run as an Administrator in Windows 8?Visual Studio debugging/loading very slowHow do I open an old MVC project in Visual Studio 2012 or Visual Studio 2013?Unable to launch the IIS Express Web serverSpecified argument was out of the range of valid values. Parameter name: siteUnable to launch the IIS Express Web server, Failed to register URL, Access is deniedVisual Studio 2017 error: Unable to start program, An operation is not legal in the current state

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

I'm seeing this error in a pop-up window when attempting to run/debug my web project from Visual Studio

The following error occurred when trying to configure IIS Express. Opening and creating websites on iis requires running visual studio under an administrator account

This happened completely out of the blue. One second I was working as normal, regularly going in and out of debug in my browser, then this error pops up. It happens when attempting to run any web project, and it doesn't matter if it's in debug, release mode or what.

Stuff I've tried:

• Run Visual Studio as Administrator


• Uninstall/Reinstall IIS Express (via "Turn Windows Features On or Off" in Control Panel)


• Update Visual Studio


• Delete project's .vs folder

But still the error persists.

Is there anything else I can reinstall, update or otherwise check?

Thanks.

visual-studio visual-studio-2017 iis-express

share|improve this question

asked Mar 23 at 11:19

Stuart AitkenStuart Aitken

141111

add a comment | 

0

I'm seeing this error in a pop-up window when attempting to run/debug my web project from Visual Studio

The following error occurred when trying to configure IIS Express. Opening and creating websites on iis requires running visual studio under an administrator account

This happened completely out of the blue. One second I was working as normal, regularly going in and out of debug in my browser, then this error pops up. It happens when attempting to run any web project, and it doesn't matter if it's in debug, release mode or what.

Stuff I've tried:

• Run Visual Studio as Administrator


• Uninstall/Reinstall IIS Express (via "Turn Windows Features On or Off" in Control Panel)


• Update Visual Studio


• Delete project's .vs folder

But still the error persists.

Is there anything else I can reinstall, update or otherwise check?

Thanks.

visual-studio visual-studio-2017 iis-express

share|improve this question

asked Mar 23 at 11:19

Stuart AitkenStuart Aitken

141111

add a comment | 

I'm seeing this error in a pop-up window when attempting to run/debug my web project from Visual Studio

The following error occurred when trying to configure IIS Express. Opening and creating websites on iis requires running visual studio under an administrator account

This happened completely out of the blue. One second I was working as normal, regularly going in and out of debug in my browser, then this error pops up. It happens when attempting to run any web project, and it doesn't matter if it's in debug, release mode or what.

Stuff I've tried:

• Run Visual Studio as Administrator


• Uninstall/Reinstall IIS Express (via "Turn Windows Features On or Off" in Control Panel)


• Update Visual Studio


• Delete project's .vs folder

But still the error persists.

Is there anything else I can reinstall, update or otherwise check?

Thanks.

visual-studio visual-studio-2017 iis-express

share|improve this question

asked Mar 23 at 11:19

Stuart AitkenStuart Aitken

141111

share|improve this question

asked Mar 23 at 11:19

Stuart AitkenStuart Aitken

141111

share|improve this question

asked Mar 23 at 11:19

Stuart AitkenStuart Aitken

141111

asked Mar 23 at 11:19

Stuart AitkenStuart Aitken

141111

asked Mar 23 at 11:19

Stuart AitkenStuart Aitken

141111

1 Answer
1

active

oldest

votes

0

Solved it by going through a day of hell, and to be honest the 'solution' was very brute force...

TL;DR: Fully deleting and reinstalling Visual Studio seemed to do the trick.

Since the usual methods weren't working, I tried a full reinstall of Visual Studio. That didn't help. I then tried a System Restore. That made everything far worse, with my project showing about 500 error messages!

I then undid the System Restore, completely deleted all traces of Visual Studio from my computer, reinstalled everything, then tried VS2019 preview edition, tried 2017 edition again, uninstalled and reinstalled NetCore 2.0, 2.1, 2.2... all just to get around the minefield of error messages I'd created for myself.

In the end I just needed to do a full NuGet clear and restore then run dotnet restore --force in the NPM console, after which all those error messages were gone. As well as this, the original IIS Administrator error was gone too, presumably fixed via the original reinstall of Visual Studio.

Lost a whole day to this quagmire.

share|improve this answer

edited Mar 24 at 14:43

answered Mar 23 at 11:30

Stuart AitkenStuart Aitken

141111

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55313167%2fopening-and-creating-websites-on-iis-requires-running-visual-studio-under-an-ad%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

0

Solved it by going through a day of hell, and to be honest the 'solution' was very brute force...

TL;DR: Fully deleting and reinstalling Visual Studio seemed to do the trick.

Since the usual methods weren't working, I tried a full reinstall of Visual Studio. That didn't help. I then tried a System Restore. That made everything far worse, with my project showing about 500 error messages!

I then undid the System Restore, completely deleted all traces of Visual Studio from my computer, reinstalled everything, then tried VS2019 preview edition, tried 2017 edition again, uninstalled and reinstalled NetCore 2.0, 2.1, 2.2... all just to get around the minefield of error messages I'd created for myself.

In the end I just needed to do a full NuGet clear and restore then run dotnet restore --force in the NPM console, after which all those error messages were gone. As well as this, the original IIS Administrator error was gone too, presumably fixed via the original reinstall of Visual Studio.

Lost a whole day to this quagmire.

share|improve this answer

edited Mar 24 at 14:43

answered Mar 23 at 11:30

Stuart AitkenStuart Aitken

141111

add a comment | 

0

Solved it by going through a day of hell, and to be honest the 'solution' was very brute force...

TL;DR: Fully deleting and reinstalling Visual Studio seemed to do the trick.

Since the usual methods weren't working, I tried a full reinstall of Visual Studio. That didn't help. I then tried a System Restore. That made everything far worse, with my project showing about 500 error messages!

I then undid the System Restore, completely deleted all traces of Visual Studio from my computer, reinstalled everything, then tried VS2019 preview edition, tried 2017 edition again, uninstalled and reinstalled NetCore 2.0, 2.1, 2.2... all just to get around the minefield of error messages I'd created for myself.

In the end I just needed to do a full NuGet clear and restore then run dotnet restore --force in the NPM console, after which all those error messages were gone. As well as this, the original IIS Administrator error was gone too, presumably fixed via the original reinstall of Visual Studio.

Lost a whole day to this quagmire.

share|improve this answer

edited Mar 24 at 14:43

answered Mar 23 at 11:30

Stuart AitkenStuart Aitken

141111

add a comment | 

Solved it by going through a day of hell, and to be honest the 'solution' was very brute force...

TL;DR: Fully deleting and reinstalling Visual Studio seemed to do the trick.

Since the usual methods weren't working, I tried a full reinstall of Visual Studio. That didn't help. I then tried a System Restore. That made everything far worse, with my project showing about 500 error messages!

I then undid the System Restore, completely deleted all traces of Visual Studio from my computer, reinstalled everything, then tried VS2019 preview edition, tried 2017 edition again, uninstalled and reinstalled NetCore 2.0, 2.1, 2.2... all just to get around the minefield of error messages I'd created for myself.

In the end I just needed to do a full NuGet clear and restore then run dotnet restore --force in the NPM console, after which all those error messages were gone. As well as this, the original IIS Administrator error was gone too, presumably fixed via the original reinstall of Visual Studio.

Lost a whole day to this quagmire.

share|improve this answer

edited Mar 24 at 14:43

answered Mar 23 at 11:30

Stuart AitkenStuart Aitken

141111

share|improve this answer

edited Mar 24 at 14:43

answered Mar 23 at 11:30

Stuart AitkenStuart Aitken

141111

answered Mar 23 at 11:30

Stuart AitkenStuart Aitken

141111

answered Mar 23 at 11:30

Stuart AitkenStuart Aitken

141111