SharePoint Service Unavailable (Application Pool crashes)

I have a brand new (1 week old) installation of SBS 2003 but for some reason
I can not use the SharePoint web sites.

The web sites are installed and running ok in IIS but when I check the
Application Pools, DefaultAppPool, StsAdminAppPool and WsusPool are Stopped
due to an unspecified error. I can start them but as soon as I access the
companyweb website the DefaultAppPool and WsusPools crashes. The same thing
happens to the StsAdminAppPool when trying to access the SharePoint Cetral
Admin website.

the W3SVC service report loads of errors in the system event log but
microsoft has no information on the error codes;

This is what it looks like in the event log for the StsAdminAppPool:

A process serving application pool 'StsAdminAppPool' terminated
unexpectedly. The process id was '4168'. The process exit code was
'0xffffffff'.

A process serving application pool 'StsAdminAppPool' terminated
unexpectedly. The process id was '860'. The process exit code was
'0xffffffff'.

A process serving application pool 'StsAdminAppPool' terminated
unexpectedly. The process id was '2052'. The process exit code was
'0xffffffff'.

A process serving application pool 'StsAdminAppPool' terminated
unexpectedly. The process id was '5028'. The process exit code was
'0xffffffff'.

A process serving application pool 'StsAdminAppPool' terminated
unexpectedly. The process id was '5220'. The process exit code was
'0xffffffff'.

Application pool 'StsAdminAppPool' is being automatically disabled due to a
series of failures in the process(es) serving that application pool.


Thanks for any help!

Take a look at the following article and see if it can be of help
http://support.microsoft.com/kb/842493


--
Costas


"pmela" <pmela@discussions.microsoft.com> wrote in message
news:4D16159C-1E57-41D4-B20E-B0C42922DFE1@microsoft.com...
>I have a brand new (1 week old) installation of SBS 2003 but for some
>reason
> I can not use the SharePoint web sites.
>
> The web sites are installed and running ok in IIS but when I check the
> Application Pools, DefaultAppPool, StsAdminAppPool and WsusPool are
> Stopped
> due to an unspecified error. I can start them but as soon as I access the
> companyweb website the DefaultAppPool and WsusPools crashes. The same
> thing
> happens to the StsAdminAppPool when trying to access the SharePoint Cetral
> Admin website.
>
> the W3SVC service report loads of errors in the system event log but
> microsoft has no information on the error codes;
>
> This is what it looks like in the event log for the StsAdminAppPool:
>
> A process serving application pool 'StsAdminAppPool' terminated
> unexpectedly. The process id was '4168'. The process exit code was
> '0xffffffff'.
>
> A process serving application pool 'StsAdminAppPool' terminated
> unexpectedly. The process id was '860'. The process exit code was
> '0xffffffff'.
>
> A process serving application pool 'StsAdminAppPool' terminated
> unexpectedly. The process id was '2052'. The process exit code was
> '0xffffffff'.
>
> A process serving application pool 'StsAdminAppPool' terminated
> unexpectedly. The process id was '5028'. The process exit code was
> '0xffffffff'.
>
> A process serving application pool 'StsAdminAppPool' terminated
> unexpectedly. The process id was '5220'. The process exit code was
> '0xffffffff'.
>
> Application pool 'StsAdminAppPool' is being automatically disabled due to
> a
> series of failures in the process(es) serving that application pool.
>
>
> Thanks for any help!

Hi Costas,
Thanks for the tip but sadly it did not make any difference. I've set the
permissions as recomended in the link you sent me but with no effect. The
Application Pools still crash as soon as I try to access any of the web site
mentioned.

We're having a lot of problems with this server currently. For one thing, it
does not restart properly. It simply hangs on the shut down message and has
to be swithed off manually.

Any tips would be appreciated, I really do not want to reinstall this Server
as it was a pain in the ... to move all clients to the new domain. I don't
want to do it all over again.

"Costas" wrote:

> Take a look at the following article and see if it can be of help
> http://support.microsoft.com/kb/842493
>
>
> --
> Costas
>
>
> "pmela" <pmela@discussions.microsoft.com> wrote in message
> news:4D16159C-1E57-41D4-B20E-B0C42922DFE1@microsoft.com...
> >I have a brand new (1 week old) installation of SBS 2003 but for some
> >reason
> > I can not use the SharePoint web sites.
> >
> > The web sites are installed and running ok in IIS but when I check the
> > Application Pools, DefaultAppPool, StsAdminAppPool and WsusPool are
> > Stopped
> > due to an unspecified error. I can start them but as soon as I access the
> > companyweb website the DefaultAppPool and WsusPools crashes. The same
> > thing
> > happens to the StsAdminAppPool when trying to access the SharePoint Cetral
> > Admin website.
> >
> > the W3SVC service report loads of errors in the system event log but
> > microsoft has no information on the error codes;
> >
> > This is what it looks like in the event log for the StsAdminAppPool:
> >
> > A process serving application pool 'StsAdminAppPool' terminated
> > unexpectedly. The process id was '4168'. The process exit code was
> > '0xffffffff'.
> >
> > A process serving application pool 'StsAdminAppPool' terminated
> > unexpectedly. The process id was '860'. The process exit code was
> > '0xffffffff'.
> >
> > A process serving application pool 'StsAdminAppPool' terminated
> > unexpectedly. The process id was '2052'. The process exit code was
> > '0xffffffff'.
> >
> > A process serving application pool 'StsAdminAppPool' terminated
> > unexpectedly. The process id was '5028'. The process exit code was
> > '0xffffffff'.
> >
> > A process serving application pool 'StsAdminAppPool' terminated
> > unexpectedly. The process id was '5220'. The process exit code was
> > '0xffffffff'.
> >
> > Application pool 'StsAdminAppPool' is being automatically disabled due to
> > a
> > series of failures in the process(es) serving that application pool.
> >
> >
> > Thanks for any help!
>

Did you have any errors when you first installed the server? If not, did
you try to swap the memory modules just in case they are defective?

--
Costas


"pmela" <pmela@discussions.microsoft.com> wrote in message
news:5F958858-A75A-4C03-976A-9EE0C3A3A405@microsoft.com...
> Hi Costas,
> Thanks for the tip but sadly it did not make any difference. I've set the
> permissions as recomended in the link you sent me but with no effect. The
> Application Pools still crash as soon as I try to access any of the web
> site
> mentioned.
>
> We're having a lot of problems with this server currently. For one thing,
> it
> does not restart properly. It simply hangs on the shut down message and
> has
> to be swithed off manually.
>
> Any tips would be appreciated, I really do not want to reinstall this
> Server
> as it was a pain in the ... to move all clients to the new domain. I don't
> want to do it all over again.
>
> "Costas" wrote:
>
>> Take a look at the following article and see if it can be of help
>> http://support.microsoft.com/kb/842493
>>
>>
>> --
>> Costas
>>
>>
>> "pmela" <pmela@discussions.microsoft.com> wrote in message
>> news:4D16159C-1E57-41D4-B20E-B0C42922DFE1@microsoft.com...
>> >I have a brand new (1 week old) installation of SBS 2003 but for some
>> >reason
>> > I can not use the SharePoint web sites.
>> >
>> > The web sites are installed and running ok in IIS but when I check the
>> > Application Pools, DefaultAppPool, StsAdminAppPool and WsusPool are
>> > Stopped
>> > due to an unspecified error. I can start them but as soon as I access
>> > the
>> > companyweb website the DefaultAppPool and WsusPools crashes. The same
>> > thing
>> > happens to the StsAdminAppPool when trying to access the SharePoint
>> > Cetral
>> > Admin website.
>> >
>> > the W3SVC service report loads of errors in the system event log but
>> > microsoft has no information on the error codes;
>> >
>> > This is what it looks like in the event log for the StsAdminAppPool:
>> >
>> > A process serving application pool 'StsAdminAppPool' terminated
>> > unexpectedly. The process id was '4168'. The process exit code was
>> > '0xffffffff'.
>> >
>> > A process serving application pool 'StsAdminAppPool' terminated
>> > unexpectedly. The process id was '860'. The process exit code was
>> > '0xffffffff'.
>> >
>> > A process serving application pool 'StsAdminAppPool' terminated
>> > unexpectedly. The process id was '2052'. The process exit code was
>> > '0xffffffff'.
>> >
>> > A process serving application pool 'StsAdminAppPool' terminated
>> > unexpectedly. The process id was '5028'. The process exit code was
>> > '0xffffffff'.
>> >
>> > A process serving application pool 'StsAdminAppPool' terminated
>> > unexpectedly. The process id was '5220'. The process exit code was
>> > '0xffffffff'.
>> >
>> > Application pool 'StsAdminAppPool' is being automatically disabled due
>> > to
>> > a
>> > series of failures in the process(es) serving that application pool.
>> >
>> >
>> > Thanks for any help!
>>

Im not sure if these errors occured initially as I did not try to use
SharePoint. Retarting the computer, however, was working fine until a couple
of days ago.

Maybe i should mention there is an Microsoft SQL Server 2005 installed on
this machine as well. Thinking it might be this one that somehow interferes
with SP I tried to uninstall it but when I did "remove" from the "add/remove
programs" menu, the SQL Server entry just vanished. Nothing happened and the
server is still installed. I looked up instructions on how to remove the SQL
server manually, but when I try that I get an error message saying something
like:

"SQL Server setup can't inspect software installed due to the WMI
configuration on this Machine"

I searched MSDN for this error and found a batch fix posted by someone that
obviously had worked for several people. I ran it on the server and it
registered a lot of DLL libraries and did other stuff, Im not sure exactly
what, but It did not solve my problem. I still can't uninstall SQL Server
manually OR run the SQL Server installation from CD due to the WMI
configuration.

"Costas" wrote:

> Did you have any errors when you first installed the server? If not, did
> you try to swap the memory modules just in case they are defective?
>
> --
> Costas
>
>
> "pmela" <pmela@discussions.microsoft.com> wrote in message
> news:5F958858-A75A-4C03-976A-9EE0C3A3A405@microsoft.com...
> > Hi Costas,
> > Thanks for the tip but sadly it did not make any difference. I've set the
> > permissions as recomended in the link you sent me but with no effect. The
> > Application Pools still crash as soon as I try to access any of the web
> > site
> > mentioned.
> >
> > We're having a lot of problems with this server currently. For one thing,
> > it
> > does not restart properly. It simply hangs on the shut down message and
> > has
> > to be swithed off manually.
> >
> > Any tips would be appreciated, I really do not want to reinstall this
> > Server
> > as it was a pain in the ... to move all clients to the new domain. I don't
> > want to do it all over again.
> >
> > "Costas" wrote:
> >
> >> Take a look at the following article and see if it can be of help
> >> http://support.microsoft.com/kb/842493
> >>
> >>
> >> --
> >> Costas
> >>
> >>
> >> "pmela" <pmela@discussions.microsoft.com> wrote in message
> >> news:4D16159C-1E57-41D4-B20E-B0C42922DFE1@microsoft.com...
> >> >I have a brand new (1 week old) installation of SBS 2003 but for some
> >> >reason
> >> > I can not use the SharePoint web sites.
> >> >
> >> > The web sites are installed and running ok in IIS but when I check the
> >> > Application Pools, DefaultAppPool, StsAdminAppPool and WsusPool are
> >> > Stopped
> >> > due to an unspecified error. I can start them but as soon as I access
> >> > the
> >> > companyweb website the DefaultAppPool and WsusPools crashes. The same
> >> > thing
> >> > happens to the StsAdminAppPool when trying to access the SharePoint
> >> > Cetral
> >> > Admin website.
> >> >
> >> > the W3SVC service report loads of errors in the system event log but
> >> > microsoft has no information on the error codes;
> >> >
> >> > This is what it looks like in the event log for the StsAdminAppPool:
> >> >
> >> > A process serving application pool 'StsAdminAppPool' terminated
> >> > unexpectedly. The process id was '4168'. The process exit code was
> >> > '0xffffffff'.
> >> >
> >> > A process serving application pool 'StsAdminAppPool' terminated
> >> > unexpectedly. The process id was '860'. The process exit code was
> >> > '0xffffffff'.
> >> >
> >> > A process serving application pool 'StsAdminAppPool' terminated
> >> > unexpectedly. The process id was '2052'. The process exit code was
> >> > '0xffffffff'.
> >> >
> >> > A process serving application pool 'StsAdminAppPool' terminated
> >> > unexpectedly. The process id was '5028'. The process exit code was
> >> > '0xffffffff'.
> >> >
> >> > A process serving application pool 'StsAdminAppPool' terminated
> >> > unexpectedly. The process id was '5220'. The process exit code was
> >> > '0xffffffff'.
> >> >
> >> > Application pool 'StsAdminAppPool' is being automatically disabled due
> >> > to
> >> > a
> >> > series of failures in the process(es) serving that application pool.
> >> >
> >> >
> >> > Thanks for any help!
> >>
>

There are way too many errors to try to pinpoint what causes them. If it
was a SharePoint error, the problem area would have been the stsadminpool
only. But you say that you can't start any of the other pools, which brings
it to the IIS having a problem.

There have been discussions here about IIS and trying to reinstall it, and
it isn't something that you want to do. I have to say it but you have one
of two options. Calling Microsoft PSS or reinstalling the server. You
might want to wait for a day or two just in case someone has another
solution and then decide what you want to do

--
Costas


"pmela" <pmela@discussions.microsoft.com> wrote in message
news:1AA4C196-B2AE-4724-9870-F25697397AB0@microsoft.com...
> Im not sure if these errors occured initially as I did not try to use
> SharePoint. Retarting the computer, however, was working fine until a
> couple
> of days ago.
>
> Maybe i should mention there is an Microsoft SQL Server 2005 installed on
> this machine as well. Thinking it might be this one that somehow
> interferes
> with SP I tried to uninstall it but when I did "remove" from the
> "add/remove
> programs" menu, the SQL Server entry just vanished. Nothing happened and
> the
> server is still installed. I looked up instructions on how to remove the
> SQL
> server manually, but when I try that I get an error message saying
> something
> like:
>
> "SQL Server setup can't inspect software installed due to the WMI
> configuration on this Machine"
>
> I searched MSDN for this error and found a batch fix posted by someone
> that
> obviously had worked for several people. I ran it on the server and it
> registered a lot of DLL libraries and did other stuff, Im not sure exactly
> what, but It did not solve my problem. I still can't uninstall SQL Server
> manually OR run the SQL Server installation from CD due to the WMI
> configuration.
>
> "Costas" wrote:
>
>> Did you have any errors when you first installed the server? If not, did
>> you try to swap the memory modules just in case they are defective?
>>
>> --
>> Costas
>>
>>
>> "pmela" <pmela@discussions.microsoft.com> wrote in message
>> news:5F958858-A75A-4C03-976A-9EE0C3A3A405@microsoft.com...
>> > Hi Costas,
>> > Thanks for the tip but sadly it did not make any difference. I've set
>> > the
>> > permissions as recomended in the link you sent me but with no effect.
>> > The
>> > Application Pools still crash as soon as I try to access any of the web
>> > site
>> > mentioned.
>> >
>> > We're having a lot of problems with this server currently. For one
>> > thing,
>> > it
>> > does not restart properly. It simply hangs on the shut down message and
>> > has
>> > to be swithed off manually.
>> >
>> > Any tips would be appreciated, I really do not want to reinstall this
>> > Server
>> > as it was a pain in the ... to move all clients to the new domain. I
>> > don't
>> > want to do it all over again.
>> >
>> > "Costas" wrote:
>> >
>> >> Take a look at the following article and see if it can be of help
>> >> http://support.microsoft.com/kb/842493
>> >>
>> >>
>> >> --
>> >> Costas
>> >>
>> >>
>> >> "pmela" <pmela@discussions.microsoft.com> wrote in message
>> >> news:4D16159C-1E57-41D4-B20E-B0C42922DFE1@microsoft.com...
>> >> >I have a brand new (1 week old) installation of SBS 2003 but for some
>> >> >reason
>> >> > I can not use the SharePoint web sites.
>> >> >
>> >> > The web sites are installed and running ok in IIS but when I check
>> >> > the
>> >> > Application Pools, DefaultAppPool, StsAdminAppPool and WsusPool are
>> >> > Stopped
>> >> > due to an unspecified error. I can start them but as soon as I
>> >> > access
>> >> > the
>> >> > companyweb website the DefaultAppPool and WsusPools crashes. The
>> >> > same
>> >> > thing
>> >> > happens to the StsAdminAppPool when trying to access the SharePoint
>> >> > Cetral
>> >> > Admin website.
>> >> >
>> >> > the W3SVC service report loads of errors in the system event log but
>> >> > microsoft has no information on the error codes;
>> >> >
>> >> > This is what it looks like in the event log for the StsAdminAppPool:
>> >> >
>> >> > A process serving application pool 'StsAdminAppPool' terminated
>> >> > unexpectedly. The process id was '4168'. The process exit code was
>> >> > '0xffffffff'.
>> >> >
>> >> > A process serving application pool 'StsAdminAppPool' terminated
>> >> > unexpectedly. The process id was '860'. The process exit code was
>> >> > '0xffffffff'.
>> >> >
>> >> > A process serving application pool 'StsAdminAppPool' terminated
>> >> > unexpectedly. The process id was '2052'. The process exit code was
>> >> > '0xffffffff'.
>> >> >
>> >> > A process serving application pool 'StsAdminAppPool' terminated
>> >> > unexpectedly. The process id was '5028'. The process exit code was
>> >> > '0xffffffff'.
>> >> >
>> >> > A process serving application pool 'StsAdminAppPool' terminated
>> >> > unexpectedly. The process id was '5220'. The process exit code was
>> >> > '0xffffffff'.
>> >> >
>> >> > Application pool 'StsAdminAppPool' is being automatically disabled
>> >> > due
>> >> > to
>> >> > a
>> >> > series of failures in the process(es) serving that application pool.
>> >> >
>> >> >
>> >> > Thanks for any help!
>> >>
>>

[Adecus]

I found a solution to this problem here:
http://www.adamwalsh.net/2009/04/18/...rating-system/

Dear: Adecus

When you reply to a post in http://forums.techarena.in
it shows up as a broken thread on a Microsoft Public newsgroup

Specifically
NewsServer: msnews.microsoft.com
newsgroup: microsoft.public.windows.server.sbs

This site.
http://forums.techarena.in/members/webwired.htm
Copies Posts from Microsoft Break/Fix SBS newsgroup.

So Any responding or posting means that 99% of the world will not know what
you are responding to.
(Since it will be a broken thread on the original source.)

In your current post we have no reference to what you are talking about.

If you avoid Techarena.in and post directly to the Microsoft
newsgroup you will benefit from threads not getting broken.
And a lot of misunderstanding.

You can either use a NNTP News Reader (Example Outlook Express)
And set it up with:
NewsServer: msnews.microsoft.com
newsgroup: microsoft.public.windows.server.sbs
or By Clicking Below
news://msnews.microsoft.com/microsof...ows.server.sbs


If you wish a "WEB" Based interface with NO Ad's you can go directly to this
forum with.
http://www.microsoft.com/communities...&lang=en&cr=US
It has the feature to notify you on a reply also.

To Search for issues in the past the best way is to Google them.
http://groups.google.com/group/micro...UTF-8&oe=UTF-8
This has way more information than that website will ever have and help you
to stay connected.

Thanks
I hope you find this information helpful.

Russ


--
Russell Grover - SBITS.Biz
Microsoft Gold Certified Partner
Microsoft Certified Small Business Specialist
World Wide 24hr SBS Remote Support - http://www.SBITS.Biz


"Adecus" <Adecus.3qubfc@DoNotSpam.com> wrote in message
news:Adecus.3qubfc@DoNotSpam.com...
>
> I found a solution to this problem here:
> http://www.adamwalsh.net/2009/04/18/...rating-system/
>
>
> --
> Adecus
> ------------------------------------------------------------------------
> Adecus's Profile: http://forums.techarena.in/members/91249.htm
> View this thread:
> SharePoint Service Unavailable (Application Pool crashes)
>
> http://forums.techarena.in
>

Russ - www.SBITS.Biz wrote:
> Dear: Adecus
>
> When you reply to a post in http://forums.techarena.in
> it shows up as a broken thread on a Microsoft Public newsgroup
>
> Specifically
> NewsServer: msnews.microsoft.com
> newsgroup: microsoft.public.windows.server.sbs
>
> This site.
> http://forums.techarena.in/members/webwired.htm
> Copies Posts from Microsoft Break/Fix SBS newsgroup.
>
> So Any responding or posting means that 99% of the world will not know what
> you are responding to.
> (Since it will be a broken thread on the original source.)
>
> In your current post we have no reference to what you are talking about.
>
> If you avoid Techarena.in and post directly to the Microsoft
> newsgroup you will benefit from threads not getting broken.
> And a lot of misunderstanding.
>
> You can either use a NNTP News Reader (Example Outlook Express)
> And set it up with:
> NewsServer: msnews.microsoft.com
> newsgroup: microsoft.public.windows.server.sbs
> or By Clicking Below
> news://msnews.microsoft.com/microsof...ows.server.sbs
>
>
> If you wish a "WEB" Based interface with NO Ad's you can go directly to this
> forum with.
> http://www.microsoft.com/communities...&lang=en&cr=US
> It has the feature to notify you on a reply also.
>
> To Search for issues in the past the best way is to Google them.
> http://groups.google.com/group/micro...UTF-8&oe=UTF-8
> This has way more information than that website will ever have and help you
> to stay connected.
>
> Thanks
> I hope you find this information helpful.
>
> Russ
>
>
SharePoint Service Unavailable (Application Pool crashes)
Furthermore that fix is for a 64bit system of which SBS 2003 is not.