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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForumForumFresh clean install & new database - Still no notificationsFresh clean install & new database - Still no notifications
Previous
 
Next
New Post
3/21/2008 2:02 PM
 

I have a completely new fresh clean install of DNN here - http://208.106.211.27/

On my old install I just can't get notifications so I did this to check the problem... but am getting nowhere.

I am adding other modules, that is all, to bring it in-line with my older installation (to switch to if needed to get this working!). But tests with a completely new installation, just forums added to it and it sheds no light and notifications don't work (except blank ones on deleting posts).

If anyone has an idea what this could be... would be great if a volunteer wants admin access to this portal to test with their own settings to see... I am at loose ends and it really can kill forums when people never get notifications to bring them back.

The DNN version is 4.6.2 (to keep in line with my other installation) and the Forums are v4.4.3.

Any & all help is appreciated.

Thanks

David

 
New Post
3/22/2008 2:17 PM
 

I am going to dig as deep as I possibly can into the issue of no notifications.  Kinda scrapped the test bit for now and looking into the data I have and where the problem really lies.

If anyone else has interest in this, or possible pointers please feel free to work with me!

I know a few people have similar problems, so if I somehow manage to find what it is I will certainly let everyone know.

Just learning SQL step-by-step as I am not a programmer... but for the Forum Notifications I have done a select * from Forum_EmailQueue_Tasks. Interestingly (for me just starting), I can see ALL notifications in the table, the last one that was sent successfully was 13 Jan 08, and the first to fail was 15 Jan 08. All other settings show as the same.

I was away at this time, so not a lot went on with the DNN and certainly no DNN updates to my knowledge!

So now I at least know when to look at in the event viewer. Will pop back next time I learn a little more...

 
New Post
3/22/2008 5:25 PM
 

 

From going through everything... my emails show on 13 Jan my host turned the database off because of high SQL CPU usage.  After this, the schedule was switched off as it was running with errors every minute and I just realised it has still been off.  I expect this stopped the emails, but I had thought odd to get blank notifications for deleting forum posts.

It really would be great if someone could look over these settings, and make recommendations if anything really doesn't look good. I will be monitoring the schedule & errors closely, but thankfully it is now on SQL Express on the local server (not shared) so I have control and no-one can just switch it off and block me!

I have also cleared out the EventLog & SiteLog tables.

When setting schedule items, should anything run on server? Or will it simply default if blank and run? (ie. I am not too sure what this means)

My Scheduler now shows:

Type Enabled Frequency Retry Time Lapse
DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE Enabled Every 1 Minute Every 15 Minutes
DotNetNuke.Services.Log.SiteLog.PurgeSiteLog, DOTNETNUKE Enabled Every 1 Day Every 2 Hours
DotNetNuke.Services.Scheduling.PurgeScheduleHistory, DOTNETNUKE Enabled Every 1 Day Every 2 Hours
DotNetNuke.Services.Log.EventLog.PurgeLogBuffer, DOTNETNUKE Enabled Every 1 Minute Every 15 Minutes
DotNetNuke.Services.Log.EventLog.SendLogNotifications, DOTNETNUKE Enabled Every 5 Minutes Every 30 Minutes
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE Enabled Every 3 Hours Every 3 Hours
DotNetNuke.Modules.Admin.ResourceInstaller.InstallResources, DOTNETNUKE Enabled Every 30 Minutes Every 2 Hours
DotNetNuke.Services.FileSystem.SynchronizeFileSystem, DOTNETNUKE Enabled Every 1 Hour Every 2 Hours
DotNetNuke.Services.Cache.PurgeCache, DOTNETNUKE Enabled Every 2 Hours Every 1 Hour
DotNetNuke.Modules.Events.EventNotification, DotNetNuke.Modules.Events Enabled Every 4 Hours Every 4 Hours
OnyakTech.Nuke
 
New Post
3/22/2008 5:48 PM
 

Errors hammering it already (several a minute).

One off:

THREAD ID: 11
TYPE: DotNetNuke.Services.Scheduling.PurgeScheduleHistory
EXCEPTION: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
RESCHEDULED FOR: 3/22/2008 11:21:56 PM
SOURCE: STARTED_FROM_TIMER
ACTIVE THREADS: 2
FREE THREADS: -1
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 2
IN QUEUE: 11
Server Name: DEDL55

others:

  22/03/2008 21:22:03   General Exception       AssemblyVersion: -1; PortalID: -1; PortalName ...
AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Could not load type ''.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.Web.HttpException: Could not load type ''. ---> System.ArgumentException: String cannot have zero length. at System.Reflection.Assembly._GetType(String name, Boolean throwOnError, Boolean ignoreCase) at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) --- End of inner exception stack trace --- at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) at DotNetNuke.Framework.Reflection.CreateType(String TypeName, String CacheKey, Boolean UseCache, Boolean IgnoreErrors)
Source:
Server Name: DEDL55

and

22/03/2008 21:22:03   General Exception       AssemblyVersion: -1; PortalID: -1; PortalName ...
AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Value cannot be null. Parameter name: type
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at DotNetNuke.Framework.Reflection.CreateObject(String TypeName, String CacheKey) at DotNetNuke.Services.Search.ModuleIndexer.GetModuleList(Int32 PortalID)
Source:
Server Name: DEDL55

and

 

22/03/2008 21:22:26   Scheduler Exception       AssemblyVersion: -1; PortalID: -1; PortalName ...
AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Services.Scheduling.DNNScheduling.SqlDataProvider.PurgeScheduleHistory() at DotNetNuke.Services.Scheduling.DNNScheduling.DNNScheduler.PurgeScheduleHistory() at DotNetNuke.Services.Scheduling.PurgeScheduleHistory.DoWork()
Source:
Server Name: DEDL55

 

All of those started appearing 41 secs after the scheduler started, and around 3 times each in 1m19secs.

That is surely too much?

 
New Post
3/22/2008 6:23 PM
 

Well... short space of time and over 60 error messages.

And now when I go to the schedule I get a timeout message.  Too tired to keep going today.

Any help appreciated... I really want to take whatever time is necessary to sort this.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForumForumFresh clean install & new database - Still no notificationsFresh clean install & new database - Still no notifications


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