Last post Jan 24, 2006 11:01 AM by wylie
Nov 14, 2005 03:35 AM|Lubet|LINK
Hello, I have a site (just name it
http://mysite.mysubdomain.mydomain.com) running DotNetNuke 3.0.13. Often when I’m modifying
my pages I get this error:
An error has occurred.
DotNetNuke.Services.Exceptions.PageLoadException: Exception of type System.OutOfMemoryException was thrown. ---> System.OutOfMemoryException: Exception of type System.OutOfMemoryException was thrown. --- End of inner exception
stack trace ---
So when I’m logged as host, I get the same error and can’t access to the administration pages. After 20-30 minutes the error disappears and I can work again as usual.
If I’m surfing it’s no problem but if I edit the pages the error is coming again.
The weird thing is that when this error is coming affects all my sites under “mysubdomain.mydomain.com”, so I get the same error in
http://mysite2.mysubdomain.mydomain.com, and so on… all the sites are running version 3.0.13 too…
It’s no memory problem on the server, that’s for sure. After I read in the forum I changed also the way DotNetNuke is storing the Site Log from Database to File System
but it didn’t help.
Your help is really appreciated because I can’t find why it’s happening. Thanks in advance!
Jan 23, 2006 02:23 PM|wylie|LINK
Jan 23, 2006 11:02 PM|xfernal|LINK
Assuming your DNN database is on a local SQL Server and not remote, most likely it IS a memory problem on the server. We were experiencing the same error on a server with Dual 3 Ghz Xeons and 2 Gb of RAM and a local SQL Server during peak traffic times.
I started digging through MSDN and found the Server Memory Options (
"Use max server memory to prevent SQL Server from using more than the specified amount of memory, thus leaving remaining memory available to start other applications quickly. SQL Server does not immediately allocate the memory specified
in max server memory on startup. Memory usage is increased as needed by SQL Server until reaching the value specified in
max server memory. SQL Server cannot exceed this memory usage unless the value of
max server memory is raised." - MSDN
So, I decided to give it a try...This is what I did:
This seemed to have worked. MS SQL Server is such a pig. By putting it on a diet and setting max server memory, the error disappeared. I decided to do some testing and was beating up the server pretty bad with several crawlers/spiders I have built and was hitting
the sites hard. The only error experienced during testing was an occasional deadlock victim error, which is expected with the number of transactions taking place on this database. I will live with a temporary error over an IIS crash anyday.
Luckily, we were only temporarily using IIS and SQL Server on the same server, while decomissioning an old server, trying to make more room in our server rack for a couple of new servers. The best option is to get SQL Server on its own server, but for those
who don't have the resources, the above is your best bet along with creating separate application pools in IIS for each domain.
To create a pool designation in IIS 6.0
To assign a pool designation to an ASP.NET application in IIS 6.0
Configuring an ASP.NET Application for an ASP.NET Version -
Jan 24, 2006 11:01 AM|wylie|LINK