Ask Question. Asked 8 years, 11 months ago. Active 2 years, 11 months ago. Viewed 47k times. It builds fine on other machines, but here I get the following vague error How can I fix this? Improve this question. Add a comment. Active Oldest Votes. Here are two possibilities: The account building your project doesn't have access to the IIS config dir.
This might happen if you have an automated build identity with special permissions, or you if you need to start Visual Studio as an administrator. You don't have IIS installed at all on the new machine. Check to be sure the IIS config directory, and redirection. If not, you'll need to install IIS. Improve this answer. Running VS as Administrator takes care of the permissions problem.
Timothy Schoonover Timothy Schoonover 3, 3 3 gold badges 27 27 silver badges 42 42 bronze badges. May work for others.
Adam Naylor Adam Naylor 5, 9 9 gold badges 47 47 silver badges 67 67 bronze badges. Cameron Taggart Cameron Taggart 5, 4 4 gold badges 39 39 silver badges 65 65 bronze badges.
Vinicius Vinicius 1, 15 15 silver badges 18 18 bronze badges. AaA, that's really interesting. Did you find any official documentation on the subject? Visual Studio tried to access the OneDrive folder which was not synced to the local disk, and thus it failed. I noticed this problem after copying a project between 2 computers, perhaps it was caused by a duplicate IISExpress port or something trivial.
Close solution. Be sure "Apply changes to this folder, subfolders and files" is selected. Reopen VS solution. This might be related. After trying to solve an issue with a quick fix of changing IIS express inside visual studio from integrated to classic pipeline , I ended up not being able to use IIS express at all.
I tried all techniques above After that, I restarted visual studio and opened my project and it worked. I ran into this issue while trying to open another developer's solution after installing VS Update 3 RC. It created nested config folders:. I found that deleting one of the sites from the applicationhost. Especially there was a site name with a bracketed number suffix e.
I'm not sure yet if VS just had an issue with the brackets or that two sites pointed to the same directory. Either way deleting it made VS happy again. I had been struggling with this issue for a couple of days and nothing seemed to help - not even the instructions given in the top answers here.
But although VS recreated the directory structure and files in the new location the errors continued and running appcmd showed that it was still pointing at the old location by default. Example: I modified the SSL port. You will get a notification that your launchsettings. Accept that and you're good to go. Just try to change iis port in file launchSettings. Restart your VS and run the project again. Mine was caused by OneDrive. Apparently my documents folder is being synced to it.
What I did is changed the location of the documents folder through regedit and navigated to this path:. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. IISExpress 8 Cannot read configuration file redirection. Asked 8 years, 7 months ago. Active 3 months ago. Viewed 77k times.
I can't find anything Improve this question. Liam 24k 26 26 gold badges silver badges bronze badges. I found this question while traying to resolve an issue with Windows 10 and Visual Studio My fix was: my user could not write to my personal folder I'm in Administrators group and I'm the folder owner , so I went to security configurations and give myself full access.
Add a comment. Active Oldest Votes. What I had to do was the following: Close Visual Studio. Start Visual Studio again. Copy the original applicationhost. Improve this answer. Ian Kemp Ian Kemp I renamed the folder, launched VS, didn't work. Stopped VS, renamed the folder, restarted.
No error. So the shadow file was there, but Visual Studio couldn't read it. Then everything worked! Renamed the config folder to config. Show 2 more comments. Not working smart. Thank you. I did as mentioned an error is gone, Thanks alot for fix — Pankaj Singh. Deva Deva 3 3 silver badges 2 2 bronze badges. In the Export Configuration dialog box, type the path to the directory where you want to export the configuration files in the Physical path box, type and confirm the encryption password, and then click OK.
When the Export Configuration dialog box appears, click OK. In the Shared Configuration pane, select the Enable shared configuration option.
In the Physical path box, type the path to the shared configuration files, type the account name with permissions to access the shared configuration files in the User name box, type the account's password in the Password box, and then type the account password again in the Confirm password box. In the Enter encryption key password box on the Encryption Keys Password dialog box, type the password for the encryption key that you created in step 5, and then click OK.
In each of the Shared Configuration dialog boxes that appear, click OK to close the dialogs. The following code example shows how to configure IIS 7 to share configuration files and encryption keys to a shared directory on the network. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services.
Privacy policy. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Changes in IIS 7. When set to false , change notifications will continue be used as they were in IIS 7. IIS 8. IIS 7.
0コメント