IIS Wont start after NAV install.

[CJM]

Recently I installed a copy of Norton Anti-Virus... well Norton Internet
Security 2003 actually.
Since then I havent been able to access my web server....

I checked in the Services MMC, and it say that the WWW Service is
'Starting'. Unfortunately it never makes it!
The Event log shows that several services try to start up (FTP, IIS Admin,
WWW etc), but that only the FTP service makes it.

I've unistalled, booted, re-installed IIS, but there is no difference.

Symantec told me to create a rule to allow traffic on port 80, but this
isn't any help.

Anybody had a similar problem? Anybody know how to troubleshoot this one?


Thanks

CJM

 

[Paul Lynch]

Recently I installed a copy of Norton Anti-Virus... well Norton Internet
Security 2003 actually.
Since then I havent been able to access my web server....

I checked in the Services MMC, and it say that the WWW Service is
'Starting'. Unfortunately it never makes it!
The Event log shows that several services try to start up (FTP, IIS Admin,
WWW etc), but that only the FTP service makes it.

I've unistalled, booted, re-installed IIS, but there is no difference.

Symantec told me to create a rule to allow traffic on port 80, but this
isn't any help.

Anybody had a similar problem? Anybody know how to troubleshoot this one?


Thanks

CJM

I think what you are seeing is similar to the symptoms described in
this KB article :

IIS Stops Responding After You Apply Updates
http://support.microsoft.com/?id=328512

One suggested workaround is to start the IIS services first then
configure your Norton Firewall afterwards so that it knows you are
already running IIS. A lot of people get caught out this way with
Zonealarm.


Regards,

Paul Lynch
MCSE

 

[Jeff Cochran]

Recently I installed a copy of Norton Anti-Virus... well Norton Internet
Security 2003 actually.
Since then I havent been able to access my web server....

I checked in the Services MMC, and it say that the WWW Service is
'Starting'. Unfortunately it never makes it!
The Event log shows that several services try to start up (FTP, IIS Admin,
WWW etc), but that only the FTP service makes it.

I've unistalled, booted, re-installed IIS, but there is no difference.

Symantec told me to create a rule to allow traffic on port 80, but this
isn't any help.

Anybody had a similar problem? Anybody know how to troubleshoot this one?

Uninstall Norton, reboot, don't reinstall Norton...

Sorry, but there are numerous issues with Norton/Symantec products,
and getting the configuration correct can be a nightmare. There are
plenty of alternative products with greater functionality for lower
cost.

The most common issue that might relate to your situation is that
Norton won't let IIS start until after Norton has started. If you set
the IIS Service to "manual" so it doesn't start automatically, you can
then try starting it after the system has booted and Norton is fully
functional.

If that works, you *may* be successful if you uninstall Norton, make
sure you have all the service packs and updtaes installed and that IIS
now starts, then reinstall Norton from scratch. At least until the
next service pack or other update makes you repeat the process.

Jeff

 

[CJM]

Thanks for all your suggestions...

However, I *appear* to have already fixed it!

I set the NIS services to manual, and rebooted, which allowed IIS to start
OK.

I then re-enabled the NIS service one by one and manually started them...

They worked fine and IIS continued to work...

So I rebooted.... and when I logged in, everything was working..


So I havent got a clue, what exactly fixed it all. Needless to say, if I
have ANY more problems, NAV will be straight in the bin.
My previous combination of Avast & ZA worked fine, so I'll be heading back
that way if there are more problems!

Thanks anyway.

Chris

 

[Paul Lynch]

Thanks for all your suggestions...

However, I *appear* to have already fixed it!

I set the NIS services to manual, and rebooted, which allowed IIS to start
OK.

I then re-enabled the NIS service one by one and manually started them...

They worked fine and IIS continued to work...

So I rebooted.... and when I logged in, everything was working..


So I havent got a clue, what exactly fixed it all. Needless to say, if I
have ANY more problems, NAV will be straight in the bin.
My previous combination of Avast & ZA worked fine, so I'll be heading back
that way if there are more problems!

Thanks anyway.

Chris

Chris,

You don't need to bin NAV, it just needs to know which programs are
allowed to talk to the outside world. You will get exactly the same
issue with ZA if and when you apply any updates which affect IIS.

Refer to the KB article I referenced for more information.


Regards,

Paul Lynch
MCSE