The following table lists errors you might encounter during initial testing and development, or during production. These errors are reported in the statusCode and statusDescription fields of the JSON output. Your programming code can test for the statusCode value, but it should not depend on the statusDescription value, which sometimes changes between Toolkit
|
Error |
Description |
Likely cause |
Likely resolution |
||
|
3 |
Incorrect command line |
Typing error, missing argument, or unexpected word. |
Re-run the command manually to see the error messages. This will provide more information than the JSON output. To see correct usage, run identify -?, identifyStream -?, or analyze -? where applicable. |
||
|
6 |
File input or output error |
You do not have permission to read the file specified by -i or -c, or you do not have permission to write the file specified by -o. |
Check the permissions on the input files (specified by -c and -i), and on the parent directory of the desired output file (specified by -o). Change the permissions as needed. |
||
|
10 |
No sound data in file |
The input is a video file containing no audio, and the configuration file specifies audio fingerprints but not video fingerprints. |
Skip these files, or sign up for a video ID service from AM. To confirm this is the cause, run the program ffprobe in the Toolkit’s bin directory: ffprobe -i <file name>. Look for lines near the end containing Stream # and see if any say audio. |
||
|
42 |
No video available |
The input is an audio file, and the configuration file specifies video fingerprints, but not audio fingerprints. |
Skip these files, or sign up for an audio ID service from Audible Magic. To confirm this is the cause, run the program ffprobe in the Toolkit’s bin directory: ffprobe -i <file name>. Look for lines near the end containing Stream # and see if any say video. |
||
|
48 |
Didn't find FFMPEG command-line program |
Incorrect installation. |
Check that the directory containing identify also contains the ffmpeg executable file. |
||
|
49 |
File not found |
An input file does not exist (either the configuration file specified by -c, or the media file or analysis file specified by -i). |
Ensure the arguments to -c and -i refer to existing files. If you run the identify command manually, an error is written to the console. If it mentions MFMediaID_CreateUsingConfigFile, the problem is with -c, and if it mentions MFMediaID_IdentifyFile, the problem is with -i. |
||
|
71 |
Not a media file |
The file specified by -i is not a valid media file. |
Skip this input file. To confirm this is the cause, run the program ffprobe in the Toolkit’s bin directory: ffprobe -i <file name>. |
||
|
2045 |
ID server response timeout |
AM took too long to respond to the request. |
Retry your transaction after a couple of seconds. If it’s a recurrent problem, contact AM Client Services. |
||
|
3000-3999 |
libcurl error (some specific cases follow below) |
Various problems when attempting to make a request. |
Subtract 3000 from the number and look up the resulting code at: https://curl.haxx.se/libcurl/c/libcurl-errors.html |
||
|
3007 |
Failed to connect to host or proxy |
Problem with the local network. |
Ensure the machine has Internet access. Ensure any proxy is correctly configured |
||
|
3028 |
Operation timeout |
Problem with the local network, or an overloaded local device. |
Ensure the machine is functioning normally when accessing the Internet. |
||
|
3056 |
Failure with receiving network data |
A network problem at AM. |
Retry your transaction after a couple of seconds. If it’s a recurrent problem, contact AM Client Services. |
||
|
5000-5999 |
HTTP error (two specific cases follow below) |
Various problems when attempting to make a request. |
Subtract 5000 from the number and look up the resulting code at: https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html |
||
|
5413 |
HTTP status code 413 |
The configuration file specifies fingerprinting the entire media file, but the media file’s duration is too long for the service you are using. |
Contact AM Client Services regarding the best way to handle long media files. |
||
|
5429 |
HTTP status code 429 |
Too many requests. |
See Retries and Timeouts below, for more information. |
||
|
20108 |
Incompatible version of configuration file |
The configuration file is for a different version of the Toolkit. |
Use a configuration file that was supplied with this release of the Toolkit, or vice versa. Check the Toolkit’s version number by running identify -? and looking for library version. |
||
|
20259 |
Didn't find FFPROBE command-line program |
Incorrect installation. |
Check that the directory containing identify also contains the ffprobe executable file. |
||
|
20266 |
ffprobe generated a zero-length output file |
The file specified by -i is not a valid media file. |
Skip this input file. To confirm this is the cause, run the program ffprobe in the Toolkit’s bin directory: ffprobe -i <file name>. |
||
|
20300 |
Couldn't dynamically load the cURL library |
Incorrect installation or different Linux version. |
Check that the directory containing identify contains the curl library (exact name differs according to OS). If so, on Linux do an "ldd" on the curl library file and see if any output line says "not found"; then download and install the mentioned library, or contact Audible Magic Client Services. |
||
|
20301 |
Couldn't dynamically load the SSL library |
Incorrect installation or different Linux version. |
Check that the directory containing identify contains the ssl library (exact name differs according to OS). If so, on Linux do an "ldd" on the curl library file and see if any output line says "not found"; then download and install the mentioned library, or contact Audible Magic Client Services. |
||
|
20403 |
Media file is too short |
The media file’s duration is too short to make an identification using the AM service you are attempting to use. |
Skip this input file. Use files that have a longer duration, or sign up for a different identification service from AM. The minimum duration depends on the configuration file and varies depending on the kind of service. Check the file’s duration by running the program ffprobe in the Toolkit’s bin directory: ffprobe -i <file name>. |
||
|
20431 |
No unknown asset identifier specified |
You omitted the -e option when running identify. |
Add -e <unique identifier> to your command line. The argument should be a string that uniquely identifies the input media in your company’s systems. |
||
|
20453 |
Couldn't decode audio in the media file |
The file specified by -i is a media file, but there was a problem decoding its audio data. |
Please report the error to AM Client Services. Skip this input file until there is a resolution. |
||
|
20454 |
Couldn't decode video in the media file |
The file specified by -i is a media file, but there was a problem decoding its video data. |
Please report the error to AM Client Services. Skip this input file until there is a resolution. |
||
|
20467 |
Empty response from server |
Transient glitch at Audible Magic. |
Retry the identification. If the issue persists, contact Audible Magic Client Services. |
||
|
20468 |
Couldn't write userGuid file |
No write permission on the directory containing identify. |
Check that the current directory (the directory containing identify) is writable. |
||
|
20531 |
Missing tsmm directory |
Incorrect installation. |
Check that the directory containing identify contains a directory named "tsmm". If not, reinstall the Toolkit. (This applies only to certain Toolkit releases.) |
||
|
20544 |
Couldn’t create log file |
The log file could not be created due to common file system IO issues such as no more disk space or inadequate permissions. |
Check to make sure that you have not run out of disk space. Make sure that you have write permissions for the location where you asked identifyStream to write its output files. |
||
|
Any others |
Contact helpdesk@audiblemagic.com if the error is not self-evident. |
||||