ASP.NET cache problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Earlier this week we set up a second application pool to be able to implement
trusted connections between ASP.NET apps and a SQL Server database on a
different server.

The trusted connection is working, but there seems to be a memory leak.
After paging through about 6 web pages that access the database, we're
getting the following application error (in Event Viewer):

Unable to get the private bytes memory limit for the W3WP process. The
ASP.NET cache will be unable to limit its memory use, which may lead to a
process restart. Error: 0x80070005

We've looked on Google at a number of postings about this error but they
don't seem to apply to our network setup situation. We can't find anything in
MSDN.

Help is appreciated. Let me know if you need more specific information.

Leslie
 
The trusted connection is working, but there seems to be a memory leak.
After paging through about 6 web pages that access the database, we're
getting the following application error (in Event Viewer):

Unable to get the private bytes memory limit for the W3WP process. The
ASP.NET cache will be unable to limit its memory use, which may lead to a
process restart. Error: 0x80070005
Click to expand...

This is not a memory leak, what it is saying is that it is unable to get the
memory limit (I'm going to take a guess and say that the new pools you setup
are running under a different user than before, and that this user does not
have permission to get this information)

Have you seen this
http://securinga.com/2004/07/unable-to-get-private-bytes-memory.html ?

Cheers,

Greg
 
Greg,

Thanks for the info. Yes, we saw references to this fix. As you will have
noted already, the downside is that the "fix" doesn't persist between server
restarts. I suppose we could write a script so that it is rexecuted every
time the server starts, but frankly, I had expected MS to give us a more
permanent solution !

Is this really the best solution available?

Leslie
 
Greg,

My network admin is saying that the fix you referenced applies to
"clusters"--which we don't do.

Is there further information or a fix for this problem?

Leslie
 
Greg,

We went ahead and applied the settings suggested in the article.

The problem has not cleared up.

I really wonder how it can be a permissions problem, since I can use the
trusted connection for 30-40 database accesses before we get the error
message. But, maybe there's something I don't understand here.

At any rate, we're still looking for a fix. Help is greatly appreciated.
Greg said:
This is not a memory leak, what it is saying is that it is unable to get the
memory limit (I'm going to take a guess and say that the new pools you setup
are running under a different user than before, and that this user does not
have permission to get this information)
Click to expand...

Leslie
 
The db connection has nothing to do with the issue

"Unable to get the private bytes memory limit for the W3WP process. The
ASP.NET cache will be unable to limit its memory use, which may lead to a
process restart. Error: 0x80070005"

It is trying to get the size of the process and failing .. I am suggesting
that it is failing on permissions to get the size. i.e. the use it is
running as does not have permissions to do it.

Cheers,

Greg Young
 
Back
Top