If FileConvert 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
No backups are made (backup create and write rights)
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.
When two jobs touch on the same folder(s), FileConvert may give you a warning or it may
disable one of the jobs. Here are some common problems and how FileConvert 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, FileConvert will
disable Job B.
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:\office\scans".
Both jobs are looking for TIFF images to convert. Because Job B is handling
"c:\office\scans", Job A will ignore that folder, but will still handle the rest of the folders in
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:\backups". However, Job B's input folder is also
"c:\backups". Because Job B could change Job A's backup files, it will be disabled.
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). FileConvert 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
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. FileConvert will not stop you from creating a loop, but