Organization Admin: Common Processed Data Errors

This article covers organization admin functionalities, which are available to certain users with contracts covering unlimited database creation. 

Table of Contents

 

This article will go over some common errors that you may encounter uploading or modifying your documents via the organization admin page. If you would like the general documentation on uploading processed documents, please consult this article

Return to table of contents

Overlaps

    • Overlaps loadfile documentoverlaps_loadfile_document.png
    • In this case, the loadfile contains documents that overlap with each other, loadfile-internally. You will need to rename the overlapping files for the upload to work.
    • Overlaps existing document
      overlaps_existing_document_error.PNG
    • In this case, the loadfile contains documents that overlap with documents that are already on the platform. You may need to perform a modification upload instead, which you can learn about in this help article
    • Modification error: Extension of end Bates number overlaps existing document
      extension_overlap.png
    • 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. Click “Try a different loadfile” and navigate to the fixed loadfile once you have corrected the error.

Return to table of contents

Page number difference

    • Error preparing "/ENRON001/IMAGES/ENRON0002.pdf": ENRON0002 is 2 pages, but "/uploads/IMAGES.pdf" had 1 pages.pages_wrong.png
    • This means that the number of pages provided in the loadfile 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.

Return to table of contents

Uploader at incorrect stage

    • Error [defining special columns on 2017/10/16 ENRON006. Upload stage is AnalyzeMetadata instead of DefineSpecialColumnsUploader_Stage_Error.png
    • 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. To get your webpage to catch up, just refresh the page. Note that if you have many uploads running at the same time, it will interrupt them and you will need to redirect the uploader to the correct files. Fortunately, they will resume uploading from the same document. If you would like to avoid having to restart running uploads, then you can just open the uploader in a new page and the upload stage should be correct.

Return to table of contents

Timeout on read error

  • Error uploading files. Timeout on Read"timeout.png
  • "Client closed connection unexpectedly"client_shutdown.png

Both of these errors mean that the upload has stopped, either because of an internal issue or an interruption in internet connection. To resume the upload, simply select “Upload Files.” You may have to reselect the folders.

Return to table of contents

Error normalizing loadfile

“Load file contains syntax errors.”

1961.png

This error occurs when the entire load file can not be parsed. This can happen in many ways, including when there are more columns in a line than expected, when there are fewer columns in a line than expected, when there is an extra separator character present in a line, when there are too few separators in a line, or missing quote characters. Any erroneous lines will be skipped and you will have the option to proceed with your upload by ignoring these errors. Please note that selecting Continue anyway will NOT upload all of the documents in your processed upload, and will skip documents associated with the skipped lines.

If you would like to fix the errors in your load file, select Download errors to download a .ZIP containing three items: 1. A .DAT containing only the valid lines of your original load file, 2. A .DAT containing the lines that could not be parsed, and 3. 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.

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.

Return to table of contents

 

 

Error defining special columns

“Load file contains malformed information”

1962.png

This error occurs when the data in the load file is malformed. This can happen in many ways, including when there are overlapping Bates ranges in the load file, when a necessary column (such as beginBates) can not be found, or 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 selecting Continue anyway will NOT upload all of the documents in your processed upload, and will skip documents associated with the skipped lines.

If you would like to fix the errors in your load file, select Download errors to download a .ZIP containing three items: 1. A .DAT containing only the valid lines of your original load file, 2. A.DAT containing the lines that could not be parsed, and 3. 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 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.
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.

Return to table of contents

 

Multiple native files

    • Multiple native files, duplicate named xmultiple_native_files.png
    • 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, when both are .pdfs. To deal with this, you want to reorganize the files if necessary and then select “Rescan or change folders.”

Return to table of contents

Conflicts with a previous image

    • Image conflicts with a previous image for # pageconflicts_with_a_previous_image.png
    • 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.

Return to table of contents

Error modifying - document in flight

    • Error verifying modifications: “Not yet published by upload”not_yet_published.png
    • This error means that the document with the begin Bates on the left that you are trying to modify is not yet uploaded, but is still in progress. This can happen when an upload is in an error state. You will have to find the upload that the document was originally present in, complete it or remove the errored documents from the original, and then retry the upload documents stage.

Return to table of contents

Error unable to rewrite PDF

    • Error preparing "/ReplacementFiles/images/#812088.1.pdf": Unable to rewrite pdferror_rewriting.jpg
    • This generally means the file is corrupt (i.e. doesn’t conform to the PDF spec).

Return to table of contents

Error timeout rewriting PDF

  • Error preparing "/ENRON000001/pdfs/ENRON001.pdf": Timeout rewriting pdftimeoutrewritingpdf2.png
  • This means the file took too long to fix in a reasonable time. This can sometimes be fixed offline.

Return to table of contents

“No image reader” error

  • Error preparing “/images/0143/ENRON2341273.tif": No image reader for /mnt/uploads/1098/30907/02/8156/0235/1.tifimage_reader_error_REDACTED.jpg
  • 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.

Return to table of contents

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.

Return to table of contents

Have more questions? Submit a request

0 Comments

Article is closed for comments.