SYMPTOMS
It could be that in certain rare cases two ZySCAN processing systems lock a single ZySCAN job for reading and do not unlock that specifc job. In order to restore access to the job make sure to create a backup of the ZySCAN job (directory) first before modifying the job content. Open the ZySCAN global options to obtain the Job Root directory path.
CAUSE
Locking for reading takes approximately up to 5 seconds. When the job is not unlocked during these 5 seconds, the Yellow lock will disappear and the process will try later on.
Yellow = Locked for reading
Orange = Locked for reading and writing to the job (during the import/OCR/export action)
Red = Locked for full control
Due to heavy resource usage on the indexing server, the feedback to the OCR/Export might take longer than 5 seconds causing the yellow lock to hang.
This could turn the yellow lock that could cause a external export/import process to be temporarily interrupted.
Other reasons could be:
The sequence.txt file in the job directory is corrupted, i.e. the contents does no longer match the sequence of the tiff files in the tiff folder.
RESOLUTION
Correctly arrange the content of the sequence.txt file, e.g. with notepad (or other text editor), in the same order as the sequence of the tiff images (as they appear in the documents).
Save the txt file so that the job should be accessible for further processing.
Open the job and process it manually in ZySCAN or use the ZySCANService.
It is also possible that the paths (fields, import, export directories) in the settings.txt are not correct.
In order to restore the job path, modify the paths to restore the correct path links based on the document file structure that is used; save the txt file and open and process the job again.
Example of a correct sequence: (notice the incremental numbers)
00000SDJHGFSDF1S6
00000SDJHGFSDF1S7
00000SDJHGFSDF1S8
00000SDJHGFSDF1S9
00000SDJHGFSDF1SA
00000SDJHGFSDF1SB
This should restore access to the specific ZySCAN job.
APPLIES TO
6.2; 6.2 Service Pack 1; 6.2 Service Pack 2; 6.3; 6.4
Comments
0 comments
Article is closed for comments.