Table of Contents
- Overlaps
- Page number difference
- Uploader at incorrect stage
- Server interruption
-
Load file errors
- Multiple native files
- Conflicts with a previous image
- Error modifying - document in flight
- Error unable to rewrite PDF
- Error timeout rewriting PDF
- “No image reader” error
- Error finding file or directory
Uploading document sets with a load file can be a complex and error-prone process. This article will go over some common errors that you may encounter uploading or modifying your documents via the Processed Uploader. You can find general documentation on uploading processed data with a load file here and PDFs without a load file here.
Overlaps
By default, Everlaw does not allow for documents with overlapping Begin Bates or overlapping Bates ranges. But you can skip documents with overlapping Bates ranges and continue uploading documents that do not overlap with other documents in the same upload or same database. For example, when uploading CAT001 (3 pages) and CAT002 (1 pages), these documents would be flagged as overlapping Bates ranges because CAT001 (as a three-paged document) reserves CAT001, CAT002, and CAT003 and as result overlaps CAT002.
In choosing which overlapping document is uploaded/skipped, Everlaw selects the overlapping document with a lower Bates number to be uploaded and skips any overlapping documents with a higher Bates number. Here, CAT001 would be uploaded because it has the lower Bates number compared to CAT002.
In the alternative, you can enable the Overlapping Bates setting for your database so that you can ignore overlapping Bates warnings and continue uploading documents with overlapping Bates ranges to the same database. Learn more about the “Overlapping Bates” setting.
Overlaps document within same upload [Internal overlap]
In this case, the upload contains documents that have a range of Bates numbers that overlaps with other documents in the same upload. For example, let’s say you are uploading five documents with the following Begin Bates numbers:
-
- ABC001 (3 pages)
- ABC002 (2 pages)
- ABC003 (1 page)
- ABC004 (4 pages)
- ABC005 (5 pages)
Here, the “internal overlap” error appears because ABC002 and ABC003 overlap with ABC001, and ABC005 overlaps with ABC004.
At this point you can take one of the following actions:
- You can rename ABC002 and ABC003 so that they no longer overlap with ABC001 then rename ABC005 so that it no longer overlaps with ABC004. Be sure to rename files so that they do not overlap any other documents contained in the same upload or database.
- You can skip errors and continue which will skip uploading ABC002, ABC003, and ABC005 then proceed to upload the remaining documents (ABC001 and ABC004) that do not have overlapping Bates numbers. You can also perform a modification upload instead, which you can learn about in this help article.
- You can enable the Overlapping Bates setting for your database then “ignore warnings and continue” which will upload all the documents including ABC002, ABC003, and ABC005 (assuming there are no other errors). Learn more about the “Overlapping Bates” setting.
Overlaps existing document [External overlap]
In this case, the upload contains documents that have a range of Bates numbers which overlap with documents that are already on the platform. For example, let’s assume that ABC004 (4 pages) was previously uploaded onto your database and you are now uploading four documents with the following Begin Bates numbers:
-
-
-
-
- ABC006 (1 page)
- ABC007 (2 page)
- ABC008 (1 pages)
- ABC009 (2 page)
-
-
-
Here, the “overlaps existing document” error appears because ABC006 and ABC007 overlap with an existing document (ABC004) on your database.
At this point you can take one of the following actions:
- You can rename ABC006 and ABC007 so that they no longer overlap with ABC004 or any other documents contained in the same upload or database.
- You can skip errors and continue which will skip uploading ABC006 and ABC007 then proceed to upload the remaining documents (ABC008 and ABC009) that do not have overlapping Bates numbers. You can also perform a modification upload instead, which you can learn about in this help article.
- You can enable the Overlapping Bates setting for your database then ignore warnings and continue which will upload all the documents including ABC006 and ABC007 (assuming there are no other errors). Learn more about the “Overlapping Bates” setting.
Modification error: Extension of end Bates number overlaps existing document
This error occurs when you change the Bates numbering of documents through a modify, causing the documents to overlap with documents already on the platform. You will need to change the name of some documents, or consider switching the overlapping documents to a page separator system. You can also enable the Overlapping Bates setting and then start a new upload. Learn more about the “Overlapping Bates” setting.
Page number difference
- Error preparing "/ENRON001/IMAGES/ENRON0002.pdf": ENRON0002 is 2 pages, but "/uploads/IMAGES.pdf" had 1 pages.
This means that the number of pages provided in the load file is different than the number of pages present in the PDF that you have pointed the system to.
This could mean that you have single-page PDFs, all images for the same document, which Everlaw does not support. They will need to be combined into PDFs or converted into image format. Once you have converted the documents, you can click Rescan or change folders to point the uploader to the correct place.
It could also mean that there is in an error in the page count column in the load file. You can consult the OPT file (if available) to confirm the correct Page Count. If there is a discrepancy with the load file, update the load file with the correct page count.
Uploader at incorrect stage
- Upload stage is [IncorrectStage]. Expected stages: [ExpectedStage]
This is an error that happens when the frontend has not caught up with the stage of the upload. The page will show that you are on one step of the upload, but the uploader recognizes it’s actually on the next stage. This can happen if there is a problem with your internet connection or if your browser is struggling to load the next stage. To get your webpage to catch up, click OK.
Server interruption
The server was interrupted while [Task]
Server interruption errors may also come in the form of "Error uploading files. Timeout on read" or "Client closed connection unexpectedly."
These errors mean that the upload has stopped, either because of an internal issue or an interruption in internet connection. To resume the upload, verify that your internet connection is stable and select Resume [Task]. In some instances, you may have to reselect the folders.
Load file errors
Error parsing load file
- Fix your load file and replace it
- [X] line(s) in your load file have syntax errors
- Error using separator [Separator] and encapsulator [Encapsulator]
This error occurs when the some or all of the load file can not be parsed. This can happen in many ways, including, but not limited to the following:
- There are more columns in a line than expected
- There are fewer columns in a line than expected
- There is an extra separator character present in a line
- There are too few separators or encapsulators in a line (These are what define what values belong to each cell in the load file. Common separators and encapsulators are commas, quotation marks, DC4 (also known as ASCII 20 (0x14)) "", and the thorn character "þ"
This error will display what lines were skipped as a result of the error and what separator and encapsulator are used in your load file. Any erroneous lines will be skipped and you will have the option to proceed with your upload by ignoring these errors. Please note that by selecting Skip errors and continue you will NOT upload all of the documents in your processed upload. Skipping these files and continuing with the upload will skip documents associated with the erroneous lines.
If you would like to fix the errors in your load file, select "Download error report and load files" to download a .ZIP containing three items:
- A .DAT containing only the valid lines of your original load file
- A .DAT containing the lines that could not be parsed
- A .CSV that lists what errors were found and which lines the errors occur on. You can use this error .CSV to help troubleshoot your original load file.
The .CSV list of errors skips the first row and column of the .DAT load file. This means that if there is an error listed for row 79, the corresponding line in the .DAT file would be row 80.
Note that if the first two lines of your load file can not be parsed, these errors will not be stored.
The error .CSV may contain any of the following entries.
| Error message |
Explanation |
| Encountered more than [x] characters |
This error happens when a line has more characters than is able to be processed. There may be missing line and row breaks in your load file. |
| Line [x] is connected to errors on line [y] |
This error occurs when an error is found on a multi line row. You must fix the errors on line [y] for line [x] to be parsed. |
| Expected at least [x] columns but found [y] |
The uploader could not find the necessary number of columns in this row. Your load file must have at least two columns. |
| Expected [x] columns but found [y] |
The uploader could not find the necessary number of columns in this row. This can be caused by extra separators or missing separators on the erroneous line. |
| There were more than [x] columns |
This error happens when a line has more columns than is able to be processed. There may be missing line and row breaks in your load file. |
| A row had more than [x] characters |
This error happens when a line has more characters than is able to be processed. There may be missing line and row breaks in your load file. |
| An encapsulator [character] seems to be missing |
Encapsulators are the characters that surround each entry in your row. This error occurs when an entry in your row is missing an encapsulator, either before or after it. |
| Invalid escape character after encapsulator |
This error is caused by extra characters in your load file that are not encapsulated. Check to make sure there are no extraneous characters in your load file. |
|
Encapsulator in the middle of an unencapsulated cell |
This error is caused by extra encapsulators in your load file. Check to make sure there are no extraneous characters on this line. |
| Non-special character after escape character |
This error is caused by extra characters in your load file that are not encapsulated. Check to make sure there are no extraneous characters in your load file. |
|
Non-separator after closing encapsulator |
This error is caused by extra characters in your load file that are not encapsulated. Check to make sure there are no extraneous characters in your load file. |
|
Reached end-of-input in the middle of an encapsulated cell |
The load file ended before the last line was entirely parsed. Double check that your load file is complete and that the last line is properly formatted. |
Error defining identity fields
- Fix your load file and replace it
- [X] out of [Y] rows in your load file have logical errors
- Error using Bates prefix [Bates]
This error occurs when the data in the load file is malformed. This can happen in many ways, including but not limited to, the following:
- There are overlapping Bates ranges in the load file
- A necessary column (such as beginBates) can not be found
- When there are invalid entries in special columns.
Any erroneous lines can be skipped and you will have the option to proceed with your upload without uploading these documents. Please note that by selecting Skip errors and continue, you will not upload all of the documents in your processed upload. Skipping these files and continuing with the upload will skip documents associated with the erroneous lines.
If you would like to fix the errors in your load file, select Download error report and load files to download a .ZIP containing three items
- A .DAT containing only the valid lines of your original load file
- A .DAT containing the lines that could not be parsed
- A .CSV that lists what errors were found and which lines the errors occur on. You can use this error .CSV to help troubleshoot your original load file.
The .CSV list of errors skips the first row and column of the .DAT load file. This means that if there is an error listed for row 79, the corresponding line in the .DAT file would be row 80.
The error .CSV may contain any of the following entries.
| Error | Explanation |
| Empty [begin Bates column]: Should have a beginBates. | The column you have chosen as your begin Bates column does not have any values. |
| Encountered non-bates in [begin Bates column]: [x] | There is a value in your chosen begin Bates column that does not match your Bates Numbering scheme. |
|
Invalid begin bates in [begin Bates column]: [x] |
There is a valid Bates number in your begin Bates column, but it can not be a begin Bates value. |
|
Bates prefix "#" is reserved for Everlaw control numbers |
Your begin Bates column includes a document whose prefix is '#', and there is not a native document in your database with this control number. If you are performing an upload, select "Change identity fields" from the error banner. On the Identity fields page, select "Assign Bates prefix". If you are performing an overlay, confirm that the load file references a document that exists in this database. |
| Repeated bates number: [x] | A begin Bates number has appeared multiple times in your begin Bates column. |
| Empty [page count column]: Should have a pageCount. | The column you have chosen as your page count column does not have any values. |
| Invalid page count in [page count column]: [x] | There is a value in your page count column that is not a valid page count number. |
| Empty [end Bates column]: Should have an endBates. | The column you have chosen as your end Bates column does not have any values. |
| Encountered non-bates in column [end Bates column]: [x] | There is a value in your chosen end Bates column that does not match your Bates numbering scheme. |
| beginBates [Bates number] cannot precede endBates [Bates number] | A Bates range in your load file has a larger value for the beginning of the range than the end of the range. Double check the Bates ranges of your documents. |
| Internal overlap: [Bates number] overlaps with [Bates number] | There is a range of Bates numbers that overlap. Double check the Bates ranges of your documents. |
| Cannot determine page count from [begin Bates number] and [end Bates number] |
Everlaw could not automatically determine the page count from this Bates range. This error requires a .OPT file to resolve. |
|
Page count conflict with pageRange [x] and pageCount [y] |
The page range and page count for this document do not align. This error requires a .OPT file to resolve. |
Multiple native files
- Multiple native files, duplicate named [X]
When there are multiple files with the same name as a document present in the native path, the system cannot determine which to upload as the native file. This commonly happens when you point to a native directory that also contains the image files and both are .PDFs. To deal with this, you want to reorganize the files if necessary, select Try again, and reselect the folders.
Conflicts with a previous image
- Image conflicts with a previous image for # page
This occurs when multiple images were provided for the same document page. You can remove the extraneous files and upload them separately under another name if necessary.
Error modifying - document in flight
- Error verifying modifications: “Not yet published by upload”
This error means that a document that you are trying to modify is not yet uploaded, but is still in progress from a previous upload. This can happen when a previous upload is in an error state. You will have to find the upload that the document was originally present in and complete it or remove the errored documents from the original upload. Once you have fixed the previous upload, you can retry the upload documents stage on this upload.
Error unable to rewrite PDF
- Error preparing "/ReplacementFiles/images/#812088.1.pdf": Unable to rewrite pdf
This generally means the file is corrupt (i.e. doesn’t conform to the PDF spec).
Error timeout rewriting PDF
- Error preparing "/ENRON000001/pdfs/ENRON001.pdf": Timeout rewriting pdf
This means the file took too long to fix in a reasonable time. This can sometimes be fixed offline.
“No image reader” error
- Error preparing “/images/0143/ENRON2341273.tif": No image reader for /mnt/uploads/1098/30907/02/8156/0235/1.tif
This error means that the uploader could not read the image file. For example, this may include documents that have a size of 0 kb.
Error finding file or directory
- Failed to upload [filename]: Frontend error: NotFoundError: A requested file or directory could not be found at the time an operation was processed.
This typically occurs when the user is uploading from a network that the uploader tool cannot access. It can be avoided by uploading directly from the user's computer/local drive, instead of the network.
This can also occur when the file path character limit has been surpassed. The limit is 255 characters from the first number of the IP address to the last letter of the file path. The solution is to change the file name or path so that it contains fewer characters. Then, retry the upload.
0 Comments