Error Messages: Reasons and Solutions

The Semantic Extraction from virtually any binary document or web resources, coupled with OCR functionality, is a very complex process. Consequently, the process can sometimes fail for several reasons.

Most of the problems stem from broken or password encrypted documents, inaccessible URLs, or misuse of the service (interface contract violation).

Here’s a detailed list of the most common error messages, their reason of occurrence and possible solutions.

Username or password not provided

Reason: Either username or password have not been provided

Solution: Provide the correct user credentials you've received from JoinVision for accessing the web service (respect case-sensitivity!)

Username not found

Reason: The provided username is not valid

Solution: Provide the correct user credentials you've received from JoinVision for accessing the web service (respect case-sensitivity!)

Invalid Username/Password

Reason: The username or product token that was provided is not valid

Solution: Provide the correct user credentials you've received from JoinVision for accessing the web service (respect case-sensitivity!)

Invalid Auth Token

Reason: The product token that was provided is not valid

Solution: Provide the correct credentials you've received from JoinVision for accessing the web service (respect case-sensitivity!)

Product locked

Reason: The product you are trying to access is locked

Solution: Please contact the JoinVision Sales Team

Product expired

Reason: The product you are trying to access expired

Solution: Please contact the JoinVision Sales Team

Authentication via Password not supported

Reason: The authentication method you are using is no longer supported.

Solution: Please authenticate with your product token instead of your password!

Account locked

Reason: Your account has been locked

Solution: Please contact the JoinVision Sales Team

One or more parameters are not provided

Reason: The method contract has been violated

Solution: Provide values for all method parameters

No enum constant com.jv.iex.models.Model.XXXX

Reason: The provided extraction model String is invalid

Solution: Provide a valid extraction model identifier

File length too short

Reason: The size of the provided input file is too short for being a valid (binary) input file for semantic extraction

Solution: Provide a valid (binary) file for extraction

Too many requests are currently processed by this user (queue length exceeded)

Reason: You've started too many requests to the web service at the same time. The maximum amount of parallel requests is currently limited to 10 calls, whereas not more than 2 calls can be processed at the same time. The remaining calls will be queued.

Solution: Reduce the amount of parallel requests to our service to a maximum of 10. Please note that multiple extraction requests will not speed up the extraction process, as only 2 requests will be processed simultaneously. If more parallel connections are required, please get in touch with us

Too many concurrent connections from same IP: XX

Reason: You've started too many request to the web service at the same time from the same IP address. The maximum amount of parallel requests is limited to 10.

Solution: Reduce the amount of parallel requests to our service to a maximum of 10.

Input Data/File is locked because it’s currently processed or has caused errors within the last XX hours and is therefore rejected

Reason a: The file or URL provided for processing has caused an error within the last XX hours (dynamic value)

Solution a: Do not re-issue a request shortly after it has failed for the first time - in virtually all cases the result will not be different. Retry failed URLs after some period of time in order to check if the remote resource has changed or is now available

Reason b: The file or URL provided for processing is already being processed by another request (because you have sent a request twice, for example)

Solution b: Do not send the same request/document more than once at the same time

Could not filter job offer from URL

Here is a list of the most common errors that can occur if remote pages are crawled. This list is not exhaustive, as it depends on the remote host which errors are thrown.

HTTP request failed: HTTP/1.1 401 Unauthorized

Reason: The URL passed for semantic analysis is not accessible without authorization

Solution: Provide a URL pointing to a resource which is accessible without prior authorization

HTTP request failed: HTTP/1.1 403 Forbidden

Reason: The URL references a resource where access is not permitted

Solution: Provide a URL pointing to a resource which is accessible via a generic HTTP GET request

HTTP request failed: HTTP/1.1 404 Not Found

Reason: The URL references a resource that is not available (any more) at the time of fetching

Solution: Validate the URL and/or provide a URL pointing to an existing resource

HTTP request failed: HTTP/1.1 500 Internal Server Error

Reason: The server cannot process a generic HTTP GET request to the provided URL

Solution: Validate the URL and/or get in touch with the operator of the remote server

HTTP request failed: HTTP/1.1 503 Service Unavailable

Reason: The URL references a server that is not available at the time of extraction

Solution: Retry to process the URL at a later point in time (at least 60 minutes later) and/or get in touch with the service operator of the remote server

Illegal Character in fragment at index XX

Reason: The URL contains invalid characters

Solution: Provide a valid URL following the specification

Could not crawl XXXX Code: 0 - Host name may not be null

Reason: The URL does not contain a valid host name

Solution: Provide a valid, complete URL (including the protocol identifier:

Could not crawl XXXX Code: 0 - Socket closed / Connection reset / Unknown host / Connection refused / Socket timeout

Reason: Either the service could not connect to the host/port defined in the URL, or the network connection was aborted / timed out during data transfer

Solution: Retry the request at a later point in time. If it still fails, get in touch with the operator of the remote server.

Length of fetched data is 0

Reason: The document provided by the server has zero content

Solution: Provide a URL pointing to a valid resource (HTML or binary) with some content

Page HTML sourcecode is too large

Reason: The HTML document provided by the server exceeds a maximum amount of bytes (usually >100KB)

Solution: Only process URLs which contain one single document rather than several documents (i.e. a list of job offers)

Could not cut out job offer from given URL

Reason: The URL references a resource that is not processable by our semantic extraction engine

Solution: If the URL points to an obviously valid job offer or CV, please report the URL to our support team in order to analyze the reason for the problem.

Cannot process/convert file

Reason: The provided file or the file referenced by a given URL is not processable by our semantic extraction engine. This may be due to the file being invalid or because the format is not supported.

Solution: Provide a supported, valid (not corrupted nor fragmented and complete) and accessible (not password protected) document

Received no reply document from conversion for document type XXX

Reason: The conversion engine of our service was unable to process the provided document

Solution: Provide a supported, valid (not corrupted nor fragmented and complete) and accessible (not password protected) document

Could not convert to intermediate format

Reason: The engine was not able to convert the provided document into a semantically processable format, usually because the document is invalid, corrupted or not supported

Solution: Provide a supported, valid (not corrupted nor fragmented and complete) and accessible (not password protected) document

Could not OCR-process PDF of size XXX

Reason: The provided document requires an OCR conversion (usually because it consists of or contains scanned images) and the OCR engine was not able to process the images

Solution: Provide a supported, valid (not corrupted nor fragmented and complete) and accessible (not password protected) document

Could not semantically process data

Reason: A serious error occurred during the semantic extraction of the provided document

Solution: Get in touch with JoinVision and provide the original file for analysis

End-of-File, expected line

Reason: The provided document is incomplete or fragmented (broken)

Solution: Provide a valid, complete document

File is too large for semantic processing

Reason: The provided document is too large for semantic processing, In virtually all cases it is no valid HR document (CV, attachment, or job)

Solution: Only provide valid, supported, single HR documents to the service (e.g. not a collection of CVs at once)

The document has no pages

Reason: The provided document is broken or password protected

Solution: Provide a valid (not corrupted nor fragmented and complete) and accessible (not password protected) document

Unparsable JSON format

Reason: The provided JSON file is broken or invalid

Solution: Provide a valid, supported and complete JSON document

Invalid HTML, missing body or HTML node

Reason: The HTML document (or HTML delivered by the URL) is invalid or incomplete

Solution: Provide a valid, complete HTML document including head and body statements respectively. Assure that the provided URL points to a valid HTML document

Amount of pages in documents to be classified exceeds limit: XX

Reason: The combined amount of pages of all valid documents in the application folder exceed the limit for semantic processing, which is 50 pages in total.

Solution: Ensure that only one application folder is processed during one query. The error usually occurs if two or more folders are processed in one query.

Amount of documents to be classified exceeds limit: XX

Reason: The application folder contains too many documents (XX is a dynamic value)

Solution: Ensure that only one application folder is processed during one query. The error usually occurs if two or more folders are processed in one query.

Size input file exceeds limit

Reason: At least one submitted document is too large (binary size) (default is 20MB)

Solution: Ensure that the document is a valid HR document and contains only one application. The error usually occurs if two or more candidate profiles are contained in one file.

CV could not be identified

Reason: No CV could be identified in the application folder provided for the Merger module, so no further processing is possible

Solution: Ensure that the provided application folder contains at least one valid CV