Hi there,

We are developing a huge portal with about 50-100 custom made modules and a fully custom build back-end for all these modules' data retrieval and validation . The portal is based on DotNetNuke 3.2.0 for now and in the near future 4.4.*

The problem described in this thread "Randomly Logging Out During Edit" is partially our problem too. But with the small difference we got it also while not editing content ! It does not happen in a pattern (like every five minutes for example) like some users say on these forums. We got these "logout & reloggin" issues randomly.

We are using Windows Authentication for portal users and forms login for admin and host (no login/logout button available in the skin but accessed through ctl=login querystring parameter). We have only one portal and no child portals at all.  The problem sound like the one Steve has too. "it appears to be a app time-out(/process recycle)".

I've read multiple threads about this problem on these Dnn forums but all are started by a person who is telling about the problem, others who are reacting on that post and communicate that they have a similar problem, in most threads a core member steps in but in the end all of these threads have an open ending with no result and bleed to death.

I've noticed the last post was from Locopon on 11/20/2006 2:20:49 PM already a while ago, I'am wondering if people like Steve have solved the problem yet. If they do, can they please leave a message on these forums with the/a solution ?

I hope to here from people with the same problem who can help me with this, because it's really getting a big problem.

Can also a core member give a reaction on this problem because with this problem alone real big commercial sites can't be build with DotNetNuke... And that would be sad  

Thanks for reading

P.H. Leenaers

It's been a while .....

But my problem with randomly still exists :-(

its is very hard (like impossible.. ) to reproduce, but we've got the randomly logging out problem on all platforms (test, acceptation and production) all these platforms are using windows authentication. Only one portal exists, no childs are used. The only thing I can add to my previous post is that it maybe is not as random as I thought.

After having an application in the production environment (a wizard like module which is based on the portal wizard solution of dnn core btw), with a user constantly using the application we saw that while working with the app the user sometimes was thrown back to the first page of the wizard and lost all the data on the wizard pages she filled in before. After checking the logviever information we saw a pattern of login succes message of this user every 60 till 70 minutes. We can confirm she did not have a session time out, she worked for hours without stop using the wizard (she can work through a wizard process in like 7 or 8 minutes, something like adding objects to a database). But while working in such work (wizard)process, in 60 (till 70) minutes after the previous (logviewer) message of login succes the problem occured again. After having this problem registered by multiple users we 've monitored the logviewer closer and notice that quite often this pattern occures for multiple users.

We also got "normal" modules (though custom made but with just a form and buttons no pages loaded in wizardpagecollection or something like that). I think (but ar not sure yet) that we got the same windows re-login there too but users don't notice it there because the user is re-logged in again right away and the page keeps looking the same because of the viewstate (all usercontrols have a controller class which autobind controls on the ascx through viewstate).

we've allready checked the server IIS configuration etc. but nothing there. No specific hard-configured recycle in machine.config or web.config.

My biggest concern is the time frame of 60 -70 minutes between two login succes messages in the logviewer.

can anyone help me with suggestions ?

Pepijn