Troubleshooting

This topic describes some of the errors you might encounter.

Skipped Files

If QuikFile encounters a file that it can’t convert, it will note an error in the logs and give the file a Skipped status. QuikFile may skip a file for any of these reasons:

• The file is corrupt
• The file has incompatible PDF features
• The file format isn’t supported
• The file is encrypted or secured by a password
• The file is in use by another program
• The PDF file already has OCR text
• The PDF file is text-based or has text elements
• The file is a Word document and you’re running QuikFile as a service (see below)

When QuikFile skips a file, it won’t try to convert the file again. But you can force QuikFile to try again. See Redo Files for instructions.

Network Drives

If you’re running QuikFile as a service, you should use UNC paths instead of mapped drive letters for all network drives. See Run as a Service for more information.

Permission Issues

QuikFile must have network and share read, write, modify, create, and delete rights for the:

• source drive
• source folder(s)
• source file(s)
• backup drive
• backup folder(s)
• target drive
• target folder(s)
• separators database folder

If QuikFile lacks the proper rights, any of the following could happen:

• No files get converted (source read rights)
• The source files never get deleted (source delete rights)
• The same files get converted over and over (source create and delete rights)
• The source files disappear but the converted files never show up (target create and write rights)
• No backups are made (backup create and write rights)

Office Files

In order for Microsoft Word documents to convert, Word must be installed and running on the same machine where QuikFile is installed.

Duplex Documents Don’t Separate Properly

If you scan with a duplex scanner and separators and you find that your documents aren’t separating properly, try using duplex separators. Duplex separators are something that you print yourself. Just print the same separator on both sides of the paper.

Overlapping Jobs

When two jobs touch on the same folder(s), QuikFile may give you a warning or it may disable one of the jobs. Here are some common problems and how QuikFile handles them:

Same Input Folder

Suppose that Job A and Job B both have the same input folder(s) and both look for the same file types. Since these jobs are directly competing with each other, QuikFile will disable Job B.

Overlapping Jobs

Suppose that Job B’s input folder(s) are within Job A’s input folders, and both jobs look for the same file types. Since some of Job A’s input folders are covered by another job, Job A will ignore those folders.

Example: Job A covers "c:office" and all of its subfolders. Job B covers "c:officescans". Both jobs are looking for TIFF images to convert. Because Job B is handling "c:officescans", Job A will ignore that folder, but will still handle the rest of the folders in "c:office".

Converting a Backup Folder

Suppose that Job B is set to convert Job A’s backup folder. Job B will be disabled.

Example: Job A backs up its originals to "c:ackups". However, Job B’s input folder is also "c:ackups". Because Job B could change Job A’s backup files, it will be disabled.

Job Chains

Suppose that Job A’s output folder is Job B’s input folder. This is a chain, since documents get passed along from one job to the next. There is nothing inherently wrong with this, but it can introduce a risk of creating a loop (see next item). QuikFile may give you a warning if it detects a chain that could turn into a loop.

Example: Job A converts files and places them in "c:office". Job B’s input folder is also "c:office". This isn’t a problem unless Job B passes its converted files back into Job A’s input folder.

Job Loops

Suppose that Job A’s output folder is Job B’s input folder. Likewise, Job B’s output folder is Job A’s input folder. This is a loop. QuikFile will not stop you from creating a loop, but realize that it could lead to a never ending conversion run.

Example: Job A watches "c:TIFF" for new TIFF files. It converts them to image-only PDF and outputs them to "c:PDF". Job B watches "c:PDF" for new image-only PDF files. It converts them to TIFF and outputs them to "c:TIFF". This creates a loop. A new file will be endlessly converted back and forth from TIFF to PDF and passed back and forth between the folders.