SUBMISSION INTEGRATION: ERROR CODES
This page provides a detailed reference for error codes encountered during submission integration in ScholarOne Manuscripts. Each error code includes its description and troubleshooting steps.
| Error Code | Description |
|---|---|
| -1 | Unknown Error: An unexpected error has occurred. Contact ScholarOne support for assistance. |
| 0 | Ingestion Successful: The submission was ingested successfully. No errors were encountered. |
| 1 | Unable to Read Archive File: The system was unable to open or process the archive file provided for submission. This error may occur due to issues such as a password-protected ZIP file, a virus within the file, or a corrupted file. Verify the ZIP file for any issues and resubmit. |
| 2 | Missing Client Key: The GO file is missing the client key. Verify the GO file contains the client key. |
| 3 | Missing Previous External ID (Revision): The GO file indicates a revision submission but does not include the external ID of the manuscript in the prev-id field. Check the GO file and include the correct prev-id. |
| 4 | Missing Previous External ID (Resubmission): The GO file indicates a resubmission but does not include the external ID of the manuscript in the prev-id field. Check the GO file and include the correct prev-id. |
| 5 | Invalid Previous ID (Original Submission): The GO file includes a prev-id for an original submission. Remove the prev-id from the GO file. |
| 6 | AWS Error: This error typically occurs when the GO file references an archive file that was not sent or does not match the name indicated in the GO file. Verify the archive file name and the name referenced in the GO file. This error can also indicate an S3 issue. If the file names are correct, contact ScholarOne support. |
| 7 | Unable to Parse GO File: The GO file contains syntax errors or does not validate against the specified DTD. Check the GO file for correct syntax and DTD compliance. |
| 8 | Client Key Mismatch: The client key in the GO file does not match the client key assigned to you or the S3 bucket prefix where the deposit was placed. Ensure the GO file contains the correct client key and that the deposit is in the correct bucket path. |
| 9 | Journal Mismatch: The journal specified in the GO file does not match the client key. Verify that the GO file contains the correct journal name and client key pair. |
| 10 | Journal in Maintenance Mode: The journal you are depositing to is currently in maintenance mode. Contact your business team or ScholarOne support. |
| 11 | X-Path Error: An X-Path error occurred while reading the GO file. Check the GO file for completeness and ensure all required information is present. |
| 12 | Unable to Locate JATS File: The JATS file referenced in the GO file is not found in the archive. Verify that the GO file correctly references the JATS file and that the JATS file is included in the archive. |
| 13 | Unable to Parse JATS File: The JATS file is not a properly formatted XML document. Check the JATS file for XML formatting errors. |
| 14 | No Authors Found: No authors were present in the JATS file, or the author data could not be extracted. Verify the JATS file contains author information. |
| 15 | Can't create revision/resubmission - Previous ID Missing in JATS File: The previous ID is required in the JATS file for revisions or resubmissions. Include the previous ID in the JATS file. |
| 16 | Can't create revision/resubmission - Unable to Locate Previous Manuscript: The system could not locate the previous submission using the provided previous ID. Verify the previous ID is correct. |
| 17 | Can't create revision/resubmission - Previous Document Not Decisioned: The previous submission does not have a decision. Ensure the correct previous ID is provided and that the previous manuscript's status is appropriate. |
| 18 | Can't create revision/resubmission - Revision/Resubmission Already Exists: A revision or resubmission is already in process for this submission. Only one revision or resubmission can be in process at a time. |
| 19 | Can't create revision/resubmission - Revision/Resubmission Option Expired: The time limit for starting a revision or resubmission has expired. This is a configurable setting. |
| 20 | File List Mismatch: The file list in the GO file does not match the file list in the JATS file. This is based on a simple comparison of the list sizes. Check both files for discrepancies in the file lists. |
| 21 | File Missing from JATS File List: A file declared in the GO file is not present in the JATS file list. Compare the file entries in both files. |
| 22 | Unable to Extract/Copy File: The system was unable to extract or copy a file from the archive for processing. Contact ScholarOne support for assistance. |
| 23 | Invalid Email for Person: The email addresses provided for authors in the JATS file are not in a valid format. Verify the email addresses in the JATS file. |
| 24 | Missing First Name: A new person record is missing the first name. Ensure all author records in the JATS file include a first name. |
| 25 | Missing Last Name: A new person record is missing the last name. Ensure all author records in the JATS file include a last name. |
| 26 | No Author Role Present: The journal does not have an author role configured. Contact your business team or ScholarOne support. |
| 27 | Person Does Not Have Author Role: Existing authors must have had the author role prior to the submission. Verify the user's profile in ScholarOne to ensure they are assigned the author role. |
| 28 | External ID Already Used: The provided external ID already exists in the system. Ensure the external ID is unique. |
| 29 | External ID is Missing: The JATS file does not contain an external ID. Include an external ID in the JATS file. |
| 30 | Duplicate Email Address: An author on the submission has a duplicate account using the same email address. Contact your business team or ScholarOne support to resolve the duplicate account. |
| 31 | First Name Mismatch (To Be Retired): The first name provided does not match the name on record for the given email address. Verify the author's first name in the JATS file. |
| 32 | Last Name Mismatch (To Be Retired): The last name provided does not match the name on record for the given email address. Verify the author's last name in the JATS file. |
| 33 | Username Already in Use: The email address used for a new user account is already associated with an existing username. Contact your business team or ScholarOne support. |
| 34 | File Missing in Archive: The GO file indicates a file that is not present in the archive. Ensure all files referenced in the GO file are included in the archive. |
| 35 | Empty File Name in GO File: A file name provided in the GO file is empty. Check the GO file for empty file names. |
| 36 | First Name Too Long: The author's first name exceeds the maximum allowed length of 40 characters (double-byte characters count as 2). Check the length of the first name in the JATS file. |
| 37 | Last Name Too Long: The author's last name exceeds the maximum allowed length of 60 characters (double-byte characters count as 2). Check the length of the last name in the JATS file. |
| 38 | Middle Name Too Long: The author's middle name exceeds the maximum allowed length of 40 characters (double-byte characters count as 2). Check the length of the middle name in the JATS file. |
| 39 | Invalid document_replaces Value: The value provided for document_replaces in the GO file is non-numeric, missing, or unparseable. This field should contain the ScholarOne system's internal document ID for replacement packages. Check the GO file for the correct value. |
| 40 | document_replaces Document Does Not Exist: The document ID provided in the document-replaces doc-id field cannot be found in the system. Verify the document ID with the ScholarOne system. If the issue persists, contact ScholarOne support. |
| 41 | document_version Mismatch: Provided document_version does not match document external Id. The document-replaces doc-id allows the system to locate a document, but its external ID does not match the value provided in the prev-id field. Verify the values in these fields. If the issue persists, contact ScholarOne support. |
| 42 | Missing GO File Version: The GO file is missing the version information. The document-version version="xxx" element is either missing or cannot be parsed. Add the version information to the GO file. |
| 43 | Invalid File Type in Original Version: The original submission contains a "response to decision letter" type file, which is not allowed. Verify the file entries in the JATS file. |
| 44 | Document Unlocked: The GO file attempts to replace a document that is not currently locked. Locate the document in the ScholarOne user interface to determine its unlocked status. If the document was returned to draft before the unsubmit workflow was activated, it must be manually locked before a replacement document can be submitted. |
| 45 | Submitting Author Mismatch: The JATS file must use the same submitting author as the original file being replaced. Updating or changing the submitting author is not permitted. Verify the author ordering, email addresses, and author-related flags are consistent. Authors can be added or removed, but the submitting author must remain the same. |
| 46 | External ID Too Long: The external ID exceeds the maximum allowed length of 256 characters. Ensure the external ID is within the length limit. |
| 47 | Author Email Too Long: The author's email address exceeds the maximum allowed length of 128 characters. |
| 48 | File Name Max Length Exceeded: The file name exceeds the maximum allowed length of 256 characters. |
| 49 | Document Not Ingested/Unsubmitted/Lock Editing Unchecked: This error may occur if the feature is not activated, the document in the GO file is no longer in draft, or other conditions. Verify the values in the GO file and contact ScholarOne support if the issue persists. |
| 50 | No Submitting Author Found: A submitting author could not be located in the JATS file. Verify the author section in the JATS file. If the issue persists, contact ScholarOne support. |
| 51 | Replacement Failed: Replacement document is not a revision or resubmission: The provided document cannot be ingested as a replacement because it is not identified as a revision or resubmission. Only documents explicitly marked as revisions or resubmissions can be processed for replacement. |
| 52 | Unable to Read Document XML: This may be due to incorrect formatting, corruption, or an unsupported encoding in the XML file. Ensure the XML is properly formatted and valid before ingestion. |
| 53 | File Already Exists: The file being submitted has the same name as an existing file in the system. Duplicate file names are not allowed. To resolve this issue, rename the file before submission or check if the file has already been uploaded. |
| 54 | Previous Document Not Accepted: The system requires an accepted previous document for this operation, but the referenced document has not been accepted. Ensure that the prior document has been successfully processed before submitting this one. |
| 55 | Document External ID Does Not Match XML External ID: The external ID provided in the document metadata does not match the external ID specified in the XML. This discrepancy prevents proper document identification and processing. Verify that both IDs are correctly aligned before ingestion. |
| 56 | Provided XML contains duplicate External PDF Proof files: The provided XML contains more than one entry for an External PDF Proof file. Duplicate proof files are not allowed in the submission. Remove any duplicate references before resubmitting. |
| 57 | Provided XML has invalid file format for External PDF Proof files: The XML references an External PDF Proof file with an unsupported or incorrect format. Ensure that the file is in the required format before ingestion. |
| 58 | Provided Document is Not Invited: The submission references a document that has not been invited for submission. Ensure that the manuscript (stub) has been properly created before attempting to ingest it. |
| 59 | Provided Add-External-ID is Not Numeric: The document ID provided as the doc-id attribute must be a numeric value. Non-numeric values are not accepted. Update the document ID to a valid numeric format and retry the submission. |
| 60 | Go File Missing New External ID: The go.xml file does not contain the required new-external-id field. This field is necessary for tracking and processing the document. Ensure the external ID is included before submission. |
| 61 | External ID Already Assigned: The document has already been assigned an external ID, and a duplicate assignment is not allowed. |
| 62 | Site Not Configured for Document Locking: The submission cannot proceed because document locking is not enabled for this site. Contact the ScholarOne support to enable this feature if required. |
| 63 | Site Not Configured for Invited Document Locking: The document locking for invited submissions is not enabled on this site. Contact the ScholarOne support to enable this feature if required. |
| 64 | Site Not Configured for Final Files and First Look Document Locking: The site is not set up to handle document locking for final files and first look ingestions. Contact the ScholarOne support to enable this feature if required. |
| 65 | Both a submitting agent and submitting author were listed: An author cannot be designated as both the corresponding author and the submitting agent. Update the submission to assign only one of these roles to the author. |
| 66 | Submitting agent is not configured on this journal: Verify that the submitting agent role is correctly configured on the site before attempting to ingest. |
| 67 | Multiple Submitting Agents Found: More than one submitting agent has been listed in the submission, but only one submitting agent is allowed. Remove any additional submitting agents before resubmitting. |
| 68 | Multiple Submitting Authors Found: The submission contains more than one submitting author, which is not allowed. Ensure that only a single submitting author is listed before proceeding. |
| 69 | Both Submitting Agent and Submitting Author Listed: The submission includes both a submitting agent and a submitting author, which is not permitted. Only one of these roles should be assigned. Update the submission accordingly. |
| 70 | Audit Trail Entries Exceed Maximum Limit: The number of audit trail entries has exceeded the system’s maximum limit of 20. Reduce the number of audit trail entries and resubmit. |
| 71 | Only One File Attachment Allowed per Audit Trail Email: The submission includes multiple file attachments in an audit trail email, but only one attachment is allowed. Remove extra attachments before resubmitting. |
| 72 | Duplicate Authors Found: The submission contains duplicate author entries. Each author should be listed only once. Review and remove duplicate author entries before submission. |
| 73 | Unsupported Encoding Used in Archive File: The archive file contains special characters in file names but does not use UTF-8 encoding. Ensure that file names within the zip archive are encoded in UTF-8 before submitting. |
| 74 | File Designation Not Configured as an "Image": Update the designation settings before submitting. |
| 75 | Replacement Ingestion Not Allowed for Accepted Manuscripts: An attempt was made to replace an already accepted manuscript, which is not permitted. Once a manuscript is accepted, it cannot be replaced. |
| 76 | Person ID Not Found and No Valid Email Provided: The system could not locate the specified person ID, and no valid email address was provided as an alternative. Ensure that either a valid person ID or a valid email address is included. |
| 77 | Person ID Not Found: The provided person ID does not match any records in the system. Verify the person ID before resubmitting. |
| 78 | Submitting Agent can not be added/changed on the First Look/Final Files ingestion: The submitting agent cannot be changed or added during the ingestion process for First Look or Final Files. If a change is required, it must be handled outside the ingestion process. |
| 79 | Unsupported ingestion type to attempt submit: The attempted submission type is not supported. Check the documentation for allowed ingestion types and adjust the submission accordingly. |
| 80 | Unsupported Submission with Payment Enabled: The system does not support this type of submission while payment processing is enabled. |
| 81 | Unsupported attempt submission with CCC/Rightslink require view payment estimate turned on. |
| 82 | Too Many Author Departments Listed: The number of author departments listed in the submission exceeds the allowed limit. Reduce the number of departments before resubmitting. |
| 83 | CRediT Information Required for Author: The submission is missing required CRediT information for an author. |
| 84 | Previous Document Not in First Look Status: The referenced previous document must be in "First Look" status, but it is not. Update the document status or select a valid document before proceeding. |
| 85 | Document version in go file does not match meta flag. |
| 86 | Document Person Info Incomplete: The document submission contains incomplete person-related information. Ensure that all required author and contributor details are fully provided before resubmitting. |
| 87 | Document Person Info Invalid Email Address: The email address associated with a person in the document submission is invalid. Verify and correct the email address before proceeding. |
| 88 | Document Person Info Duplicate Primary Email Address: The system detected multiple instances of the same primary email address assigned to different persons. Ensure that each person has a unique primary email before submission. |
| 89 | Document File Has Restricted Extension: The submitted file has a restricted file extension. Check the site configuration for allowed file extension types. |
| 90 | Document file has restricted file designation extension. |
| 91 | Attribute is Not Configured. |
Updated 5 months ago
What’s Next
