Using DMX 5.2.4 on DNN 5.3.1 the re-indexing script fails after about 100 documents have been indexed.  This fails consistently on two separate server installations with the following error:

00:01:57.562 -    Reindex P/N 422581, 9Z Valve (EntryId 93) Success
00:01:58.375 -    Reindex P/N 422582, 13Z Valve (EntryId 94) Success
00:01:59.171 -    Reindex P/N 422745, 15Z Valve (EntryId 95) Success
00:01:59.968 -    Reindex P/N 422811, 9Z Dummy (EntryId 96) Success
00:02:00.781 -    Reindex P/N 422812, 13Z Dummy (EntryId 97) Error!
 Error!
00:02:01.500 -  Thread was being aborted.
 Error!
00:02:01.500 -  Thread was being aborted.

[ThreadAbortException: Thread was being aborted.]
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +486
   System.Web.ApplicationStepManager.ResumeSteps(Exception error) +501
   System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) +123
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +379

I need to re-index all of the documents because all document attribute data and titles were assigned via SQL when moving from an older DMX to new DMX on new framework.  Lucene is only recognizing those docs indexed prior to script fail.  If we step into the modify attribute screen and then finish without changing data, the document gets indexed.  However, we have alot of documents and this would be a painstaking effort.  Any help would be appreciated.  Thanks.

 

 

Hi Aaron,

I'll make a note and see if there is a break point somewhere that could have been hit.

Peter

Hi Peter,

getting the same error. Increased timeout in web.config but it desn#t solve the problem.

Any ideas what could happend?

Hi Stephan,

My guess is that IIS killed the process as it was using iFilters. Are you running medium trust?

Peter

I am having this same issue. The reindex appears to timeout after exactly 2 minutes on each attempt. Here is a sample log.

00: - Retrieving Settings
00: - PortalId: Success
00: - TabId: Success
00: - ModuleId: Success
00: - Finding Script: Success
00:00:00.015 - Reading 'D:\Inetpub\PublicPortal\DesktopModules\Bring2mind\DMX\Admin\Scripts\ReindexPortal.Resources': Success
00:00:00.015 - Script title: Reindex Portal 00:00:00.015 - Checking permission: Success
00:00:00.015 - Script description: This script will reindex all found entries in the current portal.
00:00:00.015 - Instantiating Bring2mind.DNN.Modules.DMX.Services.Search.SearchController, BRING2MIND.DNN.MODULES.DMX.CORE: Success
00:00:00.015 - Reindexing Portal NoaNet BTOP Portal
00:00:04.500 - Reindex NoaNet (EntryId 1) Success
00:00:04.625 - Reindex RW Plan Example (EntryId 3) Success
00:00:04.859 - Reindex noanet_routes (EntryId 5) Success
00:00:04.984 - Reindex SW WA 2 (EntryId 6) Success
00:00:05.109 - Reindex RW Plan Example (EntryId 7) Success
00:00:05.343 - Reindex Application Guidelines (EntryId 9) Success
00:00:06.218 - Reindex NoaNet Application Package (EntryId 10) Success
00:00:18.281 - Reindex Round 1 (EntryId 11) Success
00:00:18.437 - Reindex Application Guidelines (EntryId 12) Success
00:00:19.390 - Reindex NoaNet Application Package (EntryId 13) Success
00:00:31.421 - Reindex team_docs (EntryId 14) Success
00:00:31.546 - Reindex PM (EntryId 15) Success
00:00:31.656 - Reindex Contact List 050710 (EntryId 16) Success
00:00:31.843 - Reindex Noanet_project management plan 042610 v3.1 (EntryId 17) Success
00:00:32.156 - Reindex Reference (EntryId 18) Success
00:00:32.296 - Reindex BasemapWithRoutes_10-05-21 (EntryId 19) Success
00:00:32.875 - Reindex NoaNet 2008 logo (EntryId 20) Success
00:00:33.015 - Reindex NoaNet WA POP list (EntryId 21) Success
00:00:33.156 - Reindex TelecomExchangeMap11x17 as of 2 Apr 10 (EntryId 22) Success
00:00:33.640 - Reindex Sub-Participants (EntryId 23) Success
00:00:33.765 - Reindex Black Rock Cable (EntryId 24) Success
00:00:33.875 - Reindex Bellingham-Deming (EntryId 25) Success
00:00:34.609 - Reindex Black Rock Route (EntryId 26) Success
00:00:35.578 - Reindex Black Rock new (EntryId 29) Success
00:00:35.703 - Reindex Pacific County PUD (EntryId 30) Success
00:00:35.828 - Reindex Pacific_BTOP Participant Data Request Form (EntryId 31) Success
00:00:35.984 - Reindex Pacific_SBToTokeland1 (EntryId 32) Success
00:00:36.578 - Reindex Pacific_SBToTokeland2 (EntryId 33) Success
00:00:37.203 - Reindex Pacific_SBToTokeland3 (EntryId 34) Success
00:00:37.703 - Reindex Pacific_SouthBendToHagen1 (EntryId 35) Success
00:00:38.078 - Reindex Pacific_SouthBendToHagen2 (EntryId 36) Success
00:00:38.625 - Reindex Pacific_SouthBendToHagen3 (EntryId 37) Success
00:00:38.921 - Reindex Pacific_SouthBendToHagen4 (EntryId 38) Success
00:00:39.171 - Reindex Pacific_SouthBendToHagen5 (EntryId 39) Success
00:00:39.453 - Reindex Pacific_SouthBendToHagen6 (EntryId 40) Success
00:00:39.687 - Reindex Pacific_SBtoHagen Shape Files (EntryId 41) Success
00:00:39.812 - Reindex Archive created by free jZip (EntryId 42) Success
00:00:39.937 - Reindex Pacific_SBtoHagen Shape Files (EntryId 43) Success
00:00:40.046 - Reindex SBtoHagen.shp (EntryId 44) Success
00:00:40.187 - Reindex SBtoHagen (EntryId 45) Success
00:00:40.312 - Reindex Pacific_SBToTokeland Shape Files (EntryId 46) Success
00:00:40.437 - Reindex Archive created by free jZip (EntryId 47) Success
00:00:40.546 - Reindex Pacific_SBToTokeland Shape Files (EntryId 48) Success
00:00:40.671 - Reindex SBToTokeland.shp (EntryId 49) Success
00:00:40.796 - Reindex SBToTokeland (EntryId 50) Success
00:00:40.937 - Reindex Port of Whitman County (EntryId 51) Success
00:00:41.046 - Reindex Clarkston to Spokane (EntryId 53) Success
00:00:44.656 - Reindex Clarkston to Spokane (EntryId 54) Success
00:00:44.953 - Reindex SawNet Technologies (EntryId 55) Success
00:00:45.078 - Reindex BTOP I - Sawtooth Data Request final 051110-pjh (EntryId 56) Success
00:00:45.296 - Reindex Sawtooth White Salmon to Snowden to Appleton to Glenwood to Ponderosa UPDATED 5_10_2010 (EntryId 57) Success
00:00:45.640 - Reindex Skamania County Environmental Assessment (EntryId 58) Success
00:00:46.156 - Reindex Washougal to North Bonneville to Stevenson to Stabler to Mill A UPDATED 5_10_2010 (EntryId 59) Success
00:00:46.796 - Reindex Washougal to North Bonneville to Stevenson to Stabler to Mill A UPDATED 5_10_2010 (EntryId 60) Success
00:00:48.031 - Reindex White Salmon to Snowden to Appleton to Glenwood to Ponderosa UPDATED 5_10_2010 (EntryId 61) Success
00:00:48.593 - Reindex Yakima County (EntryId 62) Success
00:00:48.734 - Reindex Harrison Hill fiber (EntryId 63) Success
00:00:48.968 - Reindex Landfill to Noanet fiber (EntryId 64) Success
00:00:49.312 - Reindex Possible Buena - Zillah Routes (EntryId 65) Success
00:00:49.578 - Reindex Sunnyside Library route (EntryId 66) Success
00:00:49.937 - Reindex Sunnyside WorkSource (EntryId 67) Success
00:00:50.171 - Reindex YVCC Yak-Grdvw Fiber (EntryId 68) Success
00:00:50.671 - Reindex Upload (EntryId 69) Success
00:00:50.796 - Reindex CHR (EntryId 71) Success
00:00:50.921 - Reindex Contact List 052710 (EntryId 72) Success
00:00:51.078 - Reindex Pacific_SouthBendToHagen1 (EntryId 73) Success
00:00:51.437 - Reindex BTOP I - Participant Data Request final Klickitat (EntryId 74) Success
00:00:51.656 - Reindex Klickitate County Environmental Assessment (EntryId 75) Success
00:00:52.234 - Reindex Sunnyside Fiber Map update 05210 (EntryId 76) Success
00:00:52.546 - Reindex BTOP I - Participant Data Request final 051110 (2) (EntryId 77) Success
00:00:52.734 - Reindex Clallum PUD (EntryId 78) Success
00:00:52.843 - Reindex Clallam County PUD (EntryId 79) Success
00:00:52.968 - Reindex Clallam County PUD (EntryId 80) Success
00:00:53.078 - Reindex 1a (EntryId 81) Success
00:00:53.328 - Reindex 1b (EntryId 82) Success
00:00:53.562 - Reindex 2 (EntryId 83) Success
00:00:53.765 - Reindex 3a (EntryId 84) Success
00: - Reindex 3b (EntryId 85) Success
00:00:54.218 - Reindex Alternate (EntryId 86) Success
00:00:54.468 - Reindex BTOP I - Participant Data Request Response (EntryId 87) Success
00:00:54.640 - Reindex Franklin County PUD (EntryId 88) Success
00:00:54.765 - Reindex noanetadmin (EntryId 89) Success
00:00:54.875 - Reindex Noa Net fils (EntryId 90) Success
00:01:03.687 - Reindex PM (EntryId 91) Success
00:01:03.828 - Reindex Reference (EntryId 92) Success
00:01:03.968 - Reindex Mapping (EntryId 93) Success
00:01:04.078 - Reindex GIS (EntryId 94) Success
00:01:04.203 - Reindex CAD (EntryId 95) Success
00:01:04.312 - Reindex OSP Contstruction (EntryId 96) Success
00:01:04.437 - Reindex Specs (EntryId 97) Success
00:01:04.562 - Reindex Contracts (EntryId 98) Success
00:01:04.671 - Reindex Contractor Invoices (EntryId 99) Success
00:01:04.781 - Reindex Electronics (EntryId 100) Success
00:01:04.890 - Reindex Specs (EntryId 101) Success
00:01:05.015 - Reindex Contracts (EntryId 102) Success
00:01:05.125 - Reindex Contractor Invoices (EntryId 103) Success
00:01:05.234 - Reindex Environmental Assessment (EntryId 104) Success
00:01:05.359 - Reindex Project Maps (EntryId 105) Success
00:01:05.484 - Reindex blackrock (EntryId 106) Success
00:01:05.593 - Reindex franklin (EntryId 107) Success
00: - Reindex pacific (EntryId 108) Success
00:01:06.125 - Reindex Bellingham-Deming (EntryId 109) Success
00:01:06.781 - Reindex Black Rock new (EntryId 110) Success
00:01:06.906 - Reindex Black Rock Route (EntryId 111) Success
00:01:07.875 - Reindex Pacific_SouthBendToHagen6 (EntryId 112) Success
00:01:08.125 - Reindex Pacific_BTOP Participant Data Request Form (EntryId 113) Success
00:01:08.296 - Reindex Pacific_SBToTokeland1 (EntryId 114) Success
00:01:08.875 - Reindex Pacific_SBToTokeland2 (EntryId 115) Success
00:01:09.500 - Reindex Pacific_SBToTokeland3 (EntryId 116) Success
00:01:09.765 - Reindex Pacific_SouthBendToHagen1 (EntryId 117) Success
00:01:10.140 - Reindex Pacific_SouthBendToHagen2 (EntryId 118) Success
00:01:10.687 - Reindex Pacific_SouthBendToHagen3 (EntryId 119) Success
00:01:10.984 - Reindex Pacific_SouthBendToHagen4 (EntryId 120) Success
00:01:11.250 - Reindex Pacific_SouthBendToHagen5 (EntryId 121) Success
00:01:11.515 - Reindex Pacific_SBToTokeland Shape Files (EntryId 122) Success
00:01:11.640 - Reindex Archive created by free jZip (EntryId 123) Success
00:01:11.765 - Reindex Pacific_SBToTokeland Shape Files (EntryId 124) Success
00:01:11.890 - Reindex SBToTokeland.shp (EntryId 125) Success
00:01:12.031 - Reindex SBToTokeland (EntryId 126) Success
00:01:12.156 - Reindex Pacific_SBtoHagen Shape Files (EntryId 127) Success
00:01:12.281 - Reindex Archive created by free jZip (EntryId 128) Success
00:01:12.406 - Reindex Pacific_SBtoHagen Shape Files (EntryId 129) Success
00:01:12.515 - Reindex SBtoHagen.shp (EntryId 130) Success
00:01:12.656 - Reindex SBtoHagen (EntryId 131) Success
00:01:12.781 - Reindex Heraldsepa (EntryId 132) Success
00:01:12.937 - Reindex SEPA115oh (EntryId 133) Success
00:01:13.062 - Reindex SEPALetters (EntryId 134) Success
00:01:13.234 - Reindex 2005-12-07_ABB overview and budgetary estimate (EntryId 135) Success
00:01:13.500 - Reindex Attachment A (EntryId 136) Success
00:01:13.640 - Reindex Attachment B (EntryId 137) Success
00:01:13.937 - Reindex Submarine Power Cables (EntryId 138) Success
00:01:14.406 - Reindex Subsea Power Cables (EntryId 139) Success
00:01:14.640 - Reindex subcableproposal (EntryId 140) Success
00:01:14.781 - Reindex Route_Shapes_20100615 (EntryId 141) Success
00:01:14.953 - Reindex yakima (EntryId 142) Success
00:01:15.078 - Reindex Assessment and Maps (EntryId 143) Success
00:01:15.234 - Reindex ECRegion (EntryId 144) Success
00:01:15.359 - Reindex EC-1Route (EntryId 145) Success
00:01:15.500 - Reindex EC1RouteMaps_11x17Portrait (EntryId 146) Success
00:01:16.656 - Reindex EC1RouteMapIndex_11x17Portrait (EntryId 147) Success
00:01:16.890 - Reindex EC-2Route (EntryId 148) Success
00:01:17.015 - Reindex EC-3Route (EntryId 149) Success
00:01:17.125 - Reindex EC-4Route (EntryId 150) Success
00:01:17.250 - Reindex EC-5Route (EntryId 151) Success
00:01:17.359 - Reindex EC-6Route (EntryId 152) Success
00:01:17.468 - Reindex SCRegion (EntryId 153) Success
00:01:17.593 - Reindex SC-1Route (EntryId 154) Success
00:01:17.703 - Reindex SC-2Route (EntryId 155) Success
00:01:17.812 - Reindex SC-3Route (EntryId 156) Success
00:01:17.937 - Reindex SC-4Route (EntryId 157) Success
00:01:18.046 - Reindex SERegion (EntryId 158) Success
00:01:18.171 - Reindex SE-1Route (EntryId 159) Success
00:01:18.281 - Reindex SE-2Route (EntryId 160) Success
00:01:18.390 - Reindex SE-3Route (EntryId 161) Success
00:01:18.515 - Reindex SWRegion (EntryId 162) Success
00:01:18.625 - Reindex SW-1Route (EntryId 163) Success
00:01:18.734 - Reindex SW-2Route (EntryId 164) Success
00:01:18.859 - Reindex SW-3Route (EntryId 165) Success
00:01:18.984 - Reindex SW-4Route (EntryId 166) Success
00:01:19.093 - Reindex NCRegion (EntryId 167) Success
00:01:19.234 - Reindex NC-1Route (EntryId 168) Success
00:01:19.343 - Reindex NWRegion (EntryId 169) Success
00:01:19.453 - Reindex NW-1Route (EntryId 170) Success
00:01:19.562 - Reindex EC1RouteMaps_11x17Landscape (EntryId 171) Success
00:01:20.718 - Reindex sawnet (EntryId 172) Success
00:01:20.843 - Reindex Figures (EntryId 173) Success
00:01:20.953 - Reindex EAST CENTRAL ROUTE EC-1 Final Draft (EntryId 174) Success
00:01:21.546 - Reindex Figures and Maps (EntryId 175) Success
00:01:21.671 - Reindex EA Maps (EntryId 176) Success
00:01:21.812 - Reindex EAFigures_EC-1RouteMaps (EntryId 179) Success
00:01:22.843 - Reindex EAFigures_EC-2RouteMaps (EntryId 180) Success
00:01:23.406 - Reindex EAFigures_EC-3RouteMaps (EntryId 181) Success
00:01:23.718 - Reindex EAFigures_EC-3RouteMaps (EntryId 183) Success
00:01:24.046 - Reindex EAFigures_EC-3RouteMaps (EntryId 184) Success
00:01:24.562 - Reindex EC-4Route (EntryId 185) Success
00:01:24.671 - Reindex EAFigures_EC-3RouteMaps (EntryId 186) Success
00:01:24.984 - Reindex EA Report Map EC-4 - Final Production - 062710 (EntryId 187) Success
00:01:25.375 - Reindex EAFigures_EC-5RouteMaps (EntryId 188) Success
00:01:25.671 - Reindex EAFigures_EC-6RouteMaps (EntryId 190) Success
00:01:26.031 - Reindex ECRegion (EntryId 191) Success
00:01:26.140 - Reindex EC-1Route (EntryId 192) Success
00:01:26.265 - Reindex EA Report Map EC-1 - sub submittal - 062810 v1 (EntryId 193) Success
00:01:27.265 - Reindex EC-2Route (EntryId 194) Success
00:01:27.390 - Reindex EA Report Map EC-2 - Final Production - 062710 (EntryId 195) Success
00:01:27.890 - Reindex EC-3Route (EntryId 196) Success
00:01:28.015 - Reindex EA Report Map EC-3 - Final Production - 062710 (EntryId 197) Success
00:01:28.312 - Reindex EC-5Route (EntryId 198) Success
00:01:28.421 - Reindex EA Report Map EC-5 - Final Production - 062710 (EntryId 199) Success
00:01:28.734 - Reindex EC-6Route (EntryId 200) Success
00:01:28.859 - Reindex EA Report Map EC-6 - sub submittal 062810 v1 (EntryId 201) Success
00:01:29.218 - Reindex EC-4Route (EntryId 202) Success
00:01:29.328 - Reindex EAST CENTRAL ROUTE EC-1 Final Draft (EntryId 203) Success
00:01:29.484 - Reindex EAST CENTRAL EC-2 Final Draft (EntryId 204) Success
00:01:29.890 - Reindex EAFigures_EC-4RouteMaps (EntryId 209) Success
00:01:30.281 - Reindex EAFigures_SE-3RouteMaps (EntryId 210) Success
00:01:30.578 - Reindex East Central Route EC-1 Final Draft - June 21 (EntryId 211) Success
00:01:30.984 - Reindex East Central Region_Route EC-6 Final Draft June 21 (EntryId 215) Success
00:01:31.484 - Reindex Summary Report (EntryId 216) Success
00:01:31.609 - Reindex EA Arch Report EC-1 - working - 062810 v1 (EntryId 217) Success
00:01:33.281 - Reindex EMAIL_NoaNet_EC 2_draft_report (EntryId 218) Success
00:01:34.140 - Reindex EMAIL_NoaNet_EC-3_draft_report (EntryId 219) Success
00:01:34.437 - Reindex EMAIL EC4_draft_report (EntryId 220) Success
00:01:36.296 - Reindex EMAIL_NoaNet_EC-5_draft_report (EntryId 221) Success
00:01:36.640 - Reindex EA Arch Report EC-6 - working - 062810 v1 (EntryId 222) Success
00:01:36.953 - Reindex SWRegion (EntryId 223) Success
00:01:37.062 - Reindex SW-1Route (EntryId 224) Success
00:01:37.187 - Reindex SW-2Route (EntryId 225) Success
00:01:37.296 - Reindex SW-3Route (EntryId 226) Success
00:01:37.421 - Reindex SW-4Route (EntryId 227) Success
00:01:37.546 - Reindex NCRegion (EntryId 228) Success
00:01:37.656 - Reindex NC-1Route (EntryId 229) Success
00:01:37.765 - Reindex NWRegion (EntryId 230) Success
00:01:37.890 - Reindex NW-1Route (EntryId 231) Success
00:01:38.015 - Reindex SCRegion (EntryId 232) Success
00:01:38.125 - Reindex SC-1Route (EntryId 233) Success
00:01:38.234 - Reindex SC-2Route (EntryId 234) Success
00:01:38.359 - Reindex SC-3Route (EntryId 235) Success
00:01:38.468 - Reindex SC-4Route (EntryId 236) Success
00:01:38.578 - Reindex SERegion (EntryId 237) Success
00:01:38.703 - Reindex SE-1Route (EntryId 238) Success
00:01:38.828 - Reindex SE-2Route (EntryId 239) Success
00:01:38.953 - Reindex SE-3Route (EntryId 240) Success
00:01:39.062 - Reindex EA Report Map SE-1 - Final Production - 062710 (EntryId 242) Success
00:01:39.687 - Reindex EA Report Maps NW-1 - Final Production - 062810 (EntryId 245) Success
00:01:40.359 - Reindex EA Report Map NC-1 - Final Production - 062810 (EntryId 246) Success
00:01:40.640 - Reindex SECTION NW Region_NW1 June 21 (EntryId 250) Success
00:01:41.234 - Reindex EA Review (EntryId 251) Success
00:01:41.359 - Reindex pow (EntryId 252) Success
00:01:41.484 - Reindex EMAIL_NW1_draft_report (EntryId 254) Success
00:01:42.265 - Reindex EMAIL_NoaNet_SE1_draft_report (EntryId 255) Success
00:01:42.765 - Reindex EA Report Maps EC-1 - Final Production - 062810 (EntryId 256) Success
00:01:43.765 - Reindex EMAIL JW_SE2_draft_report (EntryId 257) Success
00:01:50.515 - Reindex EA Report Map EC-6 - Final Production - 062810 (EntryId 258) Success
00:01:50.906 - Reindex Document Management Procedures v2 (EntryId 259) Success
00:01:51.046 - Reindex clallam (EntryId 262) Success
00:01:51.156 - Reindex EA Review (EntryId 263) Success
00:01:51.281 - Reindex EA Review (EntryId 264) Success
00:01:51.406 - Reindex EA Review (EntryId 265) Success
00:01:51.531 - Reindex EA Report Maps NW-1 - sub submittal - 062210 v1 (EntryId 266) Success
00:01:52.218 - Reindex EA Report NW-1 -sub submittal - 062210 v1 (EntryId 267) Success
00:01:52.796 - Reindex EA Report - EC-1 - sub submittal - 062210 v1 (EntryId 278) Success
00:01:53.187 - Reindex EA Report EC-6 - sub submittal - 062210 v1 (EntryId 279) Success
00:01:53.687 - Reindex EA Report Map SE-1 - sub submittal - 062810 v1 (EntryId 282) Success
00:01:54.312 - Reindex EA Report SE-1 - sub sbumittal - 062210 v1 (EntryId 283) Success
00:01:54.750 - Reindex EA Report SE-1 sub submittal - 062210 v2 (EntryId 286) Success
00:01:55.171 - Reindex tokept.zip (EntryId 287) Success
00:01:58.250 - Reindex EA Review (EntryId 294) Success
00:01:58.390 - Reindex EA Report NC-1 - sub submittal - 063010 v1 (EntryId 295) Success
00:01:59.171 - Reindex EA Report Map NC-1 - sub submittal - 062810 v1 (EntryId 296) Success
00:01:59.484 - Reindex BTOP1 EA Map remarks 6 30 10 (EntryId 298) Success
00:01:59.671 - Reindex EA Report Maps SW-2 - Final Production - 062810 (EntryId 302) Success
00:02:00.625 - Reindex EA Report Maps SW-3 - Final Production - 062810 (EntryId 303) Error!
Error!
00:02:00.750 - Thread was being aborted.
Error!
00:02:00.750 - Thread was being aborted.

I apologize; I now see that this issue is marked as resolved in a later version than we are running. I will upgrade and see if that corrects it.

I just upgraded to to 5.2.9 and am still experiencing the same problem. I will do some deeper research. Please let me know if there is any specific info I can provide.

Hello,

We're running into the same issue (5.2.9), 2 minutes as well.
Did you find a solution?

Best regard,
Stéphane.

I am having the same problem... about 2 minutes before I get the error. I looked in IIS and web.config and made all of the timout values very high to test and I still get the error. I search for a document and I get no results, even when there are many documents with the word I searched in the title.

Does anyone know how to make this work?
 

Thanks!

Hi guys,

I'm afraid that the bug should come from the component itself (and not due to a server settings) because I tested the "Export" script this morning and it has been running successfully for more than 5 minutes.

Peter any ideas?

Best regard,
Stéphane.

I don't know if this post will help you, but it seemed to work for Tim:

http://www.bring2mind.net...tpage/1/Default.aspx

(simply run the script to add DMX Search to DNN Search Results page)

Hi Jason,

Thank for the tip but I've already seen this post and the provided solution didn't work.

Best regard,
Stéphane.

Peter, I saw that you were asking about the asp.net trust level earlier. I did try to set my trust level to full in the web.config, but it still aborted after exactly 2 minutes. I cannot find any settings in the web site coniguration, application pool, or asp.net machine-level configuration that would indicate a 2-minute timeout. I also tried this via both http & https.

Thanks in advance for your attention and assistance.

In general, I'm wondering which storage provider you would recommend for performance and scalability - file or SQL? My DMX_Repository table in SQL has grown to almost 2GB. I would prefer to keep the file storage in SQL for security and backup reasons, since my web server is in a DMZ.

Hi All,

There are a couple of reasons a thread gets aborted:

1. The server decides it has run long enough (executionTimeout setting in web.config) and aborts the thread. You can determine if it is this by looing at the time before the abort and comparing that to the value in the web.config (default is 90 secs I believe).

2. The server decides the code is dangerous and closes down the thread. This is Pandora's box as I suspect that many things can lead to this. Only: as long as you remain in managed code (.net) (and you run full trust) this should not happen. The indexing uses unmanaged code however (it is the only place in the application where this happens) because it needs to use iFilters that are not .net but server components. Under normal circumstances this doesn't lead to any issues, but if the iFilter that has been loaded has a fit then anything can happen. Unfortunately this is not "catchable"by .net. In other words: I can't do anything about that. I can't make the process continue with the next document for instance.
To check this: does it always stop at the same document? If so is this the first time a docuemnt of this type (Word/Excel/etc) gets indexed? If not: is this document maybe particular (i.e. does the document itself cause the iFilter to abort)?

The above should help in determining the cause of the fault. As said there is not an awful lot DMX can do to help. We keep an eye out for anything we can do in this regard.

Peter

Peter,

Thank you for your repy! I got it to work! I read the MSDN .NET information from Microsoft regarding the httpRuntime element (http://msdn.microsoft.com...brary/e1f13641.aspx) and a Dotnetnuke forum that mentioned the httpRuntime element (http://www.dotnetnuke.com...posts/Default.aspx). I needed to add the "executionTimeout="90" attribute to the httpRuntime element in my web.config!

 

Thanks!

Matt

Peter, thanks for the detail.

To clarify to your points, the ThreadAbortException always happens almost exactly as the counter reaches 2 minutes. That seems like to much of a coincidence to not be a timer-based issue. It rarely aborts on the same file or even file type.

00:01:58.531 -    Reindex EA Report Map SE-1 - Final Production - 062710 (EntryId 242) Success
00:01:59.328 -    Reindex EA Report Maps NW-1 - Final Production - 062810 (EntryId 245) Success
00:02:00.171 -    Reindex EA Report Map NC-1 - Final Production - 062810 (EntryId 246) Success
00:02:00.562 -    Reindex SECTION NW Region_NW1 June 21 (EntryId 250) Success
00:02:01.187 -    Reindex EA Review (EntryId 251) Success
00:02:01.343 -    Reindex pow (EntryId 252) Success
00:02:01.546 -    Reindex EMAIL_NW1_draft_report (EntryId 254) Error!
 Error!
00:02:01.703 -  Thread was being aborted.
 Error!
00:02:01.703 -  Thread was being aborted.
 

I have set my executionTimeout to 20 minutes and ASP.NET to use full trust in the web.config.

    1200" />

    Full" originUrl=".*" />

Still, this behavior is consistent. Do the details above completely count out the 2 reasons you've listed as possible causes, or is there something else I could be missing? Has anyone seen the Reindex operation successfully complete after running longer than 2 minutes?

Hi Peter,

As I said others scripts are running for far more than 5 minutes with no exception being thrown. So that should not be a configuration exception imho.

Plus I agree with Jordan when he said that the 2 minutes cannot be a coincidence (overall if many people run into it). I even tried to remove "faulty" documents with no luck, it still broke on the next one after the same amount of time.

Finally, I'm running in Full Trust as well.

Best regard,
Stéphane.

Hi Jordan, Stephane,

A consistent time indeicates indeed a server timing related issue. It could be that the flavor of IIS you're running has another mechanism to cut off after x seconds. You'll need to dig into this yourselves. I've gone through the reindex script with a fine comb and there are no possible thread aborts anywhere that can be called. The server cuts this off.

Here's another rumour about thread amputations: I read somewhere that IIS can cut off a process if it causes "massive" changes to the file system. I've never actually seen this in action and it would seem very silly. But it's another one to Google on.

My 2cts,

Peter

Jordan,

Did you fix it?

Gtz,
Stéphane.