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 ...identity impersonation - event queue issue on some shared hosting identity impersonation - event queue issue on some shared hosting
Previous
 
Next
New Post
9/16/2006 11:48 AM
 

Points
This issue affects only some shared hosting environments and it seems, could be more fairly addresed to MS.
I understand that there are limits to how far DNN can go to be "niggle free" on all the shared hosting setups out there.

That said the identity impersonation/event queue issue remains for some shared hosting.
Post is here: http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/47749/scope/posts/Default.aspx

Outline
 "it seems the identity impersonation doesnt kick in until after the application has started and therefore any file writes attempted during the Application_Start event will fail as the worker process user doesnt have NTFS permissions on the domain webspace. Once the application has started, that event no longer is triggered and impersonation is enabled which is why it works on the refresh".
 
On DNN startup this results in a windows login requester which, when cleared, returns an error page. Click F5 and its all OK until DNN starts again.

I have gotten round this with help from my excellent ISP (redfoxhosting) by comenting out eventqueue code in Global.asax.vb
I have a few DNN 4.3x sites running with this modification with no impact (that I can detect).

Question1 - Does anyone know if this "solution" is viable in the longer term. I am simply not qualified to evalute this.

Question2 : If this set of problem events only happens at app start and, if I keep the worker process running by hitting KeepAlive.aspx every 15 minutes then the problems should be "sidestepped"?

My main concern is that commenting out the eventqueue comes back to bite me later.

Thanks
Ian


Mutate and Survive
 
New Post
9/16/2006 12:25 PM
 

Commenting it out will keep the Upgrade interface on any new modules that are installed from running.  This may not be a major concern because for some time the upgrade interface did not work anyway so there are not a lot of modules that even use it.  The only other place it disables is the updating of the SupportedFeatures flag of modules when you click update on the ModuleDefinitions page.  For most end users this is not a concern, this is usually only used by developers.

Leaving it in only causes the error during app restart when there are messages in the queue that need to be deleted.  When you get this error, the messages have already donr their job, so it is safe to delete the messages manually.  My advice would be to leave the code in, but delete the messages in the queue.  After that, the only time the problem will come back is when you install a new module, or when someone clicks update on the Module Definition screen.

In summary, the issue you are seeing is only because the messages can't be deleted, since they are already processed, you can delete them manually to get the issue to go away.


DotNetNuke Modules from Snapsis.com
 
New Post
9/17/2006 10:26 AM
 
Hi John
Many thanks for your informative answer on this issue. 

Also Thanks for PageBlaster - I have dnn sites that outperfom basic html pages now. 

Ian

Mutate and Survive
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...identity impersonation - event queue issue on some shared hosting identity impersonation - event queue issue on some shared hosting


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