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 ...SQL Timeout expired errors when installing modules. DNN 5.1.2SQL Timeout expired errors when installing modules. DNN 5.1.2
Previous
 
Next
New Post
10/7/2009 5:21 AM
 

rename module package inside /install/module to .zip and call /install/install.aspx?mode=installresources


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/7/2009 8:42 AM
 

Sebastian, consider my Thank You!  as a virtual hand shake.
This actually worked.  Although it did take a little over 2 minutes to install so I cannot consider this issue fixed.   Strange?
I will have to see what the SQL logs show.

I am adding this to my list of DNN helpful tips and tricks.

 
New Post
10/7/2009 9:48 AM
 

it sounds to me there are performance issues with you sql server or database. check size of the transaction log and main tables as well as rebuild indexes.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/8/2009 5:51 AM
 

seeing the same thing happening to certain modules.Some even do not install any 'own' tables and sprocs, but do change the desktopmodules / module definition tables. We get a time out on the DB connection. Something is halting the installation process.

Peter


Peter Schotman
Cestus Websites voor DotNetNuke oplossingen in Nederland
Contact us for your custom design and skinning work.
 
New Post
10/8/2009 2:52 PM
 

Posting followup:
10/6 8:30am to 8:45am, is the exact time frame when I executed a SQL to truncate 1 table and delete 2 others.
The first execution was with the DNN SQL tool which returned an error.  (similar to the one at the beginning of this thread)
The second was executed in SQL Analyzer and worked perfectly.

I received the SQL server filtered log file for this date and time period and there were "0" errors reported in SQL Server.
I also confirmed from the DBA's that there is a daily maintenance plan where the Indexes are rebuilt every night.
They also have the remote connection timeout set to 600ms (30 seconds).   Which I thought was only used to establish the initial connection not the connection time of a SQL execution.   Is 30 seconds resonable for what DNN does?

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQL Timeout expired errors when installing modules. DNN 5.1.2SQL Timeout expired errors when installing modules. DNN 5.1.2


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