Tweet
Hi, I'm running the 5.1 Build 1002 indexer on Windows Server 2003, and it's crashing, with the only thing written to the end of the corrupted zoom_output.txt being the line Status: 128. What does Status 128 mean and how do I correct it? I couldn't find any mention of a Status 128 anywhere online or in the documentation. None of the data files are written out when this happens, the whole process exits. It seems to happen frequently, but not always. Each invocation of the indexer is spidering subdirectories of a fileserver where it's indexing anywhere from 500 to 6000 pdf's, varying in size from 50k to 500k. The tail of the log looks like
[11:15:14] Processing PDF file http://pdfserver:8080/documents/Docs/2010/04/16/in48.pdf
[11:15:14] DL Thread #1, got URL (http://pdfserver:8080/documents/Docs/2003/08/29/in51.pdf) off queue
[11:15:14] Downloading file http://pdfserver:8080/documents/Docs/2003/08/29/in51.pdf
[11:15:14] Indexing http://pdfserver:8080/documents/Docs/2010/04/16/in48.pdf
[11:15:14] Index Thread
Status: 128
[11:15:14] Processing PDF file http://pdfserver:8080/documents/Docs/2010/04/16/in48.pdf
[11:15:14] DL Thread #1, got URL (http://pdfserver:8080/documents/Docs/2003/08/29/in51.pdf) off queue
[11:15:14] Downloading file http://pdfserver:8080/documents/Docs/2003/08/29/in51.pdf
[11:15:14] Indexing http://pdfserver:8080/documents/Docs/2010/04/16/in48.pdf
[11:15:14] Index Thread
Status: 128
Comment