PCRS Error Codes

This section includes information on the PCRS error codes that you may encounter and their descriptions.

Error Codes

Description

 Action Required

Error Code: 401

Incorrect credentials provided by the user. 

{
     "authentication_exceptions" :
    [  [ "Authentication Failure: 1 errors, 0      successes:authenticationFailure.InvalidCredentialsException" ] ]
}

Enter correct credentials and run the API again.

Error Code: 401

Expired authentication token entered by user.

{
    "status": 401,
    "error": "Unauthorized",
    "message": "JWT expired"
}

Enter correct valid token from /auth API and call the API again.

Error Code: 401

Invalid token provided.
{
    "status": 401,
    "error": "Unauthorized",
    "message": "Not authenticated"
}

Enter correct valid token from /auth API and call the APIs again.

 

200 ok  

Compliance Policy does not exist
[
    {
        "policyId": "94473",
        "subscriptionId": "1981983",
        "hostIds": [],
        "error": "Error: Compliance Policy does not exist."
    }
]

Enter correct policy ID and run the API again.

 

400

Policy ID entered contains non-numeric characters.

[{"response":{"datetime":"2021-10-28T13:29:06Z","code":1905,"text":"parameter policy_ids has invalid value: 4199751a (Invalid value: 4199751a)"}}]

Enter only numeric value for policy IDs.

404

Invalid parameter for “evidenceRequired".

{
    "message": "Invalid input Parameter."
}

Enter integer value - 0 or 1 for the evidenceRequired request parameter.

404

Invalid input parameter for “compressionRequired”

{
    "message": "Invalid input Parameter."
}

Enter integer value - 0 or 1 for the compressionRequired request parameter.

Connection broken
(client error)

Output stream has no data in stream.

“Connection broken: InvalidChunkLength(got length b'', 0 bytes read)", InvalidChunkLength(got length b'', 0 bytes read)

Run the API again with all valid inputs and options.

Server side error

Client and server connection is broken due to connectivity loss then below error will get on server logs.

Run the API again with all valid inputs and options.

403

This error occurs in case of an SCA-only account.

403 Forbidden: [{"response":{"datetime":"2021-10-28T07:24:26Z","code":2012,"text":"User license is not authorized to run this API."}}]

Use a valid PC license.

 

You can find all our latest API Documentation at the Qualys Community at Qualys Documentation