In some cases, such as for HTTP response codes in the 400 and 500 range, you will need to analyze in more detail why a job request failed.
This response code indicates that the XML document was not well formed or did not comply with the job request XML schema (XSD). The HTTP Response body contains details of which part of the XML document caused the problem. There was no job created, so no diagnostic information is available in the Web User Interface.
In the HTTP Response body, look for the <message> element in the <error> element. For example:
<error>
<message>
Error with job validation: Problem with Reference Video: frame rate must be
provided for H.264 Annex B files.
</message>
<created>2011-08-13T17:39:19.440-04:00</created>
</error>
This response code indicates that the job queue is full. The size of the job queue is set by a system parameter in the Web User Interface.
In the Response body, look for the <message> element in the <error> element. For example:
<error>
<message>
Maximum Job Queue Error: The maximum number of jobs have been queued.
Current limit is set to 500.
</message>
<created>2011-08-10T14:17:04.199-04:00</created>
</error>
This response code indicates that the license is invalid.
In the HTTP Response body, look for the <message> element in the <error> element. Examples:
<error>
<message>
License Error License Failure: The license is invalid.
</message>
<created>2011-07-27T17:27:14.543-04:00</created>
</error>
<error>
<message>
Problem with license. The license expired.
</message>
<created>2011-08-10T10:04:44.510-04:00</created>
</error>
<error>
<message>
Problem with license. Invalid node information detected.
</message>
<created>2011-08-10T16:27:40.141-04:00</created>
</error>