Is the "Default Website" configured with some non default settings ? (F.e. listen only on some IPs or listen only to specific header names)

Is the local iis reachable over the browser with the FQDN ? (Possibly the site should be excluded from a proxy).

Thanks for the response. 

No filters on the website and I can reach the default "Under Construction" webpage using the FQDN.

I very much appreciate the suggestions but there is no proxy involved. 

Here are the errors in the install log (hostname edited but is correct in the error log).  Ring any bells for anyone?  I've checked as many ways as I can think to and the FQDN comes up as valid. 

<event date="Mar 14 15:58:02 +00:00" severity="2" hostName="XXXXXXXX" source="Symantec.Installation.UI.NSApplicationIdentityView.ValidateSslCert" module="SymantecInstallationManager.exe" process="SymantecInstallationManager" pid="1580" thread="1" tickCount="42375484"><![CDATA[Unable to validate fully qualified web domain name is current server]]></event>

<event date="Mar 14 15:58:02 +00:00" severity="1" hostName="XXXXXXXX" source="Symantec.Installation.UI.NSApplicationIdentityView+IISWebSite.checkWeb" module="SymantecInstallationManager.exe" process="SymantecInstallationManager" pid="1580" thread="1" tickCount="42375500"><![CDATA[Exception trying to access the web site

Has anyone found a solution to this? I'm runing into the same error.

Thanks,
Tom

I've had a long ticket running with NS Support.  They've been trying hard to find the cause, but so far without success.  It appears to be an issue where the NS installer is mistakenly detecting an SSL certificate (there were none on this server) and when it can't figure out the FQDN from the non-existent certificate it throws the error.

don't provide any clues, how about on the Microsoft side. Do you see anything in the event, application or http error logs?

We went through all IIS, OS, and SIM logs with fine tooth comb.  The SIM logs hinted at the cert issue described above, but we were never able to find the culprit, despite much hard effort on the part of Symantec support.  We have surrendered and are now installing to another server.  The install worked fine on that other server.

typed too fast in different section please ignore previous comment

Been bashing my head on this same issue for some days...but had a breaktrough

To cut a long story short it turned out to be permissions on the system temp folder i.e. C:\Temp

Needed to add Network Service with full control and it sprang into life

Hope this helps

Sometimes our old friend FileMon (from Microsoft, previously SysInternals) can be of assistance.  Not sure if you can still download FileMon (Process Explorer has mostly overtaken the capabilities of that and RegMon), but ProcExplorer will do too to help identify any install "FAIL" issues, particularly due to permissions.

Thanks for sharing Mark!

I have to do this on nearly every 2003 server that is built for us (and there have been ALOT of them since we finally built real dev and test environments for Altiris...5 years after we implemented!).  Sometimes you can get by with just removing IIS and reinstalling it, but frequently this will result in a prompt coming up for the 2003 SP2 source files.

Hello,
I have the same problem with installation and I just tried to use hostname instead of FQDN and it worked. There is no needed to reinstall IIS or .NET or OS. Hope this will help you:)

We ran into the same problem and we uninstall IIS and reinstalled. We are running Server 2008 

Reinstalling a service pack and\or IIS? Are you using HTTPS, where a certificate will come into play?