DotNetNuke

Re: Item has already been added. Key in dictionary

liffey — Sat, 27 May 2006 09:59:56 GMT

I have finally come up with a solution to this problem, quite by accident!!!

I have moved to a dedicated server, away from shared hosting. Now that I have my own server I split all my sites into individual instances of DNN, with a few exceptions.

Since clearing all logs and any search related tables I have not had a single recurrence of this error on any of my sites (instances of DNN).

See my post here http://dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/118/threadid/37537/threadpage/2/scope/posts/Default.aspx

for a summary of my experiences on 3 different hostig providers / plans.

Declan

Re: Item has already been added. Key in dictionary

xberserker — Wed, 01 Mar 2006 23:55:14 GMT

SQL Statements:
delete from searchword;
delete from searchitem;

I did that and now my search doesn't pull up anything.
For example I have a employee directory with my name - Tosh
When I type in Tosh in the search it used to pull up my name.
And now notta! :(

And I have all these forms, some search words pull things up,
some don't. It worked great before I did the .... delete SQL Statements.

How would I get it back to the way it was????

Re: Item has already been added. Key in dictionary

dstruve — Tue, 27 Sep 2005 19:25:59 GMT

http://www.dotnetnuke.com/Default.aspx?tabid=795

if its critical search everywhere and see what you come up with. go to the link, you will see a search button.

Re: Item has already been added. Key in dictionary

liffey — Tue, 27 Sep 2005 19:10:33 GMT

Daniel,

which URL for the sub project? The Gallery? or one for SearchIndexing?

Declan

Re: Item has already been added. Key in dictionary

dstruve — Tue, 27 Sep 2005 18:01:22 GMT

Check the DotNetNuke SubProject Forum.
Can you post this to Gemini and ILL look into for you.

Daniel

Re: Item has already been added. Key in dictionary

liffey — Tue, 27 Sep 2005 17:04:37 GMT

As a matter of interest, is anyone having this problem also running the DNN Gallery?

I was having response and site down problems. My host (WH4L) provided me with a trace which pointed me to a page containing a DNN Gallery showing photographs. I removed this page and uninstalled the Gallery. I have not had a single error since and my site is running faster.

I do have Site indexing turned off but even so continued to receive the errors ("Item has already been added. Key in dictionary"). I am going to monitor it for 48 hours and then may turn indexing back on to see what happens!

Declan

Re: Item has already been added. Key in dictionary

adefwebserver — Fri, 23 Sep 2005 19:06:31 GMT

I am one more case of two instances of DNN 3.1.1 running on a single Windows 2000 server.

Re: Item has already been added. Key in dictionary

liffey — Fri, 23 Sep 2005 14:46:14 GMT

I wonder if that is the key - two instances of DNN? I also have 2 instances of DNN running. Should they not be running in separate address spaces? Could the services be common?

Cathal, any thoughts?

Declan

Re: Item has already been added. Key in dictionary

pmgerholdt — Fri, 23 Sep 2005 14:31:49 GMT

No web farm here, just a single server, but two instances of DNN 3.1.1 on it.

I'll try to get the opportunity to do IISRESET. But I had the search indexer disabled from Sept 8 to Sept 22.

Re: Item has already been added. Key in dictionary

liffey — Fri, 23 Sep 2005 14:00:39 GMT

This is the same as my findings. See Cathal's response.

I have since discovered that my site is running on 2 different servers which will tie in with Cathal's theory. I have posted a ticket with my host and referred them to this thread, in particular to Cathal's post.

I've left it disabled but it still runs and I have no errors.

Declan

Re: Item has already been added. Key in dictionary

pmgerholdt — Fri, 23 Sep 2005 13:48:59 GMT

I re-enabled indexing for the search engine with a time lapse of 180 (3 hours, right?) and I left the retry frequency blank, which means disabled.

I let it run overnight and I don't see any items in the log registering the 'key already exists' errors. That looks good.

However, I am puzzled by what I see in the history. It looks like the scheduler has the indexer scheduled twice. Each sets itself up to run three hours later, but the two instances are starting three minutes apart:

S: 9/23/2005 8:53:56 AM
E: 9/23/2005 8:55:00 AM
N: 9/23/2005 11:53:56 AM

S: 9/23/2005 8:50:59 AM
E: 9/23/2005 8:51:58 AM
N: 9/23/2005 11:50:59 AM

S: 9/23/2005 8:50:24 AM
E: 9/23/2005 8:51:30 AM
N: 9/23/2005 11:50:24 AM

S: 9/23/2005 8:39:20 AM
E: 9/23/2005 8:40:21 AM
N: 9/23/2005 11:39:20 AM

S: 9/23/2005 5:50:20 AM
E: 9/23/2005 5:51:22 AM
N: 9/23/2005 8:50:20 AM

S: 9/23/2005 5:41:53 AM
E: 9/23/2005 5:42:53 AM
N: 9/23/2005 8:41:53 AM

And cetera.

Re: Item has already been added. Key in dictionary

cathal — Fri, 23 Sep 2005 10:29:12 GMT

I think this is an issue with threads. Originally the scheduler worked by firing off independant threads to handle each scheduled task, and a master thread to control these. The master is there to respond to requests that alter the individual threads i.e. change their settings/disable them.

IMHO Some of the difficult to explain differences between people come from this. Some hosting companies run sites in a webfarm (often without their users knowing - so they can mainatin 99.99% uptime), and I would speculate that you get rogue threads, or threads no longer under control of the master. Additionally some of them seem to kill off some of the threads on occasion to optimise their servers, and this can lead to odd issues such as logs that haven't cleared down in months. This means when you stop a scheduled task, it may not stop. Also, when you upgrade a site, the old threads may continue to run the old code rather than the new ("fixed") versions. I've had at list 1 person confirm to me that after an upgrade search continued to fail in this manner for them, but after they unloaded the application pool, it then 'magically' started to work as expected.

In recent versions we added an additional option to the schedule mode. If you log in as host and go to host->host settings and expand out advanced->other settings, you can set the scheduler mode to 'request'. This works inline with the application, which means it has less of an overhead, but that it only works whilst the web application is active. This is fine for all of the dnn scheduled tasks, but if you've written custom tasks that you need to execute at a regular basis irregardless of whether the application is active, it may not suit.

If you haven't written custom scheduled tasks in this fashion, I'd recommend you change this setting to 'request mode', and if you have the ability, either unload the application pool, or restart IIS (e.g. with IISRESET), to be sure that no old code is hanging about.

Cathal

Re: Item has already been added. Key in dictionary

liffey — Fri, 23 Sep 2005 09:21:48 GMT

This I don't understand!

I have the schedule disabled since last night for
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKEDotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE.

The schedule item is not listed when I display the Schedule Status.

However if I view the schedule history for this item I get entries stating that it has run successfully!!!

Description

Duration (ms)

Succeeded

Start/End/Next Start

DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE

Completed re-indexing content

8.217

True

S: 23/09/2005 02:17:56
E: 23/09/2005 02:18:04
N: 23/09/2005 02:47:56

DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE

Completed re-indexing content

9.686

True

S: 23/09/2005 02:10:39
E: 23/09/2005 02:10:49
N: 23/09/2005 02:40:39

DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE

Completed re-indexing content

22.767

True

S: 23/09/2005 01:49:03
E: 23/09/2005 01:49:26
N: 23/09/2005 02:19:03

DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE

Completed re-indexing content

10.36

True

S: 23/09/2005 01:47:50
E: 23/09/2005 01:48:01
N: 23/09/2005 02:17:50

etc

Is it possible that 2 tasks are running and hence the dupliction conflicts?

Declan

Re: Item has already been added. Key in dictionary

pmgerholdt — Thu, 22 Sep 2005 20:37:53 GMT

Based on the advise from ecktwo's site, I ran the queries to clean out the search tables (had done so before) and increased the time between scheduled re-indexing from 30 to 180 minutes.

Ran the indexer and fingers crossed. Ditto on reporting back in the next day or so with results.

Re: Item has already been added. Key in dictionary

liffey — Thu, 22 Sep 2005 19:14:04 GMT

Ok ecktwo,

Let's see how it runs ...

I have disabled the schedule for SearchIndexing, set the Schedule Method (Host settings) to timer, reset IIS. This should ensure that indexing will not run while I run queries to delet table content as per your tutorial. I then cleared the log, ran the queries and Reindexed from the Search config page. No errors appeared in the log. I have re-enabled the schedule for indexing.

I'll report back with the results of leaving it run over-night.

Thanks for your tutorial link,
Declan