Stéphane, Jordan or Peter,

I too am seeing this error and after reading this thread I also began to see the process abort at the 2 minute mark. I know it's not a script timeout as I can run other scripts without a timeout issue. For example I moved all the documents to a new storage provider and that took a good 15-20 minutes and the script never threw an error.

This was never a problem till I attempted to upgrade go Version 05.02.09 and now I'm currently on 05.02.10. I'm running 05.02.02 in production and do not have any problems re-indexing the portal. The script with the older version runs for about 20 minutes and then completes. My development box is running DNN 04.09.05, DMX 05.02.10, IIS 6, Windows 2003 Server. IIS timeout is set to over 200 minutes and the app pool is setup with full control. The control and the execution timeout are the only things that are different between production and development at this time. When the script fails I get the thread aborted error listed above, and with some additional digging I found the following error in the event viewer. I'm not sure if this will help or not but wanted to pass this along. Any additional information or if anyone has resolved this problem would be greatly appreciated.

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 9/9/2010
Time: 11:33:59 AM
User: N/A
Computer: 200599-MIGRATIO
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 9/9/2010 11:33:59 AM
Event time (UTC): 9/9/2010 4:33:59 PM
Event ID: c469999735cd4dd781996c661d2d5d3b
Event sequence: 48
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/760326274/Root-8-129285234547493447
Trust level: Full
Application Virtual Path: /
Application Path:
Machine name: 200599-MIGRATIO

Process information:
Process ID: 3280
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: ThreadAbortException
Exception message: Thread was being aborted.

Request information:
Request URL:/RunScriptExecute.aspx
User host address:
User:
Is authenticated: True
Authentication Type: Forms
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.ApplicationStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)


Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Thanks Arick. It's too early to say if this is indeed the clue that will crack the case but I'll definitely examine this closer.

Peter

Update on this issue:

I have made some tweaks to the run script code for version 5.3.0. Instead of stalling this issue by trying to determine what causes it, I think I have soemthing of a workaround. It centers on "chunking" processing into smaller batches. So the reindexing does n records at a time. This should resolve most of the cases mentioned, IMO. Someone with this issue tried some code in a separate module to this effect and that worked.

Peter

Are there any news on this topic?

Or is there a quick fix for the current version?

 

Hi Guys,

I'm working on the 5.3 release full time. Unfortunately I'm also dealing with an internet interruption due to the incompetence of Swisscom. My gut feeling is that the module is now really ready (I'm just testing, testing, testing now ... every day). But more tests await tomorrow.

Peter

The new version is out. Let me know how it goes.

Peter

Just to share my experience.

I was having problems with the lucene index and last night I tried to reindex the portal. Got the same error described in this thread and so i decided to upgrade DMX to the latest version (5.03.02).

Error was still there.

After 2 minutes, the script would just die. To perform the upgrade, I moved the production portal to a test server. On the test server the reindexing worked with no issues. 

Since the 2 servers are identicals, and the portal was just restored from the production machine, the only thing left to check was iFilters.

I reinstalled version 6 of iFilter downloaded from the adobe site, rebooted the server and everything started working. Reindexing finished very quickly with no errors.

Only problem left now is that not all content is indexed. but that's a different story.....

 

hope it can help somebody.

 

Vincenzo

Hi Vicenzo,

I have another idea about the cause. It could be due to content no longer being there or just not in the database either. Check if there are records in DMX_Entries that have Entry='' and EntryType LIKE 'File.%'. Those records are files without anything in the storage. Another is where the actual file has disappeared from the disk. I will solidify the code for this scenario. Note that you can force the reindexing to continue by fidgeting with the querystring StartRec parameter. Force it to go on by setting that to 50 higher than the last run.

Peter

Hi,

with DMX 5.3.x my probs are gone. Good work!!