By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,035 Members | 1,543 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,035 IT Pros & Developers. It's quick & easy.

.NET Remoting under IIS getting shut down

P: n/a
We're using .NET remoting hosted under IIS but we're running into problems
with the server shutting down the ASP.NET worker process unexpectedly. Since
I know this can occur because of the settings in the <processModel> area of
the machine.config, we've tried a couple of things to resolve this:

1) We ensured all the timeout/request limit settings were set to "Infinite"
and the memory limit set to 100%.
2) We tried setting the "logLevel" attribute to "All" so we'd get logs of
when ASP.NET was shutting down the worker process.
3) We tried disabling the processModel settings altogether by setting
enabled="false".

None of these techniques had any effect and the setting the logging to "All"
produced no entries in the Event Log. What's strange is that, when this
occurs, the server shuts down gracefully -- that is, the Application_End
event gets fired in the global.asax. So, it's not just that the server
crashes -- something's shutting it down.

Any ideas or suggestions of what to check next would be greatly appreciated.

Regards -
Ken
Nov 18 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi Ken,
I have found this link, see if it helps:

http://www.asp.net/Forums/ShowPost.a...&PostID=232621

Sunny

In article <ua**************@TK2MSFTNGP10.phx.gbl>, ken.kolda@elliemae-
nospamplease.com says...
We're using .NET remoting hosted under IIS but we're running into problems
with the server shutting down the ASP.NET worker process unexpectedly. Since
I know this can occur because of the settings in the <processModel> area of
the machine.config, we've tried a couple of things to resolve this:

1) We ensured all the timeout/request limit settings were set to "Infinite"
and the memory limit set to 100%.
2) We tried setting the "logLevel" attribute to "All" so we'd get logs of
when ASP.NET was shutting down the worker process.
3) We tried disabling the processModel settings altogether by setting
enabled="false".

None of these techniques had any effect and the setting the logging to "All"
produced no entries in the Event Log. What's strange is that, when this
occurs, the server shuts down gracefully -- that is, the Application_End
event gets fired in the global.asax. So, it's not just that the server
crashes -- something's shutting it down.

Any ideas or suggestions of what to check next would be greatly appreciated.

Regards -
Ken

Nov 18 '05 #2

P: n/a
Thanks, Sunny. I'll try the performance monitoring options to see if that
sheds any light on what's happening.

Ken
"Sunny" <su******@icebergwireless.com> wrote in message
news:eE**************@tk2msftngp13.phx.gbl...
Hi Ken,
I have found this link, see if it helps:

http://www.asp.net/Forums/ShowPost.a...&PostID=232621

Sunny

In article <ua**************@TK2MSFTNGP10.phx.gbl>, ken.kolda@elliemae-
nospamplease.com says...
We're using .NET remoting hosted under IIS but we're running into problems with the server shutting down the ASP.NET worker process unexpectedly. Since I know this can occur because of the settings in the <processModel> area of the machine.config, we've tried a couple of things to resolve this:

1) We ensured all the timeout/request limit settings were set to "Infinite" and the memory limit set to 100%.
2) We tried setting the "logLevel" attribute to "All" so we'd get logs of when ASP.NET was shutting down the worker process.
3) We tried disabling the processModel settings altogether by setting
enabled="false".

None of these techniques had any effect and the setting the logging to "All" produced no entries in the Event Log. What's strange is that, when this
occurs, the server shuts down gracefully -- that is, the Application_End
event gets fired in the global.asax. So, it's not just that the server
crashes -- something's shutting it down.

Any ideas or suggestions of what to check next would be greatly appreciated.
Regards -
Ken

Nov 18 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.