RE: ASP.Net Worker Process Drops Out Yet Again!

From: Patrick.O.Ige (PatrickOIge_at_discussions.microsoft.com)
Date: 12/02/04 

Date: Wed, 1 Dec 2004 17:12:19 -0800

Richard,
    I know it can turn soemone MAD..Take it easy..
What i can advice you is to DOCUMENT what you have done it makes it easy to
solve such a problem.Lets start from here...What were you trying to do when
you got the ERROR?
Patrick

"Richard Myers" wrote:

> Hello
>
> Im sure many of you have seen this error message before:
>
> [aspnet_wp.exe could not be started. The error code for the failure is
> 80004005. This error can be caused when the worker
> process account has insufficient rights to read the .NET Framework files.
> Please ensure that the .NET Framework is correctly
> installed and that the ACLs on the installation directory allow access to
> the configured account. ]
>
> For us its the third time this year. This error occurs seemingly at random.
> I have no idea what causes it too happen. None.
> Question 1: Do you?
>
> Secondly what is the procedure to resolve this? I have seen many threads on
> the net about this but all responses seem
> "pot luck" or "best guess". I have yet to see anyone from Microsoft respond
> to any of these threads?
>
> I have uninstalled ASP.Net using regiis;deleted ASP.NET user
> account;reinstalled ASP.NET using regiss and the result is zip.
> Same problem. I have even gone into the machine.config and given the
> processModel user and password "full priviledges",
> yes that right Admin rights... and still no resolve.
>
> Question 2: Does anyone have a dead set procedure for resolving this issue?
>
> Surely if i uninstall ASP.Net first of all then it shouldn;t matter what
> the error was to begin with? If i can reinstall successfully
> then the error should be "fixed"? I realise this is very plain logic but
> all the documentation makes this out to be a very simple
> fix.... but it never is. It becomes a cost benefit exercise...re-ghost or
> *** around for hours trying to resolve it.
>
> Microsoft talk alot about the TOC benefits with respect to their platform,
> sometimes i wonder if the TOD is really worth it.
> Exceptions like this make the platform seem really brittle. There is a
> reason for everything in software. Things just shouldn;t
> "drop out" for no particular reason.
>
> There is no problem with plain old vanilla web pages. So Im assuming no
> problem with IIS.
> Reinstalling ASP.net + user accounts; that should take care of any bung
> worker processes etc.
> If i give full admin priviledges to ASP.net then there couldn;t be a
> priviledges problem?
>
> So what other pieces of the puzzle does that leave?
> And why given full priviledges does that damn error message not change?
> This is the part that really
> annoys me the most. I feel like the error message is leading me on a wild
> goose chase. It simply doesn;t
> seem relevant.
>
> Thankfully i now have the time to resolve this. As much as i want a fix, i
> want the understanding as well.
> I want to become an expert in resolving this problem. I want to understand
> the causes and effects on every conceivable level.
> Thats how much its &%$%* me off.
>
> Where is the info for me too do this..beyond what i already know...How do i
> debug this issue?
> Any help much appreciated.
>
> Thanks
> Richard
>
>
>

Loading