• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 884
  • Last Modified:

DotNetNuke site works for superuser in edit mode, but not in view mode

...not in "view" mode.  Nor does several of my

modules when I am logged in as a "Registered User."

Specifically, my Simple Gallery module and my Active Forums module

(both heavy SQL) time out if I try to visit their pages when I am logged

in as the superuser but in "view" mode, or if I log in as a regular user.

On the other hand, if I log in as the superuser and am in EDIT mode,

they work just fine.

All was working well until a few days ago when I added a handful of new

registered members.   The application appears to shut down because of

the hosting environment (IIS 7 (whatever comes standard with Windows

2008 server)

Environment:  DNN, and all modules are up-to-date except the

Active Forums module.  I host the site on Windows Server 2008 Standard

on a Dell PE2900 w/4 gig of ram.

SQL Server 2008 Express Edition

I do get one error in my event log -

Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919413, faulting module kernel32.dll, version 6.0.6001.18215, time stamp 0x49953395, exception code 0xe053534f, fault offset 0x000442eb, process id 0x%9, application start time 0x%10.

I can provide other details if there is something I left out of the above.

Any help or leads would be appreciated!

  • 5
  • 3
2 Solutions
As the event log shows, the ASP.NET worker thread produces an error and quits for some reason. You could probably use the SQL Server profiler to see what's going on there as you said you get timeouts.
pootwaddleAuthor Commented:
thank you -- I think maybe I have hit the size limitation of my SQL Server Express database.
Time to upgrade.
What is the size of the database? It could be that the TransactionLog has grown to huge size and its time to truncate it!
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

pootwaddleAuthor Commented:
Well, it says 300.38 mb.  That doesn't seem that big to me.  The recovery model is set to "simple"
Is that the size of ldf file or the mdf? Try truncating the log by backing it up.
pootwaddleAuthor Commented:

I'll give that a try, thanks!
Do you get this pronblem only for the page with that module or also in other pages ?
in edit mode the data on this module are displayed correctly ?

pootwaddleAuthor Commented:
Hi, Paolo -
I only get the problem in the pages with those modules (there are 2 giving me fits).

I did back up the database, and there are no changes.

It looks as if my database is corrupted because I deleted the modules giving me
trouble and then added them back in and they are like brand-new installs of
those modules with none of my old data in them.  Of course, that could be
normal behavior but I don't know that for sure.

I can only work on this on the weekends, so please be patient with my changes
and replies back here.

pootwaddleAuthor Commented:
I ended up upgrading my version of SQL server, deleting the troubling modules and pages, recreating those pages then restoring the
modules back onto the new pages from the recycle bin
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now