.NET does not respond

[Jack]

Late yesterday our .NET applications stopped responding and they did not
generate any error messages.

About noon today they started responding again and our IT guys said that
they have not installed/modified anything that would affect this.

I'm curious if anyone else has run into this and if so were they able to
come up with a cause.

Thanks,
Jack

[Sean Hederman]

"Jack" <ab*@microsoft.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...

Late yesterday our .NET applications stopped responding and they did not
generate any error messages.

About noon today they started responding again and our IT guys said that
they have not installed/modified anything that would affect this.
I have a simple rule of thumb about this kind of thing. Think about what
could have changed. If no new code was released, chances are the
configuration changed. The IT guys can swear until they're blur in the face
that nothing changed, but patently something did. Now, it could have been
your code suddenly committing suicide, but generally that'd be one .NET
application, not all of them.

My money would be on investigating config changes...

Although I wouldn't bet the farm on it.

I doubt this helps ;D

I'm curious if anyone else has run into this and if so were they able to
come up with a cause.

Thanks,
Jack

[Jack]

My thoughts as well. It will probably remain a mystery.

"Sean Hederman" <us***@blogentry.com> wrote in message
news:cu**********@ctb-nnrp2.saix.net...

"Jack" <ab*@microsoft.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...

Late yesterday our .NET applications stopped responding and they did not
generate any error messages.

About noon today they started responding again and our IT guys said that
they have not installed/modified anything that would affect this.
I have a simple rule of thumb about this kind of thing. Think about what
could have changed. If no new code was released, chances are the
configuration changed. The IT guys can swear until they're blur in the

face that nothing changed, but patently something did. Now, it could have been
your code suddenly committing suicide, but generally that'd be one .NET
application, not all of them.

My money would be on investigating config changes...

Although I wouldn't bet the farm on it.

I doubt this helps ;D

I'm curious if anyone else has run into this and if so were they able to
come up with a cause.

Thanks,
Jack

[Randall]

I had the same problem on on the 11th. The splash screen on my app came up,
but the main screen would not become visible (No error messages). The app
stayed in memory though and used 100% CPU.

This app was rock solid and unchanged. The behavior was experience on
current and older versions, compiled and debug versions, and on different PCs.

We think it may have be somehow related to do with latest Windows Update.
"Jack" wrote:

Late yesterday our .NET applications stopped responding and they did not
generate any error messages.

About noon today they started responding again and our IT guys said that
they have not installed/modified anything that would affect this.

I'm curious if anyone else has run into this and if so were they able to
come up with a cause.

Thanks,
Jack