IIS 7.0 serves up nothing but blank pages on localhost

I was happily running IIS 6 on XP SP2 and then I upgraded to Windows
Ultimate. It seems to have upgraded me to IIS 7 at the same time.
Regardless of what I try to browse on localhost, IIS 7 always just serves up
a blank page. Anybody got any clues?

I have the exact same issues. And I re-installed iis 7.0 in my Vista Business
many
times still every time get the same result- http://localhost responds blank
page. I
wondered if this anything related to IUSR_xxxx(where xxxx is my machine
name) or
ASPNET account permissions??

Any ideas?? Please help...

"BillH" wrote:

> I was happily running IIS 6 on XP SP2 and then I upgraded to Windows
> Ultimate. It seems to have upgraded me to IIS 7 at the same time.
> Regardless of what I try to browse on localhost, IIS 7 always just serves up
> a blank page. Anybody got any clues?

For me it turned out to be Skype. Skype optionally listens on port 80 and
you can to into Tools, Options, Connection and uncheck the box by "Use port
80 and 443 as alternatives for incoming connections".

Skype must have turned this back on during one of the upgrade installs or
something as I remember turning this off once before. Anyway, that was the
first of several problems I had to go through with the upgrade to get things
working like they did under IIS 6.0. When I get time I'm going to uninstall
7.0, rename the configuration file from 6.0, and then do a clean install to
set things up from there.

Good luck!
Bill

"Harrison6565" wrote:

> I have the exact same issues. And I re-installed iis 7.0 in my Vista Business
> many
> times still every time get the same result- http://localhost responds blank
> page. I
> wondered if this anything related to IUSR_xxxx(where xxxx is my machine
> name) or
> ASPNET account permissions??
>
> Any ideas?? Please help...
>
> "BillH" wrote:
>
> > I was happily running IIS 6 on XP SP2 and then I upgraded to Windows
> > Ultimate. It seems to have upgraded me to IIS 7 at the same time.
> > Regardless of what I try to browse on localhost, IIS 7 always just serves up
> > a blank page. Anybody got any clues?

Thanks for shedding the light, Bill. I went in to Tools|Options|Connections
but cannot see any checkbox by "Use port 80 and 443 as alternatives for
incoming
connections". Is that something under other tabs? And according to your
experience,
what are the other steps to resolve this issue.

Thanks,
-Harrison6565



"BillH" wrote:

> For me it turned out to be Skype. Skype optionally listens on port 80 and
> you can to into Tools, Options, Connection and uncheck the box by "Use port
> 80 and 443 as alternatives for incoming connections".
>
> Skype must have turned this back on during one of the upgrade installs or
> something as I remember turning this off once before. Anyway, that was the
> first of several problems I had to go through with the upgrade to get things
> working like they did under IIS 6.0. When I get time I'm going to uninstall
> 7.0, rename the configuration file from 6.0, and then do a clean install to
> set things up from there.
>
> Good luck!
> Bill
>
> "Harrison6565" wrote:
>
> > I have the exact same issues. And I re-installed iis 7.0 in my Vista Business
> > many
> > times still every time get the same result- http://localhost responds blank
> > page. I
> > wondered if this anything related to IUSR_xxxx(where xxxx is my machine
> > name) or
> > ASPNET account permissions??
> >
> > Any ideas?? Please help...
> >
> > "BillH" wrote:
> >
> > > I was happily running IIS 6 on XP SP2 and then I upgraded to Windows
> > > Ultimate. It seems to have upgraded me to IIS 7 at the same time.
> > > Regardless of what I try to browse on localhost, IIS 7 always just serves up
> > > a blank page. Anybody got any clues?

Hmmm. It's possible you have a different version of Skype than I do. I've
got version 2.5.0.151. The checkbox may be in a different place in an
earlier version or may not be an option. Or you could just exit skype and
see if that makes a difference. You might also google search skype and IIS
together. I got several hits that talked about the problem.

I found there were a number of changes I had to make in the configuration of
IIS 7.0 to get things to work properly. That's the reason I want to start
clean by renaming the configuration file and re-installing. I fear I didn't
write them down and would have trouble figuring them out as there were a
number of things I tried before I found ones that worked.

"Harrison6565" wrote:

> Thanks for shedding the light, Bill. I went in to Tools|Options|Connections
> but cannot see any checkbox by "Use port 80 and 443 as alternatives for
> incoming
> connections". Is that something under other tabs? And according to your
> experience,
> what are the other steps to resolve this issue.
>
> Thanks,
> -Harrison6565
>

Thanks for your prompt reply Bill. I actually went in to my browser(7.0) for
it
instead of the Skype. I do not have Skyped installed in my local box.
Normally I
would try to avoid to rename or twist the system files. So in this case I
think I
would refront my box to Windows Server 2003 which I'm familiar with as my
develop environment.

Best
-Harrison6565

"BillH" wrote:

> Hmmm. It's possible you have a different version of Skype than I do. I've
> got version 2.5.0.151. The checkbox may be in a different place in an
> earlier version or may not be an option. Or you could just exit skype and
> see if that makes a difference. You might also google search skype and IIS
> together. I got several hits that talked about the problem.
>
> I found there were a number of changes I had to make in the configuration of
> IIS 7.0 to get things to work properly. That's the reason I want to start
> clean by renaming the configuration file and re-installing. I fear I didn't
> write them down and would have trouble figuring them out as there were a
> number of things I tried before I found ones that worked.
>
> "Harrison6565" wrote:
>
> > Thanks for shedding the light, Bill. I went in to Tools|Options|Connections
> > but cannot see any checkbox by "Use port 80 and 443 as alternatives for
> > incoming
> > connections". Is that something under other tabs? And according to your
> > experience,
> > what are the other steps to resolve this issue.
> >
> > Thanks,
> > -Harrison6565
> >
>