* This functionality is available for Advanced users only.
* There is no page limit for any one document that is imported to Nextpoint.
When a document batch is uploaded/imported, Nextpoint automatically reports the actions taken during the import, as well as any follow up needed and/or warnings that have been triggered.
To view the details of your import batch navigate to the Imports tab and click on the Batch Name:
On the Batch Report page, you will see four tabs: Details, PST Processing, Pending Nextpoint QA and Warnings:
Details: A summary of all items processed, documents created, and any other processing actions that were executed normally during the import.
PST Processing: This tab contains a processing summary for all PST files in your batch. If there are any PST errors, they are named and the exact locations of the errors (i.e. Inbox, Drafts, Deleted Items) are listed.
- PST File Summaries report the count of all files in the PST (total), and the count of files in each directory contained in the PST.
- PST Errors report the count of files not extracted or processed from the PST, and their location.
PST Error Solution
Nextpoint is able to process most PST files. If you have received a PST Error in your Batch Report, there is corruption within the PST and at least one files has not been extracted correctly. The PST file most likely needs to be repaired and uploaded again.
To repair a PST you can follow this short tutorial from Microsoft: How to repair your Outlook PST. Please make sure to make a backup copy of the original PST file before attempting repair.
If the unextracted files within the PST have occurred in locations that are of no consequence to your review, (e.g. Calendar, Tasks, etc.) you may choose to ignore the errors and proceed. We urge you to please review the errors carefully before continuing.
If you need additional assistance, please contact Nextpoint support at email@example.com or (888) 929-NEXT Ext. 3 for help.
Pending Nextpoint QA: Processing anomalies are reported here. Nextpoint engineers will take action to resolve these issues. Any issues that cannot be resolved by our team and require user action will be moved to the Warnings tab for further investigation by the end user.
Warnings: Processing warnings are reported here.
Here is a list of the Warnings that we see most frequently, as well as the suggested solutions you can employ to resolve them. If you receive a warning message that is not listed here, please email firstname.lastname@example.org and we will take a closer look.
- File required too much memory to process or document had too many pages to process: When processing fails for these reasons, it typically is due to corruption, complexity, password protection or sheer size of the file. In most situations it is just not practical, or even possible - to process these files into a document image.
- Extracted page count didn't match expectation: This is typically similar to the previous warning, except the import made a bit more progress—enough to know that we expected to receive some document pages, but during processing the file was found to be corrupt, very large/complex or password protected—and could not be processed as expected.
- An error occurred converting document to PDF: These are typically unsupported file types, but processing was attempted because the file extension wasn't in our file type blacklist. This error could also be due to corrupt/large/complex/password protected files.
- Couldn't convert uploaded image to PNG: These are normally images with a strange makeup. Most frequently it's seen on small, busy graphics (complex company logos, etc). Most commonly, this error occurs for images that would not be sought via search or likely to be reviewed.
- Break the file up into smaller documents.
- Remove password protection from the file.
- If the file is corrupt, attempt to re-save the file.
- Many image processing errors can be resolved by printing the file to PDF.