Error codes and solutions for Intelligent Speech Interaction-Intelligent Speech Interaction(ISI)-阿里云帮助中心

This topic describes the error codes for Intelligent Speech Interaction and their solutions. You can use this document to look up error codes and troubleshoot issues.

What are the error codes for Intelligent Speech Interaction?

If an operation fails when you use a software development kit (SDK) or call an API, the response from the client or server returns an error. The error code in the response helps you quickly identify the problem. You can then modify your code or provide feedback to the end user to resolve the issue.

Error code classification		Error code format
Server-side error codes	Server-side error	8-digit error code, for example, 50000000
Server-side error codes	Server-side error caused by a client operation	8-digit error code, for example, 40020105
SDK error codes	Mobile SDKs (iOS SDK/Android SDK)	6-digit error code, for example, 140008 or 240070
SDK error codes	Java SDK, C++ SDK, Python SDK, C# SDK, Go SDK, Node.js, WeChat mini program, and more	8-digit error code, for example, 10000004

After you send a request, the response contains the following information:

status: The status code. This numeric code indicates the nature and cause of the response and helps you find the corresponding explanation and solution.
status_text: The status message. If the status code is an error code, this field provides the error details.
task_id: The unique ID of the request.

The following code provides an example:

...
status:    40020105
status_text:    Meta:APPKEY_NOT_EXIST:Appkey not exist!
task_id:    61aff**********************
...

Server-side error codes

General-purpose error codes

Status code	Status message	Cause	Solution
40000000	The default client error code. This code corresponds to multiple error messages.	Invalid parameters or call logic was used.	Compare your code with the sample code in the official documentation to test and verify it.
40000001	The token 'xxx' has expired. The token 'xxx' is invalid	Invalid parameters or call logic was used. This is a general-purpose client error code that usually indicates an incorrect token, such as an expired or invalid token.	Compare your code with the sample code in the official documentation to test and verify it.
40000002	Gateway:MESSAGE_INVALID:Can't process message in state'FAILED'!	The message is invalid or incorrect.	Compare your code with the sample code in the official documentation to test and verify it.
40000003	PARAMETER_INVALID Failed to decode url params	The parameters passed by the user are incorrect. This error is common for RESTful API calls.	Compare your code with the sample code in the official documentation to test and verify it.
40000005	Gateway:TOO_MANY_REQUESTS:Too many requests!	Too many concurrent requests.	If you are using the Free Edition, you can upgrade to a commercial version to increase the concurrency. If you are already using a commercial version, you can purchase a concurrency resource plan to increase your concurrency quota.
40000009	Invalid wav header!	The message header is invalid.	If you send a WAV audio file and set the `format` parameter to `wav`, check whether the WAV header of the audio file is correct. If the header is incorrect, the server may reject the request.
40000009	Too large wav header!	The WAV header of the transmitted audio is invalid.	You can send the audio stream in a format such as PCM or OPUS. If you use the WAV format, make sure that the WAV header of the audio file contains the correct data length.
40000010	Gateway:FREE_TRIAL_EXPIRED:The free trial has expired!	The trial period has ended, and the commercial version is not activated or your account has an overdue payment.	You can log on to the console to check the service activation status and your account balance.
40010001	Gateway:NAMESPACE_NOT_FOUND:RESTful url path illegal	The operation or parameter is not supported.	Check whether the parameters passed in the call are consistent with the requirements in the official documentation. You can compare them with the error message to identify and set the correct parameters. For example, if you are using a curl command to make a RESTful API request, check whether the URL you constructed is valid.
40010003	Gateway:DIRECTIVE_INVALID:[xxx]	A general-purpose client-side error code.	This error indicates that the client passed an incorrect parameter or instruction. Detailed error messages are available for different operations. You can refer to the corresponding documentation to set the parameters correctly.
40010004	Gateway:CLIENT_DISCONNECT:Client disconnected before task finished!	The client actively terminated the connection before the request was processed.	None. Alternatively, you can close the connection after the server responds.
40010005	Gateway:TASK_STATE_ERROR:Got stop directive while task is stopping!	The client sent a message instruction that is not currently supported.	Compare your code with the sample code in the official documentation to test and verify it.
40020105	Meta:APPKEY_NOT_EXIST:Appkey not exist!	A non-existent Appkey was used.	Confirm whether a non-existent Appkey was used. You can log on to the console and view the project configuration to find the Appkey.
40020106	Meta:APPKEY_UID_MISMATCH:Appkey and user mismatch!	The Appkey and token passed in the call were not created by the same Alibaba Cloud account UID. This causes a mismatch.	Check whether you are using resources from two different accounts. Do not use an Appkey from Account A with a token generated from Account B.
403	Forbidden	The token is invalid. For example, the token does not exist or has expired.	Set a valid token. Tokens have an expiration period. You must obtain a new token before the current one expires.
41000003	MetaInfo doesn't have end point info	Failed to retrieve the routing information for this Appkey.	Check whether you are using resources from two different accounts. Do not use an Appkey from Account A with a token generated from Account B.
41010101	UNSUPPORTED_SAMPLE_RATE	The sample rate is not supported.	Real-time speech recognition currently supports only audio with a sample rate of 8000 Hz or 16000 Hz.
41040201	Realtime:GET_CLIENT_DATA_TIMEOUT:Client data does not send continuously!	Failed to retrieve data from the client due to a timeout.	When you call real-time speech recognition, the client must send data at a real-time rate and close the connection promptly after the data is sent.
50000000	GRPC_ERROR:Grpc error!	An exception caused by factors such as machine load or network issues. This error usually occurs randomly.	You can retry the call to resolve the issue.
50000001	GRPC_ERROR:Grpc error!	An exception caused by factors such as machine load or network issues. This error usually occurs randomly.	You can retry the call to resolve the issue.
52010001	GRPC_ERROR:Grpc error!	An exception caused by factors such as machine load or network issues. This error usually occurs randomly.	You can retry the call to resolve the issue.

Real-time speech recognition error codes

Status code	Status message	Cause	Solution
40000004	Gateway:IDLE_TIMEOUT:Websocket session is idle for too long time	After a connection is established, the server returns this error message if no data is sent for more than 10 seconds.	After establishing a connection, maintain interaction with the server. For example, continuously send the audio stream. You can send the audio while it is being captured. Close the connection promptly after the audio is sent.
40010004	Gateway:CLIENT_DISCONNECT:Client disconnected before task finished!	The client actively terminated the connection before the request was processed.	None. Alternatively, close the connection after the server responds.
40270002	NO_VALID_AUDIO_ERROR	The audio is invalid.	No valid text was recognized from the audio.
40270003	DECODE_ERROR	Audio decoding failed.	Set the format parameter based on the actual audio format.
41000002	APPKEY_KEY_IS_NULL	The appkey was not set correctly.	Refer to the official documentation and sample code.

Short sentence recognition error codes

Status code	Status message	Cause	Solution
40000000	Gateway:CLIENT_ERROR:Empty audio data!	No audio data.	You can refer to the public cloud sample code and send audio data with the request.
40000004	Gateway:IDLE_TIMEOUT:Websocket session is idle for too long time	After a connection is established, the server returns this error message if no data is sent for more than 10 seconds.	After you establish a connection, you must maintain interaction with the server. For example, you can continuously send the audio stream while it is being captured. Close the connection promptly after the audio is sent.
40010002	Gateway:DIRECTIVE_NOT_SUPPORTED:Directive'SpeechRecognizer.EnhanceRecognition'isnotsupported!	A message instruction that is not supported by the server was sent.	Compare your code with the sample code in the official documentation to test and verify it.
40010003	Gateway:DIRECTIVE_INVALID:Too many items for ‘vocabulary'!(173)	Too many hotwords were set.	You can refer to the API documentation to set the parameters correctly.
40270002	NO_VALID_AUDIO_ERROR	The audio is invalid.	No valid text was recognized from the audio.
41010104	TOO_LONG_SPEECH	The duration of the sent audio exceeds the limit. This error occurs only with the short sentence recognition operation.	Short sentence recognition supports audio up to 60 seconds long. If the audio is longer than 60 seconds, you must call the real-time speech recognition operation.
41010105	SILENT_SPEECH	The data contains only silence or noise, so no valid speech can be detected.	None.

Audio file recognition/Audio file recognition (off-peak) error codes

Status code	Status message	Cause	Solution
21050000	SUCCESS	Success.	None.
21050001	RUNNING	The audio file recognition task is running.	Send a GET request to query the recognition result later.
21050002	QUEUEING	The audio file recognition task is in the queue.	Send a GET request to query the recognition result later.
21050003	SUCCESS_WITH_NO_VALID_FRAGMENT	The operation to query the recognition result was successful, but the voice activity detection (VAD) module did not detect any valid speech.	In this case, check the following: Check whether the audio file contains valid speech. If it contains only invalid speech, such as pure silence, it is normal for no recognition result to be returned.
21050003	ASR_RESPONSE_HAVE_NO_WORDS	The operation to query the recognition result was successful, but the final recognition result is empty.	In this case, check the following: Check whether the audio file contains valid speech, or whether the valid speech consists only of filler words and the enable_disfluency parameter is enabled, causing the filler words to be filtered out. In these cases, it is normal for no recognition result to be returned.
41050001	USER_BIZDURATION_QUOTA_EXCEED	The daily duration limit is exceeded. Free Edition users can recognize audio files with a total duration of no more than 2 hours per day.	Upgrade from the Free Edition to the commercial version. If you have a high volume of business, contact our business team by email at nls_support@service.aliyun.com.
41050002	FILE_DOWNLOAD_FAILED	File download failed.	Check whether the audio file path is correct and whether the file can be accessed and downloaded from the internet.
41050003	FILE_CHECK_FAILED	The file format is incorrect.	Check whether the audio file is in single-channel or dual-channel WAV or MP3 format.
41050004	FILE_TOO_LARGE	The file is too large.	Check if the audio file size exceeds 512 MB. If it does, segment the audio file.
41050005	FILE_NORMALIZE_FAILED	File normalization failed.	Check whether the audio file is damaged and whether it can be played normally.
41050006	FILE_PARSE_FAILED	File parsing failed.	Check whether the audio file is damaged and whether it can be played normally.
41050007	MKV_PARSE_FAILED	MKV parsing failed.	Check whether the audio file is damaged and whether it can be played normally.
41050008	UNSUPPORTED_SAMPLE_RATE	The sample rate does not match.	Check whether the actual audio sample rate is consistent with the sample rate of the ASR model bound to the Appkey in the console, or set the automatic downsampling parameter enable_sample_rate_adaptive in this document to true.
41050010	FILE_TRANS_TASK_EXPIRED	The audio file recognition task has expired.	The TaskId does not exist or has expired.
41050011	REQUEST_INVALID_FILE_URL_VALUE	The file_link parameter in the request is invalid.	Confirm whether the format of the file_link parameter is correct.
41050012	REQUEST_INVALID_CALLBACK_VALUE	The callback_url parameter in the request is invalid.	Confirm whether the format of the callback_url parameter is correct and whether it is empty.
41050013	REQUEST_PARAMETER_INVALID	The request parameter is invalid.	Confirm that the task value in the request is a valid JSON format string.
41050014	REQUEST_EMPTY_APPKEY_VALUE	The appkey parameter value in the request is empty.	Confirm whether the appkey parameter value is set.
41050015	REQUEST_APPKEY_UNREGISTERED	The appkey in the request parameter is not registered.	Confirm whether the appkey parameter value in the request is set correctly, or whether it belongs to the same account as the AccessKey ID of the Alibaba Cloud account.
41050021	RAM_CHECK_FAILED	RAM check failed.	Check whether your RAM user is authorized to call the API operations of Voice Service. For more information, see Configure RAM user permissions.
41050023	CONTENT_LENGTH_CHECK_FAILED	content-length check failed.	When downloading a file, check whether the content-length in the HTTP response is consistent with the actual file size.
41050024	FILE_404_NOT_FOUND	The file to be downloaded does not exist.	Check whether the file to be downloaded exists.
41050025	FILE_403_FORBIDDEN	You do not have permission to download the required file.	Check whether you have permission to download the audio file.
41050026	FILE_SERVER_ERROR	The service where the requested file is located is unavailable.	Check whether the service where the requested file is located is available.
41050103	AUDIO_DURATION_TOO_LONG	The duration of the requested file exceeds 12 hours.	Segment the audio and submit multiple recognition tasks. For more information, see Segmentation command reference.
40270003	DECODER_ERROR	Failed to detect audio file information.	Confirm that the file at the download link is in a supported audio format.
51050000	INTERNAL_ERROR	An exception caused by factors such as machine load or network issues. This error usually occurs randomly.	Retry the call to resolve the issue. If the issue persists, contact technical support.

Flash audio file recognition error codes

Status code	Status message	Cause	Solution
40000004	Gateway:IDLE_TIMEOUT:Websocket session is idle for too long time	After a task is submitted, the server returns this error message if no task result is returned for more than 50 seconds.	If a task returns this error code, retry submitting it. We recommend retrying a maximum of two times.
40000005	-	Too many requests.	Check whether the number of concurrent connections or requests per second has been exceeded.
40270001	-	The audio format is not supported.	The requested audio format is not in the supported list.
40270002	NO_VALID_AUDIO_ERROR	The audio is invalid.	No valid text was recognized from the audio.
40270003	-	Audio decoding error.	An error occurred while decoding the audio according to the requested format.
40270004	-	No valid audio stream.	No valid audio stream was extracted from the multi-channel audio.
40270006	-	File download failed.	Check whether the file link is valid.

Speech synthesis/Long-text speech synthesis error codes

Status code	Status message	Cause	Solution
40000001	Gateway:ACCESS_DENIED:No privilege to this voice!	An incorrect speaker name was set.	You can refer to the official documentation to set the correct speaker.
40000004	Gateway:IDLE_TIMEOUT:Websocket session is idle for too long time,the last directive is 'StartSynthesis'!	After a connection is established, the server returns this error message if no data is sent for more than 10 seconds.	Close the connection promptly after the request is processed. This error may also occur if the server is under high instantaneous pressure and cannot return data in time. In this case, you can retry the request to resolve the issue.
40010003	Gateway:DIRECTIVE_INVALID:No text specified!	No valid text for synthesis was set.	You can refer to the sample code in the official documentation to set the text for synthesis.
41020001	Speech synthesis client error	Multiple error messages may be returned. Adjust your code based on the specific error message.	If the message `Engine return error code: 424.` is returned, the background music or concatenated recording does not conform to the required format. You can set the correct background music as described in the documentation. If the message `Engine return error code:418` is returned, an unsupported speaker name was passed. If the message `Engine return error code: 413` is returned, the SSML format used is incorrect. If the message `Request json illegal,failed to parse request.` is returned, the passed JSON format is invalid. If the message `SSML text length should be less than 300.` is returned, the synthesis text is too long. You must use the long-text speech synthesis operation.
51020001	TTS:TtsServerError	An exception caused by factors such as machine load or network issues. This error usually occurs randomly.	You can retry the call to resolve the issue.

Speech synthesis/CosyVoice voice cloning service error codes

Status code	Status message	Cause and solution
40001000	QUOTA_ERROR	Check whether the service is activated.
40001001	VOICE_LIMIT_ERROR	The number of cloned voices exceeds the limit. The default limit is 1,000.
40001002	VOICE_PREFIX_ERROR	The voice name prefix does not meet the following rules: It cannot be empty. It can be up to 10 characters in length. It can contain only digits and letters.
40002000	AUDIO_URL_ERROR	The audio URL is invalid.
40002001	AUDIO_DOWNLOAD_FAIL	Failed to download the audio.
40002002	FILE_SIZE_EXCEED	The audio file exceeds 10 MB.
40002003	AUDIO_SAMPLE_RATE_ERROR	The audio sample rate is less than 16 kHz.
40002004	AUDIO_FORMAT_ERROR	The audio format is incorrect and decoding failed. The supported formats are `wav`, `mp3`, `m4a`, and `aac`.
40003000	SILENT_AUDIO_ERROR	There is not enough valid speech in the audio.
40003001	AUDIO_SNR_ERROR	The signal-to-noise ratio (SNR) of the audio is too low.
50000000	SERVER_ERROR	A service error occurred. Retrying the operation usually resolves the issue. When you use the CosyVoice voice cloning feature, this error usually occurs because the recording quality is poor. Follow the instructions in the Recording guide to re-record the audio and perform voice cloning. Make sure that the recorded audio has no noise, avoid frequent and unnecessary pauses, and ensure that there are at least 5 seconds of continuous sound.
-	ACCESS_DENIED : Permission denied!	Permission denied. During voice cloning, this error occurs if you use a RAM user that has not been granted the AliyunNLSFullAccess permission. For more information, see Manage RAM user permissions.

Mobile SDK error codes

Short sentence recognition/Real-time speech recognition/Flash audio file recognition

Configuration or parameter errors

Status code	Status message	Cause	Solution
240999	DEFAULT_ERROR	Internal default error.	Internal unspecified error.
240001	NUI_CONFIG_INVALID	Configuration file error.	Configuration file error. Confirm that the resource file exists in the specified resource path. For Android, refer to the code sample and use the copyAssets interface.
240002	ILLEGAL_PARAM	Invalid parameter.	Confirm that the passed format is correct, including field types and value range limits. For example, enable_voice_detection must be set to the boolean value true, not 1 or the string "true".
240003	ILLEGAL_INIT_PARAM	Invalid initialization parameter.	Confirm whether the initialization parameter format is incorrect or if a required field is missing.
240004	NECESSARY_PARAM_LACK	A required parameter is missing.	Confirm the required parameters for the operation call.
240005	NULL_PARAM_ERROR	The parameter is null.	Confirm whether the parameter is null.
240006	NULL_LISTENER_ERROR	The event callback is not defined.	Confirm that the callback event is correctly assigned.
240007	NULL_DIALOG_ERROR	No valid dialog instance. This usually occurs during an internal state error.	Confirm that the state is correct before calling the operation. You can use the cancel operation to restore the idle state.
240008	NULL_ENGINE_ERROR	No valid engine instance. Check whether initialization was successful.	Confirm whether initialization was successful.
240009	ILLEGAL_DATA	The passed audio data address or length is invalid.	Confirm the passed data length value.

SDK status errors

Status code	Status message	Cause	Solution
240010	ILLEGAL_REENTRANT	An SDK operation was called after exiting.	This can be ignored if it does not affect functionality.
240011	SDK_NOT_INIT	The SDK is not initialized correctly.	Confirm that the initialization returns a correct value before you call other operations.
240012	SDK_ALREADY_INIT	The SDK initialization operation was called repeatedly.	Confirm the initialization call logic.
240013	DIALOG_INVALID_STATE	Internal dialog state error.	Read the SDK flowchart to confirm whether the operation was called in an incorrect state.
240014	STATE_INVALID	SDK internal state error.	Read the SDK flowchart to confirm whether the operation was called in an incorrect state.
240015	ILLEGAL_FUNC_CALL	The operation cannot be called in this mode.	Confirm whether the operation call is reasonable.

System call errors

Status code	Status message	Cause	Solution
240020	MEM_ALLOC_ERROR	Memory allocation error.	Check for insufficient memory.
240021	FILE_ACCESS_FAIL	File access error.	Check whether read and write permissions are granted for the file.
240022	CREATE_DIR_ERROR	Error creating directory.	Check for write permissions.

SDK internal call errors

Status code	Status message	Cause	Solution
240030	CREATE_NUI_ERROR	Engine creation failed.	Failed to create the instance, usually due to insufficient system resources.
240031	TEXT_DIALOG_START_FAIL	Failed to initiate text understanding.	Text-to-semantic understanding failed. Check the network connection or whether information such as the URL and token is valid.
240032	TEXT_CANCEL_START_FAIL	Failed to cancel text understanding.	This can be ignored.
240033	WUW_DUPLICATE	Duplicate dynamic wake-up word.	This can be ignored.

Local engine call errors
Status code
Status message
Cause
Solution
240040
CEI_INIT_FAIL
Local engine initialization failed.
Confirm whether the local engine's model is valid and whether the directory is readable and writable.

Audio errors

Status code	Status message	Cause	Solution
240051	UPDATE_AUDIO_ERROR	Error pushing audio, usually because the input audio length is greater than the required audio length.	Confirm whether the length of the pushed audio is invalid.
240052	MIC_ERROR	Failed to get audio for 2 consecutive seconds.	Confirm whether audio of the required length is correctly provided in the audio data callback.

Network errors

Status code	Status message	Cause	Solution
240060	CREATE_DA_REQUEST_ERROR	Failed to create a dialog assistant instance.	This can be ignored.
240061	START_DA_REQUEST_ERROR	Failed to initiate a dialog assistant request.	This can be ignored.
240062	DEFAULT_NLS_ERROR	A server-side error occurred. Note This error also contains the content of the server-side response.	For more information, see Server-side error codes to further locate the issue.
240063	SSL_ERROR	Error creating SSL instance.	Ignore if it occurs randomly.
240064	SSL_CONNECT_FAILED	SSL connection failed.	Connection exception. Check whether the service URL or local network connection is normal.
240065	HTTP_CONNECT_FAILED	HTTP connection failed.	Service connection error. Check the log file for the HTTP return value to confirm the cause.
240066	DNS_FAILED	DNS resolution failed.	Check whether the local network and DNS service are normal.
240067	CONNECT_FAILED	Socket connection failed.	Check the network connection.
240068	SERVER_NOT_ACCESS	The server is inaccessible.	Check whether the token has expired or the URL is correct.
240069	SOCKET_CLOSED	The socket is closed.	Ignore if it occurs randomly.
240070	AUTH_FAILED	Authentication failed.	Check whether you have provided the correct ak_secret, ak_id, app_key, sdk_code, and device_id. Also, confirm that you have a sufficient quota.
240071	HTTPDNS_FAILED	Failed to connect using the IP address passed by the client.	If you are accessing by directly passing an IP address, confirm whether the IP address is accessible.
240072	HTTP_SEND_FAILED	HTTP send failed for file transcription.	Confirm that the network connection is normal.
240073	HTTP_RECEIVE_FAILED	HTTP receive failed for file transcription.	Confirm that the network connection is normal.
240074	HTTP_RESPONSE_ERROR	Failed to parse received content for file transcription.	The content returned by the server is incorrect.
240075	HTTP_SERVER_ERROR	File transcription service error.	For more information, see Server-side error codes to further locate the issue.

Speech synthesis/Offline speech synthesis

SDK-related

Status code	Status message	Cause	Solution
140000	TTS_CREATE_FAILED	Engine initialization failed.	The resource path is incorrect or a resource file is abnormal. This fault is often accompanied by the error code TTS_ASSETPATH_INVALID. Review the log to confirm. Ensure the provided resource path is valid and all resource files are complete.
140001	TTS_ENGINE_INVALID	The engine is not initialized.	The current TTS instance is not created. Check if the initialization API has been called.
140002	TTS_TEXT_ERROR	The text is invalid, for example, empty.	Check the SDK log to confirm that the file is invalid. Ensure that the input text is valid.
140003	TTS_MALLOC_FAILED	Memory allocation failed.	Out of memory. Ensure enough memory is available.
140005	TTS_ASSETPATH_INVALID	The resource path is empty.	The resource path is incorrect or a resource file is abnormal. Check the logs to confirm the fault. Ensure the provided resource path is valid and all resource files are complete.
140006	TTS_HANLDE_INVALID	The processing thread does not exist.	You can release TTS and then retry.
140007	TTS_CREATE_HANLDE_FAILED	Failed to create the processing thread.	Check the error message in the log to identify the problem.
140008	TTS_AUTH_FAILED	Authentication failed. The SDK cannot be used.	Check that the akId, akSecret, and appkey are correct. Review the error message in the log for details. The issue may be that offline authentication is not enabled or that your quota is exhausted.
140011	TTS_OPERATE_INVALID	Invalid operation.	The current processing thread is in an invalid state. This can occur if a call, such as `pause`, is made before initialization. Ensure that calls are valid for the current state.
140012	TTS_OPEN_FILE_FAILED	Failed to open the file.	Failed to open the wav debug file or the log file. Check the error message in the log for details.
140013	TTS_STATE_INVALID	State machine verification failed.	The method call is invalid for the current state machine. This can occur if a method, such as `pause`, is called before initialization. Ensure that method calls are valid for the current state.
140014	TTS_SYNTHESIZER_INIT_ERROR	Synthesizer initialization failed.	Synthesizer creation failed, mainly due to out of memory.
140015	TTS_SYNTHESIZER_RELEASE_ERROR	Synthesizer release failed.	The synthesizer failed to release. Check the logs to pinpoint the cause.
140016	TTS_SYNTHESIZER_FAILED	Synthesis failed.	A state fault occurred during pre-playback. Check the logs to pinpoint the cause.
140017	TTS_WAIT_TIMEOUT	Timeout exit.	If a timeout occurs while waiting for a status, check the logs for details.
140018	TTS_CLOSED	The TTS part of the code was not compiled.	The current SDK does not include the TTS feature. Switch to the correct SDK.

Parameter configuration-related

Status code	Status message	Cause	Solution
140100	TTS_PARAM_INVALID	Invalid parameter.	An invalid input parameter was provided during initialization or when setting parameters. For example, the workspace, callback, taskId, or text is empty. Check the logs to locate the specific error.
140101	TTS_PARAM_VALUE_INVALID	Invalid parameter value.	Invalid input parameter. Check the logs to pinpoint the error.
140102	TTS_CFG_OPEN_FAILED	Failed to open the configuration file.	The resource path is incorrect or the resource file is abnormal. Check the log to confirm. Ensure the resource path is valid and all resource files are complete.

Audio processing

Status code	Status message	Cause	Solution
140200	TTS_AM_CREATE_FAILED	Player creation failed.	Creation of the SDK's internal audio manager failed.
140210	TTS_AM_OPEN_FAILED	Player open failed.	The SDK internal audio manager failed to open. Check the logs to pinpoint the issue.
140210	TTS_DECODER_INIT_FAILED	Audio decoder initialization failed.	The audio decoder, possibly an MP3 decoder, failed to initialize. Check the logs to pinpoint the cause.
140211	TTS_DECODER_MALLOC_FAILED	Audio decoder failed to allocate memory.	Out of memory. Ensure enough memory is available.
140212	TTS_DECODER_INPUT_TOO_MANY	Too much data was input at once and will be discarded.	Check the log to identify the specific issue. The maximum data size for a single input is 2000.
140213	TTS_DECODER_OUTPUT_TOO_MANY	Too much data was output, exceeding the cache, and will be lost.	Check the logs for detailed information.
140220	TTS_AP_INIT_FAILED	Audio processing unit (audioplayer) failed to open.	This error is typically returned with other AP ErrorCodes. Check the logs for more details.
140221	TTS_AP_START_FAILED	Error starting ap.	Check the logs to pinpoint the issue.
140222	TTS_AP_MALLOC_FAILED	Audioplayer failed to allocate memory.	Out of memory. Ensure there is enough memory to run.
140231	TTS_BGM_DECODE_INVALID	Decoder initialization failed.	Check the logs to confirm if the decoder is initialized.
140233	TTS_BGM_MALLOC_FAILED	Memory allocation failed.	Out of memory. Ensure there is enough memory to run.
140237	TTS_BGM_PARAM_INVALID	Background music parameter setting error.	Confirm the parameter settings are correct. Check the log to find the problem. Look for the bgm value:.

Cache-related

Status code	Status message	Cause	Solution
140300	TTS_CACHE_INIT_FAILED	Failed to initialize cache.	This error is often accompanied by the TTS_CACHE_PATH_INVALID error code. This may indicate an invalid storage path. Check the logs for details.
140302	TTS_CACHE_CMD_ERROR	The cache command is not standard.	Check the returned error message and log to pinpoint the fault.
140308	TTS_CACHE_PATH_INVALID	Failed to create the cache path.	Check the returned error message and log to locate the fault.
140309	TTS_CACHE_LIST_CREATE_FAILED	Failed to create the cache list.	Check the returned fault message and log for details.
140311	TTS_CACHE_TOO_MANY	Too much cache.	View the logs for details.
140312	TTS_CACHE_PARAM_INVALID	Parameter error.	Check the returned error message and log for details.
140313	TTS_CACHE_RECORDING_OPEN_FAILED	Error opening local file.	The file permissions or path might be incorrect. Check the logs for details.

Font delivery-related

Status code	Status message	Cause	Solution
140351	TTS_FONT_INITLIST_FAILED	Initialize the fontlist manager.	Out of memory. Ensure there is enough memory to run.
140352	TTS_FONT_INITLIST_INVALID	The fontlist manager is not initialized.	Out of memory. Ensure sufficient memory is available to run.
140353	TTS_FONT_CMD_INVALID	The command format is incorrect.	Check the returned fault messages and logs to identify the issue.
140354	TTS_FONT_RESPONSE_ERROR	The server returned an incorrect format.	Check the returned error messages and logs to pinpoint the issue.
140350	TTS_FONT_RESPONSELIST_ERROR	The fontlist request to the server returned an incorrect format.	Check the returned error message and log to locate the fault.
140356	TTS_FONT_GET_FONTLIST_FAILED	Failed to get the fontlist.	Check the returned error messages and logs to pinpoint the error.
140358	TTS_FONT_LOCALMSG_ERROR	Failed to parse the local list file.	You can check the returned error messages and logs to pinpoint the problem.
140359	TTS_FONT_LOCALFILE_ERROR	Failed to save the current list file.	Check the returned error messages and logs to pinpoint the problem.
140360	TTS_FONT_CLOUDMSG_ERROR	Failed to parse the cloud list.	Check the returned error messages and logs to locate the problem.

Local engine-related

Status code	Status message	Cause	Solution
140900	TTS_LOCAL_CRE_ENGINE_ERROR	Local engine initialization failed.	An internal error occurred in the local DPI engine. Check other error messages in the log to diagnose the fault.
140901	TTS_LOCAL_ENGINE_INVALID	The local engine is not initialized.	Check if TTS is initialized. Review the returned error messages and logs for details.
140902	TTS_LOCAL_ASSET_ERROR	Local resource verification failed.	The local engine failed to validate the resource path. Check the log for details.
140903	TTS_LOCAL_CRE_TASK_ERROR	Failed to create a local task.	You can check the logs to locate the specific issue.
140905	TTS_LOCAL_START_FAILED	Failed to start local synthesis.	View the logs to pinpoint the issue.
140906	TTS_LOCAL_OPERATION_FAILED	Local operation failed, for example, the local task does not exist or there is a default error.	View the logs to pinpoint details.
140907	TTS_LOCAL_SWITCH_FONT_FAILED	Failed to switch speaker.	Review the logs for details.
140908	TTS_LOCAL_GET_SAMPLERATE_FAILED	Failed to get the speaker's sample rate.	Check the logs to pinpoint the issue.
140909	TTS_LOCAL_ADD_FRONT_END_FAILED	Failed to add speaker.	Check the logs for details.
140910	TTS_LOCAL_VOICE_PATH_INVALID	The local speaker file does not exist or file authentication failed.	Check the logs to pinpoint the cause.
140911	TTS_LOCAL_VOICE_MISMATCH	Local speaker file mismatch.	Check the logs for details.

Cloud engine-related

Status code	Status message	Cause	Solution
141000	TTS_CLOUD_CREATE_FAILED	Cloud engine initialization failed.	View the logs for detailed information.
141004	TTS_CLOUD_START_FAILED	Cloud request failed.	This issue is typically caused by a network connection failure or invalid parameters for the Appkey, Token, or URL. Check the logs to pinpoint the exact cause.
141007	TTS_CLOUD_NETWORK_BROKEN	The network is poor.	If the network connection is poor, switch to a different network environment and try again.
141008	TTS_CLOUD_SSL_CONNECT_FAILED	SSL connection failed. Check whether the sent parameters are correct.	SSL connection failed. Check the send parameters. Review the logs for details.
141009	TTS_CLOUD_HTTP_CONNECT_FAILED	HTTP connection failed. Check whether the sent parameters are correct.	HTTP connection failed. Check the sent parameters. Review the logs for details.
141010	TTS_CLOUD_DNS_FAILED	Connection failed, DNS failed.	Connection failed. DNS failed. Check that the domain name resolution is correct. For more details, see the logs.
141011	TTS_CLOUD_URL_INVALID	The URL is invalid.	The URL is invalid. Ping the URL and port to confirm they are reachable. Check the logs for details to locate the issue.
141012	TTS_CLOUD_PROTOCOL_ERROR	Cloud protocol error.	Cloud protocol error. Check the logs for details.
141013	TTS_CLOUD_PARAMETERS_ERROR	Parameter error.	Cloud parameter error. Check the log for details.
141014	TTS_CLOUD_UNKNOWN_WS_HEAD_TYPE	WebSocket uses an unknown header type.	This is a known issue with older clients. Upgrade to the latest version.

Server-side status codes

Status code	Status message	Cause	Solution
144001	TTS_CLOUD_AUTH_FAILED	Identity authentication failed.	Check whether the token used is correct and whether it has expired.
144002	TTS_CLOUD_INVALID_MESSAGE	Invalid message.	Check whether the sent message meets the requirements.
144003	TTS_CLOUD_INVALID_TOKEN	The token has expired or the parameter is invalid.	First, check whether the token used has expired. Then, check whether the parameter value is set reasonably.
144004	TTS_CLOUD_WAIT_TIMEOUT	Idle timeout.	Confirm whether data has not been sent to the server for a long time (more than 10 seconds).
144005	TTS_CLOUD_EXCEED_CONCURRENCY	Too many requests.	Check whether the number of concurrent connections or requests per second has been exceeded. If the concurrency limit is exceeded, upgrade from the Free Edition to the commercial version, or scale out the concurrency resources for the commercial version.
144006	TTS_CLOUD_DEFAULT_ERROR	Uncategorized error returned by the cloud.	For example, an invalid model ID was used. Check the log for details.
144100	TTS_CLOUD_INVALID_INTERFACE	The interface is not supported.	An unsupported operation was used.
144101	TTS_CLOUD_UNSUPPORTED_ORDER	Unsupported instruction.	An unsupported instruction was used.
144102	TTS_CLOUD_INVALID_ORDER	Invalid instruction.	The instruction format is incorrect.
144103	TTS_CLOUD_CLIENT_DISCONNECT	The client disconnected prematurely.	Check whether the connection was closed before the request was completed normally.
144200	TTS_CLOUD_INVALID_APPKEY	The application does not exist.	Check whether the application AppKey is correct and whether it belongs to the same account as the Token.
144300	TTS_CLOUD_INVALID_PARAM	Parameter error.	Check whether the correct parameters were passed.
144301	TTS_CLOUD_UNSENDAUDIO	The client did not send a command for 10 seconds.	Check for network issues, or check whether there are situations in your business where no data is sent.
144302	TTS_CLOUD_SENDAUDIO_TOO_FAST	The client is sending data too fast, and server resources are exhausted.	Check whether the client is sending packets too fast and whether they are sent at a 1:1 real-time rate.
144303	TTS_CLOUD_INVALID_AUDIO_FORMAT	The audio format sent by the client is incorrect.	Convert the audio data format to a format currently supported by the SDK.
144304	TTS_CLOUD_INVALID_INVOKE	The client method call is abnormal.	The client should call the send request operation first, and then call other operations after the request is sent.
144305	TTS_CLOUD_INVALID_MAX_SILENCE	The client's MAXSILENCE_PARAM method setting is abnormal.	The range of the MAXSILENCE_PARAM parameter is 200 to 2000.
144306	TTS_CLOUD_MISMATCHED_SAMPLERATE	The sample rate does not match.	Check whether the sample rate set during the call is consistent with the sample rate of the ASR model bound to the Appkey on the management console.
144400	TTS_CLOUD_SERVER_ERROR	TTS server error.	This can be ignored if it occurs randomly.
144401	TTS_CLOUD_INTERNAL_SERVER_ERROR	Server internal error.	Unknown error.
144402	TTS_CLOUD_SPEECH_TRANSCRIBER_SERVER_ERROR	The real-time speech recognition service is unavailable.	Check whether the real-time speech recognition service has a task backlog that is causing task submission to fail.
144403	TTS_CLOUD_SPEECH_TRANSCRIBER_REQUEST_TIMEOUT	The request to the real-time speech recognition service timed out.	Check the real-time speech recognition logs.
144404	TTS_CLOUD_INVOKE_SPEECH_TRANSCRIBER_FAILED	Failed to call the real-time speech recognition service.	Check whether the real-time speech recognition service is started and whether the port is open normally.
144405	TTS_CLOUD_SPEECH_TRANSCRIBER_BALANCE_FAILED	Real-time speech recognition service load balancing failed. Failed to get the IP address of the real-time speech recognition service.	Check for exceptions with the real-time speech recognition service machine in the VPC.
144406	TTS_CLOUD_SERVER_AGAIN	Internal call error.	Internal service error. The client needs to retry.

C++ SDK error codes

Status code	Status message	Cause	Solution
10000001	NewSslCtxFailed	SSL: couldn't create a context!	Re-initialize.
10000002	DefaultErrorCode	return of SSL_read: error:00000000:lib(0):func(0):reason(0)	Retry.
10000002	DefaultErrorCode	return of SSL_read: error:140E0197:SSL routines:SSL_shutdown:shutdown while in init	Retry.
10000003	SysErrorCode	System error.	Handle the error based on the feedback from the system.
10000004	EmptyUrl	URL: The url is empty.	The provided URL is empty. Enter a correct URL.
10000005	InvalidWsUrl	Could not parse WebSocket url:	The provided URL format is incorrect. Enter a correct URL.
10000007	JsonStringParseFailed	JSON: Json parse failed.	JSON format exception. Check the log for the specific error point.
10000008	UnknownWsHeadType	WEBSOCKET: unkown head type.	Network connection failed. Check if the local DNS resolution and URL are valid.
10000009	HttpConnectFailed	HTTP: connect failed.	Failed to connect to the cloud. Check the network and retry.
10000010	MemNotEnough	Out of memory.	Check if there is sufficient memory.
10000015	SysConnectFailed	connect failed.	Network connection failed. Check if the local DNS resolution and URL are valid.
10000100	HttpGotBadStatusWith403	Got bad status host=xxxxx line=HTTP/1.1 403 Forbidden	The connection was rejected. Check your account, especially whether the token has expired.
10000101	EvSendTimeout	Send timeout. socket error:	libevent timed out when sending an event. Check whether there are time-consuming tasks in the callback, or whether high concurrency prevents timely event processing.
10000102	EvRecvTimeout	Recv timeout. socket error:	libevent timed out when receiving an event. Check whether there are time-consuming tasks in the callback, or whether high concurrency prevents timely event processing.
10000103	EvUnknownEvent	Unknown event:	Unknown libevent event. Retry.
10000104	OpNowInProgress	Operation now in progress	The connection is in progress. Retry.
10000105	BrokenPipe	Broken pipe	The pipe cannot be processed. Retry.
10000110	TokenHasExpired	Gateway:ACCESS_DENIED:The token 'xxx' has expired!	Update the token.
10000111	TokenIsInvalid	Meta:ACCESS_DENIED:The token 'xxx' is invalid!	Check the validity of the token.
10000112	NoPrivilegeToVoice	Gateway:ACCESS_DENIED:No privilege to this voice! (voice: zhinan, privilege: 0)	You do not have permission to use this speaker.
10000113	MissAuthHeader	Gateway:ACCESS_DENIED:Missing authorization header!	Check whether the account has permission, or whether the concurrency is within the limit.
10000120	Utf8ConvertError	utf8ToGbk failed	UTF-8 transcoding failed. This is often a system issue. Retry.