Common issues are caused by the following:
-
The workstation is not licensed for DIP.
-
User does not have network rights to access the import index file.
-
User does not have rights to the Destination Disk Group location.
-
In Process Settings, configure correct Field Type (Ordered or Tagged), Separator (New Line, Tab, Custom) and Field Delimiters (None, Single Quote, Double Quote) according to your index file.
-
Check field order configuration and DIP Index file (Make sure # of fields in the configuration and in the index file are matched).
-
Make sure to format Currency and Date Keyword Values, if they are used.
-
The files to be imported or the import index file does not exist in the specified directory.
-
The Workstation is not properly licensed for OCR when you attempt to use the OCR on Commit option.
The following table explains some common issues:
Issue |
Description |
---|---|
Unable to make file Read Only - error 74 |
The machine the user logged on to does not have sufficient network rights to change the import index file attributes. |
Cannot view the documents that have been imported, although the user has rights to the document type and the disk group location. |
Confirm that you have rights to renditions in the document type. |
DIP process is bringing in blank images. |
Check the Verification Report. If it states Could not open file…, copy the file path/full path from the import index file and browse to that location to verify that the files are present. |
It appears as if not all documents identified in the import index file have been imported. The Verification Report indicates that all items have been imported. |
Check the Document Import Configuration Process Settings. If the Append Additional Pages to Existing Document option is selected, the DIP appends documents to existing documents by matching Keyword Values of the imported document to those of an existing document. This functionality applies only to image files. |
DIP shows an extra “0” in the auto-name string |
Check to see if numeric values contained in the import index file are formatted in accordance with the corresponding Keyword Type. For example, if the Keyword Type Check Amount contains decimal places and the check value being imported does not contain decimal points, an extra 0 may appear in the Auto-Name string. |
DIP batch remains in DIP- Awaiting Commit queue rather than moving to Scan - Awaiting Commit queue even though configured to do so. |
Select box Send On Error in the DIP Processing Paths dialog box. Selecting this box will enable the batch to proceed to the Scan queue for further indexing even if a required Keyword Type is missing in the DIP batch. |
Correctly-processed Import Index files are being placed in the ERROR_FILES folder |
If multiple Import Index files are processed into a single batch and successfully-processed Import Index files are configured to not be deleted, Import Index files that have been correctly processed may be moved to the ERROR_FILES folder if one or more Import Index files that compose the batch are not processed correctly. DIP cannot distinguish between the Import Index files in the batch that had errors and those that processed correctly. All Import Index files in the process folder, including those that were processed correctly, are moved to the Error Files folder. Tip:
To prevent correctly-processed Import Index files from ending up in the Error Files folder, configure each Import Index file to be processed as an individual batch or allow the Index Import files to be deleted after processing (the default behavior), but configure the Index Import file to be backed up during the configuration for the DIP process. All correctly-imported Import Index files will be deleted after processing, the incorrectly-processed Import Index files will be moved to the Error Files folder, and all processed Import Index Files are backed up to the configured location. Note:
If a batch contains one or more corrupt image files, the batch will process correctly, but the corrupted files are not imported into OnBase. The batch is moved to the Awaiting Commit queue, but the Import Index file is moved to the ERROR_FILES folder. |
After importing multi-page TIFF images, only the first page of each document is displayed if the Document Type of the documents have a Default File Format of something other than Image File Format. |
Images files are treated slightly differently than other file formats in a DIP process because the process attempts to open image files to determine the number of pages (i.e. individual images) included in each file. In this scenario, the DIP process is not expecting to find a single file consisting of multiple pages (i.e. images), so only the first image in the file is displayed. To prevent this issue from occurring, include the >>File Type Default Keyword Type in the Import Index File to force the DIP process to recognize the file being imported as an image and open it to determine the number of pages (i.e. images) it contains. In this case, the >>File Type Default Keyword Type should be specified as 2 for Image File Format. Note:
In a Tagged DIP Process, the File Format must be specified before the path to the file. However, in an Ordered DIP, the File Format can be placed after the path to the file, if desired. Note:
If you are importing files of a file format that is different from the Document Type's Default File Format, you must include the >>File Type Default Keyword Type in the Import Index file. If the >>File Type Default Keyword Type is not added, you are unable to view your imported documents. For more information on Document Type Default File Format considerations, see Document Type Default File Format Considerations. |
The process fails even though it appears to be configured correctly. |
Ensure that if you are using the >>File Path Default Keyword Type, you are supplying an absolute path for its value. If a full path is supplied, the process will fail to run. The >>File Path Default Keyword Type must be used with the >>File Name Default Keyword Type. |
While a scheduled DIP process is running, new import files are removed from the processing directory before they are imported. |
Enable the Files idle for at least 1 minute option in Schedule Management. This allows newly created import files to be copied to the directory while the process is running and still have those files successfully imported into the system. |
The following error occurs when running a process: One or more files were not able to backup successfully. All files have been left in their current directory and no processing was performed. |
This error occurs when the Backup Path option is enabled and the processing workstation is unable to access the configured Backup Path. This can happen if the processing workstation is unable to access the configured file path, or if the Backup Path field was left blank during configuration. Ensure that a Backup Path has been configured within OnBase Configuration, and make sure that the processing workstation is able to access the configured path. |