One of our customers is having this error appear periodically on his client browsers (chrome, firefox and ie) but can clear it by a simple page refresh (undesirable workaround)
This may be a simple bottleneck of system resources starting with RAM but before I go down that road, I want to see if anyone has any better ideas as to a) what is the real problem and b) can it be managed within the current resource constraints?
The server is a 64 bit Windows Server 2008 R2 running in a HyperV env with 32G RAM allocated. The main application is SQL Server 2008 R2 which is taking 90+% RAM.
We have VB ASP code interfacing between IIS and the SQL server that calling into a DLL to build a graphic chart for display. The server log error thrown looks like it is coming from our ASP2DLL code which may be from having to cache in that code periodically, given the SQL Server is hogging the memory. We are experimenting with limiting the RAM that SQL Server will consume which *should* leave more RAM for other system applications to not need to be cached.
We have not been able to reproduce this problem but our customer is seeing in periodically on several clients. This is a server error, not a client one.
I am attaching a file with datapoints from the server to help with understanding the env and error messages.