"Timed out waiting for a program to execute". Very HUGE problem!

[Hans Baumann]

Hello everyone,

I've started to see this exception in my ASP.net app, first time was when in
one of my customers reinstalled one of the servers (actually there was only
shared folders on that server that my web application reads).

I don't know exactly if it could be the reason, but, everything was working
Ok, it just happens on that specific client. They were using my web app for
over a year, so I don't know if it because of some windows upgrade, I don't
know.

I have searching over the web and the only solution they give is to restart
IIS, it works, but I can't rely on that kind of solution because of many
reasons. First of all it is a intranet, and the scope of the application
involves the file system, so stopping the app could cause over a 50 people
to stop all their work!...

Is microsoft looking for a solution? or has it a KB with a walkthrough to
avoid this problem in the future?

Thanks!

Hans Baumann

 

[Hans Baumann]

Not here as you can see, navigating I founded that the problem is a bug in
asp.net, but nobody has a good response about it, I started thinking that
there won't be support for the .net framework under the 2.0 version.

I believe that asp.net cannot manage very well the "warm-updates", I'm sure
that if something changes in the asp.net enviroment, if you copy a new dll
in the bin folder of some web app, it tryes to recompile all the dll's
without success (that could explain why the page that generates that
exception is random) , and it need to restart in order to recompile
succesfully all the webforms, usercontrols, etc... so beware of any web app
updates or changes in the enviroment...