IIS not starting with XP pro SP2

If you have Norton firewall running, try remove it and test.

--
Regards,
Bernard Cheah
<a style='text-decoration: underline;' href="http://www.tryiis.com/" target="_blank">http://www.tryiis.com/</a>
<a style='text-decoration: underline;' href="http://support.microsoft.com/" target="_blank">http://support.microsoft.com/</a>
<a style='text-decoration: underline;' href="http://www.msmvps.com/bernard/" target="_blank">http://www.msmvps.com/bernard/</a>



"gr33n3ggz" <gr33n3ggz DeleteThis @discussions.microsoft.com> wrote in message
news:D482FB39-2AFA-4778-B269-02DD233D1D15@microsoft.com...
 >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~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

Can I suggest you remove that as well :p

--
Regards,
Bernard Cheah
<a style='text-decoration: underline;' href="http://www.tryiis.com/" target="_blank">http://www.tryiis.com/</a>
<a style='text-decoration: underline;' href="http://support.microsoft.com/" target="_blank">http://support.microsoft.com/</a>
<a style='text-decoration: underline;' href="http://www.msmvps.com/bernard/" target="_blank">http://www.msmvps.com/bernard/</a>



"gr33n3ggz" <gr33n3ggz DeleteThis @discussions.microsoft.com> wrote in message
news:7FD2D597-0920-4588-9BF7-144E6DB55F95@microsoft.com...
 > Thanks however there is nothing running except SYmantec Virus Scan, no
 > firewalls and the SP2 firewall is disabled within services.
 >
 > gr33n3ggz
 > ---------
 >
 > "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~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

"gr33n3ggz" <gr33n3ggz.RemoveThis@discussions.microsoft.com> wrote in message
news:D482FB39-2AFA-4778-B269-02DD233D1D15@microsoft.com...
 >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).

Very fatal error.
Don't you just love Symantec?<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

Symantec was removed and still no deal. AHHHHH.





"Egbert Nierop (MVP for IIS)" wrote:

 >
 >
 > "gr33n3ggz" <gr33n3ggz RemoveThis @discussions.microsoft.com> wrote in message
 > news:D482FB39-2AFA-4778-B269-02DD233D1D15@microsoft.com...
  > >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).
 >
 > Very fatal error.
 > Don't you just love Symantec?
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

Hi,

I have the same problem. I opened a support incident with MS yesterday
afternoon. I was first told this was a clash between my antivirus and SP2.
I was then instructed by the MS support technician to:
- uninstall my antivirus;
- uninstall IIS;
- manually remove some IIS files;
- reinstall IIS.

It worked at first. I rebooted a few times and all was OK.
This morning I tried restarting IISAdmin and got the same error.
So the problem was not solved by the clean IIS install and it is not a clash
with the antivirus since I have not yet re-installed it.

Thought you would be interested to hear that others are suffering with you.

Regards,
Guy

"gr33n3ggz" wrote:

 > Symantec was removed and still no deal. AHHHHH.
 >
 >
 >
 >
 >
 > "Egbert Nierop (MVP for IIS)" wrote:
 >
  > >
  > >
  > > "gr33n3ggz" <gr33n3ggz.TakeThisOut@discussions.microsoft.com> wrote in message
  > > news:D482FB39-2AFA-4778-B269-02DD233D1D15@microsoft.com...
   > > >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).
  > >
  > > Very fatal error.
  > > Don't you just love Symantec?
  > >
  > >
  > ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

"Guy" <gdifr.RemoveThis@online.nospam> wrote in message
news:FDB75483-8B6D-4FF5-A3B5-7D99325CD18F@microsoft.com...
 > Hi,
 >
 > I have the same problem. I opened a support incident with MS yesterday
 > afternoon. I was first told this was a clash between my antivirus and
 > SP2.
 > I was then instructed by the MS support technician to:
 > - uninstall my antivirus;
 > - uninstall IIS;
 > - manually remove some IIS files;
 > - reinstall IIS.
 >
 > It worked at first. I rebooted a few times and all was OK.
 > This morning I tried restarting IISAdmin and got the same error.
 > So the problem was not solved by the clean IIS install and it is not a
 > clash
 > with the antivirus since I have not yet re-installed it.
 >
 > Thought you would be interested to hear that others are suffering with
 > you.
 >
 > Regards,
 > Guy
 >
 > "gr33n3ggz" wrote:
 >
  >> Symantec was removed and still no deal. AHHHHH.


ps: There is a known problem with custom C++ component that are created
using Server.CreateObject (instead of createobject). They will cause IIS
crash if you stop the service. This type of crashing,
corrupts the metabase.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

"Guy" <gdifr.DeleteThis@online.nospam> wrote in message
news:FDB75483-8B6D-4FF5-A3B5-7D99325CD18F@microsoft.com...
 > Hi,
 >
 > I have the same problem. I opened a support incident with MS yesterday
 > afternoon. I was first told this was a clash between my antivirus and
 > SP2.
 > I was then instructed by the MS support technician to:
 > - uninstall my antivirus;
 > - uninstall IIS;
 > - manually remove some IIS files;
 > - reinstall IIS.
 >
 > It worked at first. I rebooted a few times and all was OK.
 > This morning I tried restarting IISAdmin and got the same error.
 > So the problem was not solved by the clean IIS install and it is not a
 > clash
 > with the antivirus since I have not yet re-installed it.

There must be something in common between both of your installations.
Please mention what else you did install on IIS?
Do you use ODBC? OleDB/ ADO
Exchange?
Some type of components?
ASPX?
ASP?

--
compatible web farm Session replacement for Asp and Asp.Net
<a style='text-decoration: underline;' href="http://www.nieropwebconsult.nl/asp_session_manager.htm" target="_blank">http://www.nieropwebconsult.nl/asp_session_manager.htm</a>


 > Thought you would be interested to hear that others are suffering with
 > you.
 >
 > Regards,
 > Guy
 >
 > "gr33n3ggz" wrote:
 >
  >> Symantec was removed and still no deal. AHHHHH.
  >>
  >>
  >>
  >>
  >>
  >> "Egbert Nierop (MVP for IIS)" wrote:
  >>
   >> >
   >> >
   >> > "gr33n3ggz" <gr33n3ggz.DeleteThis@discussions.microsoft.com> wrote in message
   >> > news:D482FB39-2AFA-4778-B269-02DD233D1D15@microsoft.com...
   >> > >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).
   >> >
   >> > Very fatal error.
   >> > Don't you just love Symantec?
   >> >
   >> >
   >> ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

Now, try reinstall IIS in the following steps:
a) uninstall IIS (safe or normal mode)
b) Remove files and folders
%windir%/system32/inetsvr/
/inetpub/
%windir%/iisx.log (x=5 for w2k, 6 for XP, Win03)
(use safe mode to delete)
c) reboot, reinstall IIS, repatch machines


--
Regards,
Bernard Cheah
<a style='text-decoration: underline;' href="http://www.tryiis.com/" target="_blank">http://www.tryiis.com/</a>
<a style='text-decoration: underline;' href="http://support.microsoft.com/" target="_blank">http://support.microsoft.com/</a>
<a style='text-decoration: underline;' href="http://www.msmvps.com/bernard/" target="_blank">http://www.msmvps.com/bernard/</a>



"gr33n3ggz" <gr33n3ggz.RemoveThis@discussions.microsoft.com> wrote in message
news:68330771-59F0-4A8B-8FD4-F81477B714C4@microsoft.com...
 > Symantec was removed and still no deal. AHHHHH.
 >
 >
 >
 >
 >
 > "Egbert Nierop (MVP for IIS)" wrote:
 >
  >>
  >>
  >> "gr33n3ggz" <gr33n3ggz.RemoveThis@discussions.microsoft.com> wrote in message
  >> news:D482FB39-2AFA-4778-B269-02DD233D1D15@microsoft.com...
   >> >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).
  >>
  >> Very fatal error.
  >> Don't you just love Symantec?
  >>
  >>
  >><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

I think the point in common is that we both have Visual Studio 6.
I use ASP. I do not have any server.createobjects.
We are 3 at work here with XP SP2 and we all have the same problem.

Guy

"Egbert Nierop (MVP for IIS)" wrote:

 > "Guy" <gdifr.RemoveThis@online.nospam> wrote in message
 > news:FDB75483-8B6D-4FF5-A3B5-7D99325CD18F@microsoft.com...
  > > Hi,
  > >
  > > I have the same problem. I opened a support incident with MS yesterday
  > > afternoon. I was first told this was a clash between my antivirus and
  > > SP2.
  > > I was then instructed by the MS support technician to:
  > > - uninstall my antivirus;
  > > - uninstall IIS;
  > > - manually remove some IIS files;
  > > - reinstall IIS.
  > >
  > > It worked at first. I rebooted a few times and all was OK.
  > > This morning I tried restarting IISAdmin and got the same error.
  > > So the problem was not solved by the clean IIS install and it is not a
  > > clash
  > > with the antivirus since I have not yet re-installed it.
 >
 > There must be something in common between both of your installations.
 > Please mention what else you did install on IIS?
 > Do you use ODBC? OleDB/ ADO
 > Exchange?
 > Some type of components?
 > ASPX?
 > ASP?
 >
 > --
 > compatible web farm Session replacement for Asp and Asp.Net
<font color=purple> > <a style='text-decoration: underline;' href="http://www.nieropwebconsult.nl/asp_session_manager.htm</font" target="_blank">http://www.nieropwebconsult.nl/asp_session_manager.htm</font</a>>
 >
 >
  > > Thought you would be interested to hear that others are suffering with
  > > you.
  > >
  > > Regards,
  > > Guy
  > >
  > > "gr33n3ggz" wrote:
  > >
   > >> Symantec was removed and still no deal. AHHHHH.
   > >>
   > >>
   > >>
   > >>
   > >>
   > >> "Egbert Nierop (MVP for IIS)" wrote:
   > >>
   > >> >
   > >> >
   > >> > "gr33n3ggz" <gr33n3ggz.RemoveThis@discussions.microsoft.com> wrote in message
   > >> > news:D482FB39-2AFA-4778-B269-02DD233D1D15@microsoft.com...
   > >> > >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).
   > >> >
   > >> > Very fatal error.
   > >> > Don't you just love Symantec?
   > >> >
   > >> >
   > >> >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

We don’t use C++, so that should be okay. We do use an ODBC connections and
the ADO components. We are also using ASP and some ASPX.

gr33n3ggz

- - - - - - - - - - - - -

"Egbert Nierop (MVP for IIS)" wrote:

 > "Guy" <gdifr.RemoveThis@online.nospam> wrote in message
 > news:FDB75483-8B6D-4FF5-A3B5-7D99325CD18F@microsoft.com...
  > > Hi,
  > >
  > > I have the same problem. I opened a support incident with MS yesterday
  > > afternoon. I was first told this was a clash between my antivirus and
  > > SP2.
  > > I was then instructed by the MS support technician to:
  > > - uninstall my antivirus;
  > > - uninstall IIS;
  > > - manually remove some IIS files;
  > > - reinstall IIS.
  > >
  > > It worked at first. I rebooted a few times and all was OK.
  > > This morning I tried restarting IISAdmin and got the same error.
  > > So the problem was not solved by the clean IIS install and it is not a
  > > clash
  > > with the antivirus since I have not yet re-installed it.
 >
 > There must be something in common between both of your installations.
 > Please mention what else you did install on IIS?
 > Do you use ODBC? OleDB/ ADO
 > Exchange?
 > Some type of components?
 > ASPX?
 > ASP?
 >
 > --
 > compatible web farm Session replacement for Asp and Asp.Net
<font color=purple> > <a style='text-decoration: underline;' href="http://www.nieropwebconsult.nl/asp_session_manager.htm</font" target="_blank">http://www.nieropwebconsult.nl/asp_session_manager.htm</font</a>>
 >
 >
  > > Thought you would be interested to hear that others are suffering with
  > > you.
  > >
  > > Regards,
  > > Guy
  > >
  > > "gr33n3ggz" wrote:
  > >
   > >> Symantec was removed and still no deal. AHHHHH.
   > >>
   > >>
   > >>
   > >>
   > >>
   > >> "Egbert Nierop (MVP for IIS)" wrote:
   > >>
   > >> >
   > >> >
   > >> > "gr33n3ggz" <gr33n3ggz.RemoveThis@discussions.microsoft.com> wrote in message
   > >> > news:D482FB39-2AFA-4778-B269-02DD233D1D15@microsoft.com...
   > >> > >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).
   > >> >
   > >> > Very fatal error.
   > >> > Don't you just love Symantec?
   > >> >
   > >> >
   > >> >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

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~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

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
<a style='text-decoration: underline;' href="http://www.developmentnow.com" target="_blank">www.developmentnow.com</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~ -->
 >> Stay informed about: IIS not starting with XP pro SP2 

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
<a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?scid=kb;en-us;271071" target="_blank">http://support.microsoft.com/default.aspx?scid=kb;en-us;271071</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=purple> > <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~ -->
 >> Stay informed about: IIS not starting with XP pro SP2