IIS not starting with XP pro SP2

I have a little test site running on the IBM Thinkpad that I’m writing
this message on, using IIS and XP Professional, and using a Dynamic DNS
service with port 8080 as I’m using my cable connection. Last night I
allowed SP2 to be installed, and found access to my site had gone, and
that's when a Google search brought me to this link.
It finally occurred to me that I hadn’t got the message about Windows
Firewall not being activated, which had happened when I’d installed SP2
on a machine running Symantic’s firewall software, so I checked this
morning and found I’d got the original firewall that came with the
laptop, plus the Windows Firewall. Going into Control Panel, Security,
Windows Firewall, Exceptions tab, and adding port 8080 got me back on
line.
This may not be the solution to some other people’s problem, but it
solved mine (well, not all of them …

Geoff Canham




*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

GUY, YOU ROCK! THIS WORKED and seems to be working for now. THANKS A LOT.
Consider this solved. Thanks for the info.

gr33n3ggz

"Guy" wrote:

 > Microsoft solved my problem yesterday.
 > All is included in incident number SRX041209603253.
 > The Microsoft support rep went through the following:
 > - had me stop and put in manual start mode all non-Microsoft services;
 > - IISAdmin would not restart;
 > - Downloaded the AUthdiag tool, ran it and fixed all problems found;
 > - IISAdmin would not restart;
 > - follow steps in article ID 271071 at
<font color=purple> > <a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?scid=kb;en-us;271071</font" target="_blank">http://support.microsoft.com/default.aspx?scid=kb;en-us;271071</font</a>>
 > - IISAdmin would not restart;
 > - Set the "Remote Procedure Call (RPC)" service to Log On as "Local System
 > account";
 > - reboot (because RPC can not be restarted;
 > - IISAdmin now works correctly.
 >
 > The support rep told me to do the exact same steps and try to restart
 > IISAdmin after each, on the other systems with the same problem.
 >
 > Hope this helps.
 > But I suggest you contact Microsoft an refer to the ticket (SRX041209603253)
 > before trying this, since it is a long process ~2 hours.
 >
 > Regards,
 > Guy
 >
 > "Ben Strackany" wrote:
 >
  > > Is IIS running as a domain account instead of a local user? Does the account
  > > name exist locally and at the domain level?
  > >
  > > --
  > > Ben Strackany
<font color=green>  > > <a style='text-decoration: underline;' href="http://www.developmentnow.com</font" target="_blank">www.developmentnow.com</font</a>>
  > >
  > >
  > > "gr33n3ggz" <gr33n3ggz RemoveThis @discussions.microsoft.com> wrote in message
  > > news:90390BBB-DCDD-4E7A-A234-A3260DF333D6@microsoft.com...
   > > > Here is the deal. I installed a fresh copy XP pro with SP2 installed all
  > > the
   > > > apps like IIS, VB 6, VB.NET, Office 2k3, Symantec VS, then I configured
  > > the
   > > > IIS to our standards and ran our software for 3 days. THEN I joined the
  > > PC
   > > > to the domain and had a developer login and BAM, nothing within IIS works,
   > > > the services anything. So my conclusion is it must be a domain policy
   > > > thing???
   > > >
   > > > Does anyone have any idea what might be conflicting with IIS once joined
  > > to
   > > > the domain? Note** We have the security settings for SP2's firewall
   > > > disabled as not to have any problems with SMS 2k3, WUS, etc.
   > > >
   > > > Any thoughts?
   > > >
   > > > gR33n3gGz
   > > > 12/20/04
   > > >
   > > > - - - - - - - - - - - - - - - - - - -
   > > >
   > > > "gr33n3ggz" wrote:
   > > >
   > > > > I am a domain admin at a software development company. All our
  > > development
   > > > > desktops are running IIS, SQL server, VS6, and VS.net. From a clean
  > > install
   > > > > of xp with sp2 we install IIS and it runs. We have the Firewall
  > > disabled and
   > > > > the only type of symantec product we run is VS. However after a couple
   > > > > reboots IIS gets killed with this:
   > > > > The IIS Admin service hung on starting.
   > > > >
   > > > > Then we get.....
   > > > >
   > > > > The IIS Admin service terminated with service-specific error 2147549183
   > > > > (0x8000FFFF).
   > > > >
   > > > > Then...
   > > > >
   > > > > The Simple Mail Transfer Protocol (SMTP) service depends on the IIS
  > > Admin
   > > > > service which failed to start because of the following error:
   > > > > After starting, the service hung in a start-pending state.
   > > > >
   > > > > And...
   > > > >
   > > > > The World Wide Web Publishing service depends on the IIS Admin service
  > > which
   > > > > failed to start because of the following error:
   > > > > After starting, the service hung in a start-pending state.
   > > > >
   > > > > Finally when i go into services and try to manually start IIS Admin i
  > > get:
   > > > >
   > > > > Windows could not start IIS Admin on Local Computer. For more
  > > information,
   > > > > review the System Even Log. This this is a non-Microsoft service,
  > > contact
   > > > > the service vendor, and refer to service-specific error
  > > code -2147418113.
   > > > >
   > > > > This also happens if we install XP SP2 from SP1.
   > > > >
   > > > > Any ideas?
  > >
  > >
  > ><!-- ~MESSAGE_AFTER~ -->