cjfraz

Im experiencing repeated crashes of WDS 3.01 on XP sP2 during indexing. 

 

Most, but not all crashes freeze the entire computer (even cntrl-alt-del not available), and I have no alternative but to hit the reset button.

 

Most, but not all crashes occur when indexing files on a network share (located on a SNAP server from Adaptec). 

 

WDS 2.6.x previously indexed all locations Im trying now after minimal tweaking.

 

I suspect it is just a few specific files or file types that are tripping up the indexer. So my specific question is, how can I tell which ones   Its frustrating that the index status window in 3.01 no longer shows you what file the indexer is working on.

 

Thanks,

 

J

 

ps- The only tweaks I had to make to 2.6 to get it to run well in this same environment involved reducing the types of files that were processed with full text indexing.  This is a big pain in 3.01 as the file types tab under the advanced options is terrible to work with.  Is there a more efficient way to tell WDS 3.01 something like

-          Index all files for file properties (except exclusions).

-          Index no files for full text/ full content (except inclusions / filters)

 

I loaded the group admin policy bundled with the install, but it wasn't much better for this issue.

 



Re: Windows Desktop Search Help WDS 3.01 crash during indexing

Eric Wolz - MSFT

Does any of these documents contain Chinese characters There was reported issues where the Windows XP Chinese wordbreaker was using high CPU.




Re: Windows Desktop Search Help WDS 3.01 crash during indexing

Jason Frazier

Nope, no Chinese characters.

The thing that had tripped up WDS 2.6.x was extremely large ascii files containing lots of numeric data. Telling WDS 2.6.x not to index the contents of those files cleared it up. Unfortunately, it's not been that easy to track down in 3.01.

Thanks.

J...





Re: Windows Desktop Search Help WDS 3.01 crash during indexing

Eric Wolz - MSFT

Try disabling indexing .xml files.




Re: Windows Desktop Search Help WDS 3.01 crash during indexing

Jason Frazier

No luck with disabling xml either. I now getting crashes while indexing local files routinely, and occasionaly get caught in a loop where the number of files to scan goes up indefinitely, while number scanned remains at 0.

I rolled back to an old disk image did a clean install, and quickly collected the following errors from the windows search service. I

Part of what makes this so difficult to troubleshoot is that the file types tab under advanced setting is terrible to work with. I'd like to let it scan once with no full text indexing of any file types, but it takes forever to work with this dialog and after the frist crash all my tedious work turning off the full text filter is undone!!

'm about at the end of the rope with this version of WDS. Any other help (before I give up) is much appreciated.

Thanks,

J...

Common errors:

Event ID 3026:

Advise Status Change failed. The system is probably low on resources. Free up resources and restart the service.

Context: Windows Application, SystemIndex Catalog

Details:

The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)

Event ID 3013:

The entry <D:\DOCUMENTS\OTHER\WEBS\COPY OF PD WEBSITE\IMAGES\NAVIGATION\NAVBAR_ELLIS\NAVBAR_ELLIS_B3_OVER.GIF> in the hash map cannot be updated.

Context: Windows Application, SystemIndex Catalog

Details:

A device attached to the system is not functioning. (0x8007001f)

Event ID 3024:

The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Windows Application, SystemIndex Catalog

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

Event ID 3026:

Advise Status Change failed. The system is probably low on resources. Free up resources and restart the service.

Context: Windows Application, SystemIndex Catalog

Details:

The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)

Event ID 3032:

A document ID cannot be freed.

Context: Windows Application, SystemIndex Catalog

Details:

The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)

Event ID 3090:

The gatherer files from the previous checkpoint cannot be restored, and this action cannot be completed. The gatherer will attempt to restore the files again. If the problem persists, restart the service, free system resources or verify that your hardware is working properly.

Context: Windows Application, SystemIndex Catalog

Details:

The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index. (0x8004117f)





Re: Windows Desktop Search Help WDS 3.01 crash during indexing

cjfraz

I never could track this down, but it seems it had something to do with the fact that I had originally installed Office 2007 when WDS 2.6 was still on board. When I restored a disk image from before the Office 2007 install, manually removed WDS 2.6, set up acrobat, added WDS 3.01, and THEN installed Office 2007, things worked much better. I haven't had any WDS 3.01 crashes while indexing the same disk since.

J...