w3wp.exe Crash InitializeCulture Event Log

We have an application (A) that is causing a crash in w3wp.exe.

When this crashes, we are getting an error in another site (B) of
"InitializeCulture" is not a member of...

The crash is a result of a COM object in A. Site B inherits its pages
from the MSDN.SessionPage and reports this error whenever it is
running framework 2.0.

I have been resetting B's Application Pool in order to fix this. The
site is running framework 1.1 but after the w3wp crash, it thinks it
is running 2.0 which causes the InitializeCulture error.

This all started happening last week after the latest Microsoft
Updates were applied to the server.

Does anyone have an idea on why the site would think its running 2.0
when it is not? Is there a fix?

Thanks

Tim

Re: w3wp.exe Crash InitializeCulture Event Log

Tim,

Recheck if you're really running ASP.NET 2.0. Type:
> cd c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
> aspnet_regiis -lv

Check if only 1.1 appears. If not then uninstall v2, then re-install v1.1.

> v2.0.50727\aspnet_regiis -u
> v1.1.4322\aspnet_regiis -i

I think its the best way to make sure, really.

Tiago Halm

Re: w3wp.exe Crash InitializeCulture Event Log

On Sep 17, 10:14 am, tim.cav...@gmail.com wrote:
> We have an application (A) that is causing a crash in w3wp.exe.
>
> When this crashes, we are getting an error in another site (B) of
> "InitializeCulture" is not a member of...
>
> The crash is a result of a COM object in A. Site B inherits its pages
> from the MSDN.SessionPage and reports this error whenever it is
> running framework 2.0.
>
> I have been resetting B's Application Pool in order to fix this. The
> site is running framework 1.1 but after the w3wp crash, it thinks it
> is running 2.0 which causes the InitializeCulture error.
>
> This all started happening last week after the latest Microsoft
> Updates were applied to the server.
>
> Does anyone have an idea on why the site would think its running 2.0
> when it is not? Is there a fix?
>
> Thanks
>
> Tim



The fix is for you to fix your crashing application.

You observation of the behavior change after Microsoft updates is
really irrelevant because by definition, crashes result in arbitrary
behavior. You may have liked the prior arbitrary behavior, but it is
hardly intended, so you certainly can't ask for "fix".

The only way for you to get intended behavior is to get rid of the
random behavior -- and that means to get rid of the crash.

FYI: I don't really believe that a 1.1 application would think it is
2.0 after a crash. I suspect that you have versioning conflicts going
on which are affected by URL execution order, which a crash can
affect. Once again, the sure way to get consistent behavior is to get
rid of the random crashes.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//