Cannot start Web Site with IIS on Vista. (http://localhost cannot be resolved.)

[jaay]

Hi all,

I’m using Vista Home Premium. (Clean install)

I add IIS from Windows Features. Then, I open http://localhost, but the IIS welcome page cannot be displayed.

I check the IIS Management Console; the Default Web Site is stopped.

I try to start it, but no luck because the pop-up shows error: Incorrect function. (Exception from HRESULT: 0x80070001).


What should I do to start the IIS Web Site? Any suggestion???

Thank you very very much… ;)

J.

[jaay]

Hi, again,

For additional info.....
There are 2 related records (an error report) in the Event Viewer:

1)
Description:
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix http://*:80/ for site 1. The site has been disabled. The data field contains the error number.

Log Name: System
Source: Microsoft-Windows-IIS-W3SVC
Date: 31/5/2550 20:05:37
Event ID: 1004
Task Category: None
Level: Error
Keywords: Classic
User: N/A

2)
Description:
Unable to bind to the underlying transport for [::]:80. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number.

Log Name: System
Source: Microsoft-Windows-HttpEvent
Date: 31/5/2550 20:05:37
Event ID: 15005
Task Category: None
Level: Error

[kenobewan]

Please give more details about the applcation and the server platform. Thanks.

[jaay]

Thanks "kenobewan" :)

But I ends up with formatting my computer because I have an urgent need to have the IIS run.

Again, thank you.




Ref. http://forums.iis.net/p/1116890/1733657.aspx

[kenobewan]

So you have resolved the problem?

[Burak]

Im having the same problem I'm running on vista and getting the following error on the event log

The Module DLL 'C:\Windows\System32\inetsrv\compstat.dll' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a x86 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.

Any Ideas