Hi Stan,
Thanks for posting in the community!
From your description, you encountered the "System.OutOfMemoryException"
and some other related exceptions occassionally on some certain ASP.NET web
pages in your web application. Also, these pages have called a certain
remote SErviceComponent, yes?
If there is anything I misunderstood, please feel free to let me know.
As for this problem, I agee with Alvin Bruney's suggestion that you have a
check or monitor on your ASP.NET worker process to see whether there is
anything abnormal on it, especially the memory. In addition to the Memory
Profiler Alvin Bruney has mentioned, here are some other approaches on
monitor ASP.NET process and performance:
#Watching Your Server Processes
http://msdn.microsoft.com/library/en...chserverproces
ses.asp?frame=true
#ASP.NET Performance Monitoring, and When to Alert Administrators
http://msdn.microsoft.com/library/en...rf.asp?frame=t
rue
#Production Debugging for .NET Framework Applications
http://msdn.microsoft.com/library/en...asp?frame=true
#Performance Counters for ASP.NET
http://msdn.microsoft.com/library/en...ormanceCounter
sForASPNET.asp?frame=true
In addtion, I still feel the remote SeriveComponent is a potential cause.
Would you please try temporarily remove the remote Component's calling from
those web pages to see whether the problem goes away? Or would you please
provide some further descriptions on a certain page which calls the remote
component or some infos on the remote SErviceComponent?
Please check out the above items. If you meet any further assitance, please
feel free to post here.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
-------------------------------------------------------------------------