Can't access localhost / iis after installing Oracle and loopback adapter
I recently installed Oracle and the required Loopback adapter from Microsoft which worked great. However, this seems to have distorted IIS (or at least its interaction with Visual Studio) in some way. I can no longer connect to localhost or 127.0.0.1 and I cant even open a web project in Visual Studio 2008 (which worked well) getting the error "Local IIS URL http: // localhost / MyProject specified for web -project. MyProject is not configured. To open this project, you need to configure a virtual directory. Do you want to create this directory now? " I click yes, then it gives an error that "could not find server http: // localhost on current machine".
IIS is running and I can connect to the default IIS website and other inetput / wwwroot content at localhost: 1122.
I tried disabling the loopback adapter and commenting out the line I need to add to the hosts to get Oracle working, and while that stopped Oracle working, it didn't help with IIS / localhost.
edit: This turned out to be fixed by restoring the project from a backup, so it might have been a problem with the project itself.
a source to share
I am guessing this is a loopback adapter issue. You may need to restore your connection settings correctly. Check if the loopback adapter is properly disconnected and if the connection parameters are set from the control panel-> network connections. Edit: It would also be better to reboot the system after making all the necessary changes to the settings.
You can configure your local IIS to listen on a different port. Right-click the default website, the Website tab, then Advanced. Add for example 1234 as the TCP port.
Then you can connect like http: // localhost: 1234 / YourProject
You can open the website in Visual Studio from the file system and specify the new url in Project -> Property Pages -> Launch Options -> Use Custom Server.
a source to share
Something similar happened to me today in Windows XP and IIS 5. whatever it is. The problem is that the tool I installed created some virtual directories with no application name under the default website.
The solution was to open the IIS snap-in, right-click and select Properties for the offending virtual directories, and compose the Application Name in the Virtual Directory tab of the Properties dialog box that appears. It didn't matter what I called it if the default website didn't have a virtual directory with an empty application name.
a source to share