I had exactly the same problem when the organisation I worked for changed the network drive where they've mapped my My Documents folder (along with a bunch of others). It used to be on \machine1\myusername$ and was moved to \someothermachine\myusername$.
When I tried to fire up iisexpress in a console window from "C:\Program Files (x86)\IIS Express>" via a VS command prompt, it came back with
An error occurred while reading configuration information. Make sure that the configuration file \\machine1\myusername$\IISExpress\config\applicationhost.config exists, it is accessible, and contains valid configuration information.
Their script didn't bother to zip through the registry and update the pointers from the old "home" to the new one. So I ended up with missing files, duplicates in some cases, and rude messages along the lines of "this file is currently not available for use on this computer".
To fix it, I did the following:
- Located the root/base of my new "My documents" folder (now
\\someothermachine\myusername$
)
- Did a (manual, via regedit) registry search for keys, values and data for
\\machine1\myusername$\
and replaced it with the new version. This took a while, there were about 40-50 replacements.
- Rebooted.
I was then able to fire up iisexpress again, from the same console window. It re-registered the standard base website, and it's all working again.
I hope this helps someone else!