Dave - welcome to the world of DNN!! I have this problem and it's been driving me mad..

I actually wrote a bit on my blogs about it - http://www.xd.com.au/blogs.xd?EntryID=312

But the first thing we've done that's helped is change the caching memory to disk. You may need to modify your pagesys file to maximum and while the response is milliseconds slower, it does help alleviate some of the problems.

You might also check your error logs and see if there is something showing there.. I bet you've got some rogue module creating memory leaks.

This blog mght give you some insight but honestly - it's been very difficult for me to manage my servers, but I'm on Win2k so the behaviour is even worse.

I also read in the Core forums some problems with the NRL site - it's giving them hell when it spikes.. There was discussion of how some of the code was working and what core solutions there could be to rectify this, but not being a coder, I'm not able to exactly cover this in much detail.

Administration of a DNN site uses alot of memory, can you not use application pooling on your server to manage this behaviour and stop it from affecting other sites? Or is this a dedicated box  ( I think it would be based on they type of site you are describing)

3.1.1 is a stable build - so there might be some further optimisation you can do, but I would be checking your modules, particularly if you have anything that is XML based, it will eat into your memory like you can't believe.

Anyway my blog might give you some further snippets on this extremely frustrating issue that I have had to battle with over the last 2 months.  However, I did have a site on there which when I asked the developer to move, it did help somewhat.. so a bad module will surely spike your aspnet exe like you've never seen before.

Check also your sql logs - on the other box - that too can cause problems and lock the server.

Nina Meiers

Can you look at your event logs - they will tell you a few things and post what they say here - i know there is something that refers to bitchunk and not enough space, which I originally thought was a disk space issue but upon searching, I found it was in fact something to do with sql and the field parameters being too short but I've never been able to track it down.

You could also google the event Id's that are created when you have these problems *sigh*.. many a saturday night and sunday have been spent reading through them and since I'm not a qualified administrator, and only learnt through having to sort out my own problems, I can't quickly identify them.

I do know that there are also sql administrators and IIS admnistrators who can assist in tweaking the default settings that you need to do when you reach a certain size of traffic because the standard settings simply don't apply.

However, having said that I'm not qualified, it doesn't mean that I don't know how to manage my servers, it's just something that I find alot of people don't have answers for and we're simply working on the the knowledgeabase at the moment.

So check out the eventID and see if that doesn't give you some more information too - i thik there is a site called eventID.net- it's bookmarked ony server so I'm just guessing now - but that's also a good start to look.

And please if you find something enlightening here, share it - so I can also nut out this annoying problem.  And also, I don't get EventId entries, or log files either so if you don't get them either - doesn't mean the the problem doesn't exist.

Nina Meiers