asked on

DotNetNuke error

I have a web server and a database sersver, both running in VM's, using Win2K12R2. One of our websites failes every morning at the exact same time, with the following error. If anyone has any idea what is causing it, that would be great.
What's strange is, after about 5 -9 minutes, it comes back up by itself.

Message:
DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to FeaturedVideoPane ---> DotNetNuke.Services.Exceptions.PageLoadException: Error: Featured Video is currently unavailable. ---> DotNetNuke.Services.Exceptions.ModuleLoadException: Error: Featured Video is currently unavailable. ---> System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

R. Toby Richards

Two things:

1. Check your DotNetNuke setup and your Windows Scheduled Tasks to see if there is a recurring task that runs at that time. It looks like DotNetNuke is trying to install or update a module every day.

2. MaxPoolSize errors are often the result of a poorly maintained database. Make sure that you have an SQL maintenance task that rebuilds your indexes and updates statistics weekly.

Dan

ASKER

Task scheduler is clear, no jobs running from 2 am to 3 am except defrag and time synchronization, which both run at 2:05 am and both were successful.

I'll check into the other items you mentioned.

How can I tell if DotNetNuke is trying to install or update a module? Is there a DotNetNuke log or something?

R. Toby Richards

I know very little about DotNetNuke. I personally prefer PHP solutions. I do know that there MAY be an auto-update feature somewhere in the settings.

Dan

ASKER

my web developer just said that with DotNetNuke, it can't autoupdate, it has to be manually done.

ASKER CERTIFIED SOLUTION

R. Toby Richards

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Dan

ASKER

Thanks, you pointed me in the right direction, the problem was with my SQL backup job. I was using the option to index files and for some strange reason, with that option turned on, it would crash dotnetnuke. I disabled that feature and my issue went away.