Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN 4.02 problemDNN 4.02 problem
Previous
 
Next
New Post
1/22/2006 3:31 PM
 

I install DNN 4.02 on my development PC to work out the details and it works great. Now I moved it to my provider and it works sort of.

It takes foreaver to get a page for the first time and somethimes it returns a Request Timed Out error. It also sometimes gives me a Object Reference not set to instance of an object.

Once I do get it running if I remain on the site and keep changing from page to page it works fine and responds well. But if I allow it to sit a few minutes before click on new pages, it will once again start the whole process again.

I have seen references to the problems associated with the Object Reference problem but it seems if I had it working one place it would work in another location or not at all.

Any help would be appreciated

 
New Post
1/22/2006 4:02 PM
 

The issues associated with load time are usually a function of the application not being loaded ( in the .Net sense ).  So, for example, a busy site will perform very well.  But one that is only hit once in a while will experience a delay while .Net starts up a worker process and loads the application.  Since these are IIS settings, the host has some influence about how often this occurs, such as determining how long it takes for the application to give up its worker process and go to sleep ( typically 20 minutes ).  Generally, these kinds of policies are one of the differentiating factors between hosts since they have to balance how much resources each client is consuming.

There are things you can do to "keep your site alive" if it is one that is not trafficed much.  There is a file in your web root called keepalive.aspx which does nothing but render the time and refresh itself periodically.  This should keep the worker process loaded since your application ( the site in the dnn root ) appears to be active to .Net.  Likewise there are any number of services which will do site pings for you as well.

Cheers


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
New Post
1/23/2006 8:46 AM
 

I don't think it's only a matter of keeping it alive. It seems to be something else. It errors alot with time outs and the Object Reference not set to instance of object. I don't think I'm the only one out here that has this problem since there seems to be others that have written something similar.

There has got to be an answer to this other than me rewriting some of the code to address caching objects. Is it possible that it's as simple as a database settings. One thing I did do is move my site and it's possible that there are some entries in the databse tables that do not correspond to it's current location but I have not been able to find them.

Does anyone else have the same issues?

 
New Post
1/30/2006 9:42 AM
 

I have been working with this problem and here is what I have found (no solution yet).

  • The Application randomly suts down for no apparent reason. We have moved it to different AppPools and have verfied that no other app is causing the shut down. It will happen many times within an hour even though KeepAlive.aspx is refreshing every 5 minutes
  • It does not seem to happen on the XP version of IIS. Only seems to happen in IIS6
  • Nothing but Application is shutting down and Application started shows up in the log.
  • I'm not the only person to have this issue http://forums.asp.net/1174451/ShowPost.aspx

Anyone else having this problem or is DNN 4 just not being used much at all?

 
New Post
1/31/2006 6:45 AM
 
One more bit of information to help those that may have the same issue, It is definately DNN that is causing the problem. It is in it's own Application Pool and it is causing the crash although we have not been able to determine why.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN 4.02 problemDNN 4.02 problem


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out