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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Event Log getting huge due to numerous errors...Event Log getting huge due to numerous errors...
Previous
 
Next
New Post
3/10/2011 9:46 AM
 
This is going to contain a lot of info, but I thought better to fully explain so I can get the help needed to fix these issues. I have a DNN Instance that was upgraded from 4.9.0 to 5.6.0... All sites sunction normally (with the exception of some not being able to access the HTML editor correctly - I have another thread on this).

My system admin has told me that the log file for this particular site is getting big fast... if he purges/truncates the log within a day it will grow to 1GB or more... Below are some of the more common errors that show up. They will happen every few seconds for minutes at a time.

How can I do to remendy these issues. I have no idea what these mean:

AssemblyVersion: 5.6.0
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: aca9e1db-71c6-498f-931b-4b7818ff466b
InnerException: Violation of UNIQUE KEY constraint 'IX_Dnn_SearchItemWord'. Cannot insert duplicate key in object 'dbo.Dnn_SearchItemWord'. The statement has been terminated.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Data.SqlClient.SqlConnection.
StackTrace:
Message: System.Data.SqlClient.SqlException (0x80131904): Violation of UNIQUE KEY constraint 'IX_Dnn_SearchItemWord'. Cannot insert duplicate key in object 'dbo.Dnn_SearchItemWord'. The statement has been terminated. at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection. (SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() 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.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteScalar() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Data.SqlDataProvider.AddSearchItemWord(Int32 SearchItemId, Int32 SearchWordsID, Int32 Occurrences) at DotNetNuke.Services.Search.SearchDataStore.AddIndexWords(Int32 indexId, SearchItemInfo searchItem, String language) at DotNetNuke.Services.Search.SearchDataStore.StoreSearchItems(SearchItemInfoCollection SearchItems)
Source:
Server Name: WEBSERV01



AssemblyVersion: 5.6.0
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 48f14c6c-278e-4a1a-9d8d-d196f144e34c
InnerException: Collection index must be in the range 1 to the size of the collection.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: Microsoft.VisualBasic.Collection.IndexCheck
StackTrace:
Message: System.IndexOutOfRangeException: Collection index must be in the range 1 to the size of the collection. at Microsoft.VisualBasic.Collection.IndexCheck(Int32 Index) at Microsoft.VisualBasic.Collection.get_Item(Int32 Index) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.ScheduleQueueContains(ScheduleItem objScheduleItem) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.AddToScheduleQueue(ScheduleHistoryItem objScheduleHistoryItem) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.WorkCompleted(SchedulerClient& objSchedulerClient)
Source:
Server Name: WEBSERV01



I also get a lof of these errors - the Type will change however they are all related tot eh scheduler:

THREAD ID: 81
TYPE: DotNetNuke.Services.Search.SearchEngineScheduler
EXCEPTION: 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.
RESCHEDULED FOR: 3/9/2011 5:11:35 PM
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: 0
FREE THREADS: 1
READER TIMEOUTS: 6516
WRITER TIMEOUTS: 6109
IN PROGRESS: 4
IN QUEUE: 9
Server Name: WEBSERV01

Below is a screen grab of the scheduler... does this look correct? Should I remove anything? Please let me know.


 
New Post
3/10/2011 9:23 PM
 
timeout is referring to a lack of resources. The first error might be solved by clearing the search index tables (please read here: http://www.deutschnetnuke.de/tabid/134/Default.aspx)

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/11/2011 9:41 AM
 
Sebastian Leupold wrote:
timeout is referring to a lack of resources. The first error might be solved by clearing the search index tables (please read here: http://www.deutschnetnuke.de/tabid/134/Default.aspx)

 I have done that and also the following just to make sure:

go to Host :: SQL. copy&Paste the following lines, check "Execute Script" and hit run:
TRUNCATE TABLE {databaseOwner}{objectQualifier}EventLog GO
TRUNCATE TABLE {databaseOwner}{objectQualifier}ScheduleHistory GO
TRUNCATE TABLE {databaseOwner}{objectQualifier}SiteLog GO
TRUNCATE TABLE {databaseOwner}{objectQualifier}SearchItemWordPosition GO
DELETE FROM {databaseOwner}{objectQualifier}SearchItemWord GO DELETE FROM {databaseOwner}{objectQualifier}SearchWord
GO
DELETE FROM {databaseOwner}{objectQualifier}SearchItem
GO









I will see if this helps control the errors. Can anyone else explain possibly what the other errors are for?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Event Log getting huge due to numerous errors...Event Log getting huge due to numerous errors...


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