Error Codes of Device Integration APIs
|
Status Code |
Error Codes |
Error Message |
Description |
Solution |
|---|---|---|---|---|
|
400 |
RML.0001 |
The input parameter is null. |
The input parameter is null. |
Check whether the input parameter is null. |
|
400 |
RML.0002 |
The input parameter is invalid. |
The input parameter is invalid. |
Check whether the input parameter is valid. |
|
400 |
RML.0003 |
The input parameter is not in JSON format or the format is invalid. |
The input parameter is not in JSON format or the format is invalid. |
Check whether the input parameter is in JSON format or the format is valid. |
|
400 |
RML.0004 |
The project ID is null or invalid. |
The project ID is null or invalid. |
Check whether the product ID is null or valid. |
|
400 |
RML.0005 |
The request body is null. |
The request body is null. |
Check whether the request body is null. |
|
400 |
RML.0006 |
The request parameter is not in JSON format. |
The request parameter is not in JSON format. |
Check whether the request parameter is in JSON format. |
|
400 |
RML.0007 |
The query parameter is invalid. |
The query parameter is invalid. |
Check whether the query parameter is valid. |
|
400 |
RML.0008 |
No operation permission. |
No operation permission. |
You need to replace the user or role that has the permission to perform this operation. |
|
400 |
RML.0009 |
No CSV found. |
No CSV found. |
Choose CSV file to import. |
|
400 |
RML.0010 |
Failed to write data into the CSV file. |
Failed to write data into the CSV file. |
Check whether CSV file exists. |
|
400 |
RML.0011 |
Failed to export data. |
Failed to export data. |
Check whether data exists. |
|
400 |
RML.0012 |
Failed to download ssl certificate. |
Failed to download ssl certificate. |
Check whether the internet connection is normal. |
|
400 |
RML.0013 |
The input parameter oid is null. |
The input parameter oid is null. |
Input the parameter oid which is not null. |
|
400 |
RML.0014 |
The Topic field in the CSV file is incorrect. Check product serial number and device name in Topic. |
The Topic field in the CSV file is incorrect. Check product serial number and device name in Topic. |
Change the topic field and try again. |
|
400 |
RML.0015 |
Incorrect file extension. |
Incorrect file extension. |
Change the file extension and try again. |
|
400 |
RML.0100 |
Invalid instance ID. |
Invalid instance ID. |
Change the instance ID. |
|
400 |
RML.0101 |
The instance is not running. |
The instance is not running. |
Keep the instance running and try again. |
|
400 |
RML.0102 |
The instance does not exist. |
The instance does not exist. |
Create the instance and try again. |
|
400 |
RML.0103 |
The instance ID is null. |
The instance ID is null. |
Add the instance ID. |
|
400 |
RML.0104 |
Invalid instance parameter. |
Invalid instance parameter. |
Check whether the instance parameter is valid. |
|
400 |
RML.0105 |
Failed to reset the instance password. |
Failed to reset the instance password. |
Check whether the instance exists. |
|
400 |
RML.0106 |
Invalid instance number. |
Invalid instance number. |
Check whether the instance number is correct. |
|
400 |
RML.0200 |
The device ID is null or invalid. |
The device ID is null or invalid. |
Check whether the device ID is null or invalid. |
|
400 |
RML.0201 |
The device name is null or invalid. |
The device name is null or invalid. |
Check whether the device name is null or invalid. |
|
400 |
RML.0202 |
The device name already exists. |
The device name already exists. |
Change the device name and try again. |
|
400 |
RML.0203 |
The device does not exist. |
The device does not exist. |
Create the device and try again. |
|
400 |
RML.0204 |
The device status is null or invalid. |
The device status is null or invalid. |
Check whether the device status is null or invalid. |
|
400 |
RML.0205 |
The device description is longer than 200 characters. |
The device description is longer than 200 characters. |
Change the length of the device description. |
|
400 |
RML.0206 |
The client ID of the device is null or invalid. |
The client ID of the device is null or invalid. |
Check whether the client ID is null or invalid. |
|
400 |
RML.0207 |
Duplicated device names exist during device adding in batches. |
Duplicated device names exist during device adding in batches. |
Change the duplicated device names. |
|
400 |
RML.0208 |
The device quota is not enough. |
The device quota is not enough. |
Contact the administrator to increase the device quota. |
|
400 |
RML.0209 |
The number of devices to be imported to the CSV file is over 1000. |
The number of devices to be imported to the CSV file is over 1000. |
Change the number of devices to be imported to the CSV file. |
|
400 |
RML.0210 |
The number of batch added devices exceeds 100. |
The number of batch added devices exceeds 100. |
Change the number of batch added devices. |
|
400 |
RML.0212 |
The topic name is null or invalid. |
The topic name is null or invalid. |
Check whether the topic name is null or invalid. |
|
400 |
RML.0213 |
The topic already exists. |
The topic already exists. |
Change the topic and try again. |
|
400 |
RML.0214 |
The topic does not exist. |
The topic does not exist. |
Create the topic and try again. |
|
400 |
RML.0215 |
The permission name of the device topic is incorrect. |
The permission name of the device topic is incorrect. |
Change the permission name of the device topic. |
|
400 |
RML.0216 |
The device topic description cannot exceed 200 characters. |
The device topic description cannot exceed 200 characters. |
Change the length of the device topic description. |
|
400 |
RML.0217 |
The topic name already exists. |
The topic name already exists. |
Change the topic name. |
|
400 |
RML.0218 |
The topic quota is not enough. |
The topic quota is not enough. |
Contact the administrator to increase the topic quota. |
|
400 |
RML.0219 |
Incorrect title format for the device CSV file. |
Incorrect title format for the device CSV file. |
Change the title format for the device CSV file. |
|
400 |
RML.0220 |
The number of devices to be exported exceeds 1000. |
The number of devices to be exported exceeds 1000. |
Change the number of devices to be exported. |
|
400 |
RML.0221 |
Choose at least one device when exporting data. |
Choose at least one device when exporting data. |
Choose one or more device data to export. |
|
400 |
RML.0222 |
The device parameter is null. |
The device parameter is null. |
Check whether the device parameter is null. |
|
400 |
RML.0223 |
Duplicate client IDs exist during device adding in batches. |
Duplicate client IDs exist during device adding in batches. |
Change the duplicated client IDs. |
|
400 |
RML.0224 |
The device client ID already exists in the local database. |
The device client ID already exists in the local database. |
Change the device client ID. |
|
400 |
RML.0225 |
Failed to reset the device password. |
Failed to reset the device password. |
Check whether the device exists. |
|
400 |
RML.0226 |
Invalid user name of the device. |
Invalid user name of the device. |
Check whether the user name of the device is valid. |
|
400 |
RML.0227 |
Invalid password of the device. |
Invalid password of the device. |
Check whether password of the device is valid. |
|
400 |
RML.0228 |
The number of devices to be exported exceeds 500. |
The number of devices to be exported exceeds 500. |
Change the number of devices to be exported. |
|
400 |
RML.0229 |
The device name is invalid or duplicated. |
The device name is invalid or duplicated. |
Check whether the device name is valid or duplicated. |
|
400 |
RML.0230 |
The device status is invalid. |
The device status is invalid. |
Check whether the device status is valid. |
|
400 |
RML.0231 |
All the uploaded devices already exist. |
All the uploaded devices already exist. |
Change the uploaded devices which are exist. |
|
400 |
RML.0232 |
The client ID is invalid or duplicated. |
The client ID is invalid or duplicated. |
Check whether the device ID is valid or duplicated. |
|
400 |
RML.0233 |
The topic name does not exist. |
The topic name does not exist. |
Check whether the topic name is exist. |
|
400 |
RML.0234 |
Invalid topic ID. |
Invalid topic ID. |
Check whether topic ID is valid. |
|
400 |
RML.0235 |
Deleting online devices is not allowed. |
Deleting online devices is not allowed. |
Keep the devices offline and try again. |
|
400 |
RML.0236 |
The device is offline. |
The device is offline. |
Keep the device online and try again. |
|
400 |
RML.0237 |
The device is not a gateway. |
The device is not a gateway. |
Change the gateway device and try again. |
|
400 |
RML.0238 |
The mqtt node does not exist. |
The mqtt node does not exist. |
Create the mqtt node and try again. |
|
400 |
RML.0300 |
The product ID is null or invalid. |
The product ID is null or invalid. |
Check whether the product ID is null or invalid. |
|
400 |
RML.0301 |
The product name is invalid. |
The product name is invalid. |
Check whether the product name is valid. |
|
400 |
RML.0302 |
The product does not exist. |
The product does not exist. |
Create the product and try again. |
|
400 |
RML.0303 |
The product description is longer than 200 characters. |
The product description is longer than 200 characters. |
Change the length of product description. |
|
400 |
RML.0304 |
The product already exists. |
The product already exists. |
Change the product and try again. |
|
400 |
RML.0305 |
The product quota is not enough. |
The product quota is not enough. |
Contact the administrator to increase the product quota. |
|
400 |
RML.0306 |
The product name does not exist. |
The product name does not exist. |
Add the product name. |
|
400 |
RML.0308 |
The product attribute does not exist. |
The product attribute does not exist. |
Add the product attribute. |
|
400 |
RML.0309 |
The product attribute already exists. |
The product attribute already exists. |
Change the product attribute and try again. |
|
400 |
RML.0310 |
The product attribute identifier is invalid. |
The product attribute identifier is invalid. |
Check whether the product attribute identifier is valid. |
|
400 |
RML.0311 |
The product attribute identifier already exists. |
The product attribute identifier already exists. |
Change the product attribute identifier and try again. |
|
400 |
RML.0312 |
Import a product before importing a device. |
Import a product before importing a device. |
Import the device and try again. |
|
400 |
RML.0313 |
The product list is null. |
The product list is null. |
Choose one or more products to export. |
|
400 |
RML.0314 |
Invalid product serial number. |
Invalid product serial number. |
Check whether the product serial number is valid. |
|
400 |
RML.0315 |
All the uploaded products already exist. |
All the uploaded products already exist. |
Change the existing products and try again. |
|
400 |
RML.0316 |
Incorrect field in the title of the product CVS file. |
Incorrect field in the title of the product CVS file. |
Check whether fields in the title of the product CSV file are correct. |
|
400 |
RML.0317 |
The product name already exists. |
The product name already exists. |
Change the product name and try again. |
|
400 |
RML.0318 |
The product attribute name already exists. |
The product attribute name already exists. |
Change the product attribute name and try again. |
|
400 |
RML.0319 |
Invalid product name. |
Invalid product name. |
Check whether the product name is valid. |
|
400 |
RML.0320 |
Failed to reset the product password. |
Failed to reset the product password. |
Check whether the product exists. |
|
400 |
RML.0321 |
A product with devices attached cannot be deleted. |
A product with devices attached cannot be deleted. |
Delete all devices of the product and try again. |
|
400 |
RML.0322 |
The number of products to be exported exceeds 500. |
The number of products to be exported exceeds 500. |
Change the number of products to be exported. |
|
400 |
RML.0323 |
The product user name in the CSV file is invalid. |
The product user name in the CSV file is invalid. |
Check whether the product user name is valid. |
|
400 |
RML.0324 |
The product password in the CSV file is invalid. |
The product password in the CSV file is invalid. |
Check whether the product password in the CSV file is valid. |
|
400 |
RML.0400 |
The model name already exists. |
The model name already exists. |
Change the model name and try again. |
|
400 |
RML.0401 |
Unable to edit the attribute when the model is in disabled state. |
Unable to edit the attribute when the model is in disabled state. |
Enable the model and try again. |
|
400 |
RML.0402 |
The model attribute does not exist. |
The model attribute does not exist. |
Add the model attribute. |
|
400 |
RML.0403 |
The model attribute name already exists. |
The model attribute name already exists. |
Change the model attribute name and try again. |
|
400 |
RML.0404 |
The model attribute identifier already exists. |
The model attribute identifier already exists. |
Change the model attribute identifier and try again. |
|
400 |
RML.0405 |
A model with products attached cannot be deleted. |
A model with products attached cannot be deleted. |
Delete all products of the model and try again. |
|
400 |
RML.0406 |
Invalid model ID. |
Invalid model ID. |
Check whether the model ID is valid. |
|
400 |
RML.0407 |
The model ID does not exist. |
The model ID does not exist. |
Create the model ID. |
|
400 |
RML.0408 |
The model does not exist. |
The model does not exist. |
Create the model. |
|
400 |
RML.0409 |
Invalid model name. |
Invalid model name. |
Check whether the model name is valid. |
|
400 |
RML.0410 |
The model description is longer than 200 characters. |
The model description is longer than 200 characters. |
Change the length of the model description. |
|
400 |
RML.0411 |
The model already exists. |
The model already exists. |
Change the model and try again. |
|
400 |
RML.0412 |
Invalid attribute identifier. |
Invalid attribute identifier. |
Check whether attribute identifier is valid. |
|
400 |
RML.0413 |
Invalid attribute data unit. |
Invalid attribute data unit. |
Check whether attribute data unit is valid. |
|
400 |
RML.0414 |
Invalid attribute default data type. |
Invalid attribute default data type. |
Check whether attribute default data type is valid. |
|
400 |
RML.0415 |
The attribute description is longer than 200 characters. |
The attribute description is longer than 200 characters. |
Change the length of attribute description. |
|
400 |
RML.0416 |
Invalid attribute name. |
Invalid attribute name. |
Check whether the attribute name is valid. |
|
400 |
RML.0417 |
The model status is null or invalid. |
The model status is null or invalid. |
Check whether the model status is valid. |
|
400 |
RML.0500 |
The data source of the rule engine is invalid. |
The data source of the rule engine is invalid. |
Check whether the data source of the rule engine is valid. |
|
400 |
RML.0501 |
The rule engine does not exist. |
The rule engine does not exist. |
Add the rule engine. |
|
400 |
RML.0502 |
Invalid rule engine ID. |
Invalid rule engine ID. |
Check whether the rule engine is valid. |
|
400 |
RML.0503 |
The level of the rule engine should be 0 or 1. |
The level of the rule engine should be 0 or 1. |
Change the level of the rule engine. |
|
400 |
RML.0504 |
The rule engine source does not exist. |
The rule engine source does not exist. |
Add the rule engine source. |
|
400 |
RML.0505 |
Invalid rule name. |
Invalid rule name. |
Check whether the rule name is valid. |
|
400 |
RML.0506 |
The topic is already added to the source. |
The topic is already added to the source. |
Change the topic of the source. |
|
400 |
RML.0507 |
Only one topic can be added to the source rule. |
Only one topic can be added to the source rule. |
Change the number of the source rule's topics. |
|
400 |
RML.0508 |
The source rule is not supported. |
The source rule is not supported. |
Change the source rule. |
|
400 |
RML.0509 |
Only one topic can be added to the destination rule. |
Only one topic can be added to the destination rule. |
Change the number of the destination rule's topics. |
|
400 |
RML.0510 |
The topic quota is not enough. |
The topic quota is not enough. |
Contact the administrator to increase the quota. |
|
400 |
RML.0511 |
Invalid destination address. |
Invalid destination address. |
Check whether the destination address is valid. |
|
400 |
RML.0512 |
The topic of the MQS destination is invalid. |
The topic of the MQS destination is invalid. |
Change MQS Topic. |
|
400 |
RML.0513 |
The destination MQS user name or password is null. |
The destination MQS user name or password is null. |
Check whether the user name or password is null. |
|
400 |
RML.0514 |
The level of the rule engine should be device or product. |
The level of the rule engine should be device or product. |
Change the level of the rule engine. |
|
400 |
RML.0515 |
The rule engine already exists. |
The rule engine already exists. |
Change the rule engine and try again. |
|
400 |
RML.0516 |
The rule engine status is invalid. |
The rule engine status is invalid. |
Change the rule engine status. |
|
400 |
RML.0517 |
The rule engine description is too long. |
The rule engine description is too long. |
Change the length of rule engine description. |
|
400 |
RML.0518 |
The rule name already exists. |
The rule name already exists. |
Change the rule name. |
|
400 |
RML.0519 |
Invalid rule source ID. |
Invalid rule source ID. |
Change the rule source ID. |
|
400 |
RML.0520 |
Invalid rule destination ID. |
Invalid rule destination ID. |
Change the rule destination ID. |
|
400 |
RML.0521 |
Invalid rule destination type. |
Invalid rule destination type. |
Change the type of rule destination. |
|
400 |
RML.0522 |
Rule destination device topic exists. |
Rule destination device topic exists. |
Change the topic of rule destination device. |
|
400 |
RML.0523 |
Rule destination connection failed. |
Rule destination connection failed. |
Check whether the rule destination connection is normal. If the fault persists, contact technical support for assistance. |
|
400 |
RML.0524 |
Rule already has javascript express. |
Rule already has javascript express. |
Delete the javascript express and try again. |
|
400 |
RML.0525 |
The sql field is invalid. |
The sql field is invalid. |
Modify the SQL field. |
|
400 |
RML.0526 |
Rule already has sql express. |
Rule already has sql express. |
Delete SQL and try again. |
|
400 |
RML.0527 |
Product does not belong to the app. |
Product does not belong to the app. |
Choose the product under this app. |
|
400 |
RML.0528 |
The rule and product belong to different apps. |
The rule and product belong to different apps. |
Choose the rule engine and product under the same app. |
|
400 |
RML.4038 |
The input parameters of the interface used for query are incorrect. judge the error information according to the prompt. Fill in the correct parameters again. |
Invalid {x} parameter in the request. |
Check whether the input parameters comply with the rules as prompted. |
|
400 |
RML.4039 |
The input parameters of the interface used for requesting are incorrect, and the error information is judged according to the prompt. Enter the correct parameters again |
Invalid {x} parameter in the request. |
Check whether the input parameters comply with the rules as prompted. |
|
400 |
RML.4040 |
The input parameter format of the interface used for requesting is incorrect. judge the error information according to the prompt and fill in the parameter that complies with the rule again. |
parameter {x} format error. It must be {1}. |
Check whether the input parameters comply with the rules as prompted. |
|
400 |
ROMA.00110001 |
The parameter does not meet verification rules: {0} |
The parameter does not meet verification rules: {0} |
Check whether the parameter complies with the rules as prompted. |
|
401 |
RML.4101 |
The token carried in the request interface is invalid. The login page may time out. You need to refresh the page for login. |
Invalid token. |
The login page may have timed out and needs to be refreshed. Login again before operation. |
|
403 |
RML.4303 |
The currently logged in user or role does not have permission to perform the operation. |
This role does not have the permission to perform this operation. |
You need to replace the user or role that has the permission to perform this operation. |
|
403 |
ROMA.00110005 |
You do not have the {0} permission on the application to which the resource belongs. |
You do not have the {0} permission on the application to which the resource belongs. |
Grant the required permission by clicking Authorize User on the Integration Applications page of the ROMA Connect console. |
|
403 |
ROMA.00110007 |
You do not have the permission to view any application resources. Choose Integration Applications > Authorize User, and check whether you have been granted the corresponding permission. |
You do not have the permission to view any application resources. Choose Integration Applications > Authorize User, and check whether you have been granted the corresponding permission. |
Grant the required permission by clicking Authorize User on the Integration Applications page of the ROMA Connect console. |
|
403 |
ROMA.00110008 |
You do not have the {0} permission on the resource. Check whether you have been granted the corresponding permission in the related service. |
You do not have the {0} permission on the resource. Check whether you have been granted the corresponding permission in the related service. |
Grant the required permission by clicking Authorize User on the Integration Applications page of the ROMA Connect console. |
|
403 |
ROMA.00110014 |
The current login account has limited rights and no op _ service rights. |
The account is not an op_service account and does not have permission to perform the current operation |
Change the account with op _ service permission to log in again. |
|
403 |
ROMA.00110015 |
The current account has limited rights and does not have the right to operate the current instance. |
The current account does not have permission to operate the current instance: {0} |
Change the account with permission to operate the instance to log in and then operate. |
|
404 |
RML.4041 |
The interface input parameter for the request is missing a field, and an error message is judged according to the prompt. Fill in the correct parameters again. |
missing param {x}. |
Add this field parameter according to the page prompt. |
|
404 |
RML.4402 |
Failed to create the instance. failed to query the instance. Database error. querying database failed. |
This ROMALINK instance does not exist. |
Contact technical support for assistance. |
|
404 |
ROMA.00110006 |
The resource does not exist. Check whether the resource ID {0} is correct. |
The resource does not exist. Check whether the resource ID {0} is correct. |
Check whether the resource ID exists. |
|
500 |
ROMA.00110000 |
Internal Error. |
Internal Error. |
Contact technical support for assistance. |
|
500 |
ROMA.00110002 |
The instance does not exist. project_id: {0}, instance_id: {1} |
The instance does not exist. project_id: {0}, instance_id: {1} |
Create an instance or use another instance. |
|
500 |
ROMA.00110003 |
An error occurs when reading data from or writing data to Redis on the data plane. |
An error occurs when reading data from or writing data to Redis on the data plane. |
Check whether the network and instance status are normal. If the fault persists, contact technical support for assistance. |
|
500 |
ROMA.00110004 |
The quota exceeds the upper limit, {0}. Increase the quota. |
The quota exceeds the upper limit, {0}. Increase the quota. |
Contact the administrator to increase the quota. |
|
500 |
ROMA.00110009 |
The request body is empty. |
The request body is empty. |
Transfer the correct request body. |
|
500 |
ROMA.00110010 |
Failed to call the MQS interface. |
Failed to call the MQS interface. |
Check whether the MQS service is normal. If the fault persists, contact technical support for assistance. |
|
500 |
ROMA.00110011 |
Invalid encoding format. Check whether the encoding format of the file is UTF8. |
Invalid encoding format. Check whether the encoding format of the file is UTF8. |
Check the file encoding format. If the file encoding format is not UTF8, change it to UTF8. |
|
500 |
ROMA.00110012 |
The maximum number of products to be deleted at a time cannot exceed {0}. |
The maximum number of products to be deleted at a time cannot exceed {0}. |
Reduce the number of products to batch delete each time. |
|
500 |
ROMA.00110013 |
The maximum number of devices to be deleted at a time cannot exceed {0}. |
The maximum number of devices to be deleted at a time cannot exceed {0}. |
Reduce the number of devices to batch delete each time. |
|
500 |
ROMA.00110201 |
The product template name {0} already exists. Change the name and try again. |
The product template name {0} already exists. Change the name and try again. |
Use another product template name and try again. |
|
500 |
ROMA.00110202 |
The product template corresponding to the ID {0} does not exist. Select an existing product template and try again. |
The product template corresponding to the ID {0} does not exist. Select an existing product template and try again. |
Select an existing product template and try again. |
|
500 |
ROMA.00110203 |
The product template is being disabled. Enable the template first. |
The product template is being disabled. Enable the template first. |
Enable the product template and try again. |
|
500 |
ROMA.00110401 |
The command name {0} already exists. Change the name and try again. |
The command name {0} already exists. Change the name and try again. |
Use another command name and try again. |
|
500 |
ROMA.00110402 |
The command name {0} does not exist. Select an existing command and try again. |
The command name {0} does not exist. Select an existing command and try again. |
Select an existing command and try again. |
|
500 |
ROMA.00110403 |
The command delivery field name {0} already exists. Change the name and try again. |
The command delivery field name {0} already exists. Change the name and try again. |
Use another name and try again. |
|
500 |
ROMA.00110404 |
The command delivery field name {0} does not exist. Select an existing command delivery field and try again. |
The command delivery field name {0} does not exist. Select an existing command delivery field and try again. |
Select an existing command delivery field and try again. |
|
500 |
ROMA.00110405 |
The command response field name {0} already exists. Change the name and try again. |
The command response field name {0} already exists. Change the name and try again. |
Use another command response field name and try again. |
|
500 |
ROMA.00110406 |
The service name {0} already exists. Change the name and try again. |
The service name {0} already exists. Change the name and try again. |
Use another name and try again. |
|
500 |
ROMA.00110407 |
The attribute name {0} already exists. Change the name and try again. |
The attribute name {0} already exists. Change the name and try again. |
Use another attribute name and try again. |
|
500 |
ROMA.00110701 |
The product name {0} already exists. |
The product name {0} already exists. |
Use another product name. |
|
500 |
ROMA.00110702 |
The product with ID {0} does not exist. |
The product with ID {0} does not exist. |
Check whether the corresponding product exists. |
|
500 |
ROMA.00110703 |
The product named {0} contains devices. Delete all devices under the product and try again. |
The product named {0} contains devices. Delete all devices under the product and try again. |
Delete all devices under the product and then delete the product. |
|
500 |
ROMA.00110704 |
The product has been used in a rule. |
The product has been used in a rule. |
Delete the product used in the rule engine. |
|
500 |
ROMA.00110705 |
The topic name {0} of the product already exists. |
The topic name {0} of the product already exists. |
Use another topic name and try again. |
|
500 |
ROMA.00110706 |
The manufacturer ID and product model already exist. |
The manufacturer ID and product model already exist. |
Use another manufacturer ID and product model and try again. |
|
500 |
ROMA.00110707 |
The product topic has been used in the rule {0} and cannot be modified. Delete the product topic used in the rule and then modify the product topic. |
The product topic has been used in the rule {0} and cannot be modified. Delete the product topic used in the rule and then modify the product topic. |
Delete the product topic used in the rule engine. |
|
500 |
ROMA.00110708 |
Failed to create an MQS topic for product {0}. Check whether the number of MQS topic partitions exceeds the partition limit or whether the MQS service is normal, and try again. |
Failed to create an MQS topic for product {0}. Check whether the number of MQS topic partitions exceeds the partition limit or whether the MQS service is normal, and try again. |
Check whether the MQS service is normal. If the fault persists, contact technical support for assistance. |
|
500 |
ROMA.00110709 |
Failed to delete the MQS topic when deleting product {0}. Check whether the MQS service is available. |
Failed to delete the MQS topic when deleting product {0}. Check whether the MQS service is available. |
Check whether the MQS service is normal. If the fault persists, contact technical support for assistance. |
|
500 |
ROMA.00110710 |
The product protocol {0} is not supported. |
The product protocol {0} is not supported. |
Select a correct product protocol. |
|
500 |
ROMA.00110711 |
The topic has been bound to a connection point on the OPC UA device {0} and cannot be modified. Delete the connection point from the OPC UA device first. |
The topic has been bound to a connection point on the OPC UA device {0} and cannot be modified. Delete the connection point from the OPC UA device first. |
Delete the connection of the OPC UA device, and then modify the product topic. |
|
500 |
ROMA.00110712 |
The app ID does not exist. Enter a correct app ID. |
The app ID does not exist. Enter a correct app ID. |
Use a correct application ID. |
|
500 |
ROMA.00110713 |
Gateway products cannot be created on old instances. Create a common product. |
Gateway products cannot be created on old instances. Create a common product. |
Create a common product. |
|
500 |
ROMA.00110714 |
All products to be imported already exist. |
All products to be imported already exist. |
Select the product to import again. |
|
500 |
ROMA.00110715 |
The title row contains incorrect fields. See the title: {0}. |
The title row contains incorrect fields. See the title: {0}. |
Check and modify the fields in the title row of the file as prompted. |
|
500 |
ROMA.00110716 |
The product does not exist. Select at least one product to export. |
The product does not exist. Select at least one product to export. |
Check whether the subscriber has products. If yes, select at least one product and export it again. |
|
500 |
ROMA.00110717 |
The number of products to be exported cannot exceed 500. |
The number of products to be exported cannot exceed 500. |
Check that the number of products to export does not exceed 500. |
|
500 |
ROMA.00110718 |
Failed to read the file stream. Check whether the file is normal or whether the network connection is normal. |
Failed to read the file stream. Check whether the file is normal or whether the network connection is normal. |
Check whether the network connection is normal. Check whether the file is damaged. Check whether the file contains a large number of empty rows. |
|
500 |
ROMA.00110719 |
The app name does not exist. Check the app name {0}. |
The app name does not exist. Check the app name {0}. |
Based on the error information, change the application name in the file or create an application with the same name. |
|
500 |
ROMA.00110720 |
The file does not exist or the file format is incorrect. Import a CSV file. |
The file does not exist or the file format is incorrect. Import a CSV file. |
Check whether the imported CSV file is correct. |
|
500 |
ROMA.00110721 |
Failed to read the CSV file. Check the file content. |
Failed to read the CSV file. Check the file content. |
Check whether the CSV file content is valid. |
|
500 |
ROMA.00110722 |
Failed to query the product. Check whether product data in the request exists. |
Failed to query the product. Check whether product data in the request exists. |
Check whether the product data exists in the request. |
|
500 |
ROMA.00110723 |
Incorrect DeviceType field in the file: {0}. |
Incorrect DeviceType field in the file: {0}. |
Check whether the value of the DeviceType field is correct. |
|
500 |
ROMA.00110724 |
Incorrect ProductType field in the file: {0}. |
Incorrect ProductType field in the file: {0}. |
Check whether the value of the ProductType field is correct. |
|
500 |
ROMA.00110725 |
Incorrect DataFormat field in the file: {0}. |
Incorrect DataFormat field in the file: {0}. |
Check whether the value of the DataFormat field is correct. |
|
500 |
ROMA.00110726 |
The file is abnormal. Check the file content {0}. |
The file is abnormal. Check the file content {0}. |
Check whether the file content is correct. |
|
500 |
ROMA.00110727 |
Failed to obtain the service address of ROMA Server. Check whether this service address is configured in the environment. |
Failed to obtain the service address of ROMA Server. Check whether this service address is configured in the environment. |
Contact technical support for assistance. |
|
500 |
ROMA.00110728 |
Incorrect device type: {0}. Enter a correct device type or define a new device type in the data dictionary. |
Incorrect device type: {0}. Enter a correct device type or define a new device type in the data dictionary. |
Enter the correct device type when calling the API of creating a product. |
|
500 |
ROMA.00110729 |
Failed to request ROMA Server. Check whether ROMA Server is available. |
Failed to request ROMA Server. Check whether ROMA Server is available. |
Contact technical support for assistance. |
|
500 |
ROMA.00110730 |
Illegal product ID during export: {0}. |
Illegal product ID during export: {0}. |
Check whether the entered product ID list is a numeric value. If yes, import the product ID list again. |
|
500 |
ROMA.00111001 |
The product associated with the device does not belong to the specified application {0}. Check whether the app ID is correct. |
The product associated with the device does not belong to the specified application {0}. Check whether the app ID is correct. |
Check whether the application ID is correct. |
|
500 |
ROMA.00111002 |
Invalid tag name: {0}. Enter a maximum of 64 characters, consisting of letters, digits, hyphens (-), and underscores (_). |
Invalid tag name: {0}. Enter a maximum of 64 characters, consisting of letters, digits, hyphens (-), and underscores (_). |
Check whether the tag key is valid. |
|
500 |
ROMA.00111003 |
The device ID {0} already exists. Change the device ID. |
The device ID {0} already exists. Change the device ID. |
Change the device ID. |
|
500 |
ROMA.00111004 |
Failed to forcibly bring device {0} offline. Possible cause: The data plane service is abnormal. |
Failed to forcibly bring device {0} offline. Possible cause: The data plane service is abnormal. |
Check whether the network between the management plane and the data plane is normal and whether the instance is running properly. If the fault persists, contact technical support for assistance. |
|
500 |
ROMA.00111005 |
Commands cannot be delivered to a device in disconnected state. Bring the device online first. |
Commands cannot be delivered to a device in disconnected state. Bring the device online first. |
Bring the device online and try again. |
|
500 |
ROMA.00111006 |
Commands cannot be delivered to a device in disabled state. Enable the device first. |
Commands cannot be delivered to a device in disabled state. Enable the device first. |
Enable the device. |
|
500 |
ROMA.00111007 |
Commands cannot be delivered to an offline device if the device shadow is disabled. Enable the device shadow first. |
Commands cannot be delivered to an offline device if the device shadow is disabled. Enable the device shadow first. |
Enable the device shadow. |
|
500 |
ROMA.00111008 |
Failed to deliver the command. Check whether the server status is normal. |
Failed to deliver the command. Check whether the server status is normal. |
Check whether the device is connected. Check whether the network connection of the data plane is normal. Check whether the instance status is normal. If the fault persists, contact technical support for assistance. |
|
500 |
ROMA.00111009 |
An online device cannot be deleted. Bring the device offline first. |
An online device cannot be deleted. Bring the device offline first. |
Check whether the device is online. If the device is online, bring the device offline and delete the device. |
|
500 |
ROMA.00111010 |
Failed to query the device. Check whether the device data in the request exists. |
Failed to query the device. Check whether the device data in the request exists. |
Check whether the device data exists in the request. |
|
500 |
ROMA.00111011 |
The device contains subdevices and cannot be deleted. Delete the subdevices under the device first. |
The device contains subdevices and cannot be deleted. Delete the subdevices under the device first. |
Delete the subdevices under the device and then delete the device. |
|
500 |
ROMA.00111012 |
Failed to deliver the command for deleting the subdevice. Check whether the gateway managing the subdevice exists. |
Failed to deliver the command for deleting the subdevice. Check whether the gateway managing the subdevice exists. |
Check whether the gateway of the subdevice exists. |
|
500 |
ROMA.00111013 |
Failed to deliver the command for deleting the subdevice. Check whether the product to which the subdevice belongs exists. |
Failed to deliver the command for deleting the subdevice. Check whether the product to which the subdevice belongs exists. |
Check whether the product associated with the subdevice exists. |
|
500 |
ROMA.00111014 |
Failed to register the subdevice because the specified gateway does not exist. |
Failed to register the subdevice because the specified gateway does not exist. |
Check whether the specified gateway device ID is correct. |
|
500 |
ROMA.00111015 |
Failed to register the subdevice because the specified gateway is invalid. |
Failed to register the subdevice because the specified gateway is invalid. |
Use a correct gateway device ID. |
|
500 |
ROMA.00111016 |
Failed to register the subdevice because the product associated with the subdevice must be of the common type. |
Failed to register the subdevice because the product associated with the subdevice must be of the common type. |
Check whether the associated product is a common product. |
|
500 |
ROMA.00111017 |
Failed to obtain the username and password of the device. Check whether the device data is correct. |
Failed to obtain the username and password of the device. Check whether the device data is correct. |
Check whether the token_oid associated with the device exists. |
|
500 |
ROMA.00111018 |
Only a directly connected device can be added as a gateway subdevice. Check whether the type of the added device is correct. |
Only a directly connected device can be added as a gateway subdevice. Check whether the type of the added device is correct. |
Check the device type and select a directly connected device as the subdevice of the gateway. |
|
500 |
ROMA.00111019 |
An online device cannot be added as a gateway subdevice. Bring the device offline first. |
An online device cannot be added as a gateway subdevice. Bring the device offline first. |
Check the device status and bring the device offline. |
|
500 |
ROMA.00111020 |
The Modbus connection point does not exist. Device ID: {0}; connection point ID: {1}. |
The Modbus connection point does not exist. Device ID: {0}; connection point ID: {1}. |
Check whether the Modbus connection point exists. If the connection point does not exist, create it. If yes, contact technical support for assistance. |
|
500 |
ROMA.00111021 |
The Modbus policy does not exist. Device ID: {0}; connection point ID: {1}; policy ID: {2}. |
The Modbus policy does not exist. Device ID: {0}; connection point ID: {1}; policy ID: {2}. |
Check whether the Modbus policy exists. If the Modbus policy does not exist, create it. If the Modbus policy already exists, contact technical support for assistance. |
|
500 |
ROMA.00111022 |
The Modbus policy name {2} (device ID: {0}; connection point ID: {1}) already exists. Change the Modbus policy name. |
The Modbus policy name {2} (device ID: {0}; connection point ID: {1}) already exists. Change the Modbus policy name. |
Use another Modbus policy name. |
|
500 |
ROMA.00111023 |
All node paths in the imported file already exist. |
All node paths in the imported file already exist. |
Change the node path in the imported file. |
|
500 |
ROMA.00111024 |
The OPC UA connection point does not exist. Device ID: {0}; connection point ID: {1}. |
The OPC UA connection point does not exist. Device ID: {0}; connection point ID: {1}. |
Check whether the OPC UA connection point exists. If the connection point does not exist, create it. If the connection point already exists, contact technical support for assistance. |
|
500 |
ROMA.00111025 |
The OPC UA connection point name {1} (device ID: {0}) already exists. Change the OPC UA connection point name. |
The OPC UA connection point name {1} (device ID: {0}) already exists. Change the OPC UA connection point name. |
Use another connection point name. |
|
500 |
ROMA.00111026 |
The OPC UA node does not exist. Device ID: {0}; connection point ID: {1}; node ID: {2}. |
The OPC UA node does not exist. Device ID: {0}; connection point ID: {1}; node ID: {2}. |
Check whether the OPC UA node exists. If the OPC UA node does not exist, create it. If the OPC UA node already exists, contact technical support for assistance. |
|
500 |
ROMA.00111027 |
The OPC UA node does not belong to the current device. Node ID: {0}; device ID: {1}. |
The OPC UA node does not belong to the current device. Node ID: {0}; device ID: {1}. |
Check whether the OPC UA node exists. If the OPC UA node does not exist, create it. If the OPC UA node already exists, contact technical support for assistance. |
|
500 |
ROMA.00111028 |
The node_path {2} (device ID: {0}; connection point ID: {1}) already exists. Change the node path of the OPC UA node. |
The node_path {2} (device ID: {0}; connection point ID: {1}) already exists. Change the node path of the OPC UA node. |
Modify the corresponding connection point in the OPC UA configuration of the device. |
|
500 |
ROMA.00111029 |
The Modbus connection point (device ID: {0}; connection point name: {1}) already exists. Change the Modbus connection point name. |
The Modbus connection point (device ID: {0}; connection point name: {1}) already exists. Change the Modbus connection point name. |
Use another Modbus connection point name. |
|
500 |
ROMA.00111030 |
The Modbus connection point name {1} (device ID: {0}) already exists. Change the Modbus connection point name. |
The Modbus connection point name {1} (device ID: {0}) already exists. Change the Modbus connection point name. |
Modify the name of the Modbus connection point as prompted. |
|
500 |
ROMA.00111031 |
Failed to deliver the command to Edgeshell. |
Failed to deliver the command to Edgeshell. |
Check whether the LINK instance is normal. If the fault persists, contact technical support for assistance. |
|
500 |
ROMA.00111032 |
Failed to deliver commands to the offline Edgeshell. Bring Edgeshell online and try again. |
Failed to deliver commands to the offline Edgeshell. Bring Edgeshell online and try again. |
Check whether the device is online. If not, bring the device online. |
|
500 |
ROMA.00111033 |
The specified service ID or command ID does not exist. Check whether the entered service ID or command ID is correct. |
The specified service ID or command ID does not exist. Check whether the entered service ID or command ID is correct. |
Check whether the service ID and command ID exist under the product to which the device belongs. |
|
500 |
ROMA.00111034 |
{0} OPC UA nodes to be exported, which exceeds the upper limit {1}. |
{0} OPC UA nodes to be exported, which exceeds the upper limit {1}. |
Reduce the number of OPC UA nodes to ensure that the number of OPC UA nodes to export is less than the maximum limit allowed. |
|
500 |
ROMA.00111035 |
{0} OPC UA nodes to be imported, which exceeds the upper limit {1}. |
{0} OPC UA nodes to be imported, which exceeds the upper limit {1}. |
Reduce the number of OPC UA nodes to ensure that the number of OPC UA nodes to import is less than the maximum limit allowed. |
|
500 |
ROMA.00111036 |
The imported OPC UA node file is empty. Select a valid file. |
The imported OPC UA node file is empty. Select a valid file. |
Select a valid file. |
|
500 |
ROMA.00111038 |
The total number of node paths exceeds the quota. Ensure that the total number of imported nodes and existing nodes under the same OPC UA connection point is less than the quota. |
The total number of node paths exceeds the quota. Ensure that the total number of imported nodes and existing nodes under the same OPC UA connection point is less than the quota. |
Reduce the number of nodes to import or contact the administrator to increase the quota. |
|
500 |
ROMA.00111039 |
The topic {0} used for command delivery does not meet the "%s/in/%s" rule. |
The topic {0} used for command delivery does not meet the "%s/in/%s" rule. |
Check whether the topic used for command delivery meets the rules. |
|
500 |
ROMA.00111040 |
The attribute value of the device shadow is invalid. Check the parameter and try again. |
The attribute value of the device shadow is invalid. Check the parameter and try again. |
Check whether the entered attribute value of the device shadow is valid. |
|
500 |
ROMA.00111041 |
The exported device data is empty. Export at least one device data record. |
The exported device data is empty. Export at least one device data record. |
Select at least one device to export. |
|
500 |
ROMA.00111042 |
The number of exported devices cannot exceed the upper limit {0}. |
The number of exported devices cannot exceed the upper limit {0}. |
Reduce the number of devices to export and try again. |
|
500 |
ROMA.00111043 |
The customized topic {0} already exists. Change the topic name and try again. |
The customized topic {0} already exists. Change the topic name and try again. |
Use another topic name and try again. |
|
500 |
ROMA.00111044 |
Devices using the Modbus or OPC UA protocol cannot be added as subdevices. |
Devices using the Modbus or OPC UA protocol cannot be added as subdevices. |
Select a device that uses another protocol. |
|
500 |
ROMA.00111045 |
Subdevice registration does not support products using the Modbus or OPC UA protocol. |
Subdevice registration does not support products using the Modbus or OPC UA protocol. |
Use another protocol when registering a subdevice. |
|
500 |
ROMA.00111046 |
Connection point {0} can be created only for common devices. Check the device type. |
Connection point {0} can be created only for common devices. Check the device type. |
Check whether the device is a common device. If not, change the device type. |
|
500 |
ROMA.00111047 |
All the devices to be imported already exist or the devices do not have corresponding products. |
All the devices to be imported already exist or the devices do not have corresponding products. |
Check whether all devices exist. Check whether the corresponding product exists for the devices. |
|
500 |
ROMA.00111048 |
The number of imported devices exceeds the upper limit {0}. |
The number of imported devices exceeds the upper limit {0}. |
Reduce the number of devices in the file based on the maximum number of devices that can be imported. |
|
500 |
ROMA.00111049 |
The imported field does not match the title. Import correct data based on the title {0}. |
The imported field does not match the title. Import correct data based on the title {0}. |
Import correct data based on the title fields. |
|
500 |
ROMA.00111050 |
The device name {0} already exists in the product {1}. |
The device name {0} already exists in the product {1}. |
Use another device name. |
|
500 |
ROMA.00111051 |
The device {0} does not exist. Check the parameters and try again. |
The device {0} does not exist. Check the parameters and try again. |
Register a new device or replace the device with another one. |
|
500 |
ROMA.00111052 |
Invalid topic permission. Change the permission to pub or sub and try again. |
Invalid topic permission. Change the permission to pub or sub and try again. |
Change the topic permission and try again. |
|
500 |
ROMA.00111053 |
The device topic {0} does not exist. Check the parameters and try again. |
The device topic {0} does not exist. Check the parameters and try again. |
Check whether the topic exists. |
|
500 |
ROMA.00111054 |
The device password cannot be empty. Check information of the device ID {0}. |
The device password cannot be empty. Check information of the device ID {0}. |
Check whether the device password in the file is empty. |
|
500 |
ROMA.00111055 |
Incorrect Enable field. Enter 0 (indicating that the device is enabled) or 1 (indicating that the device is disabled). |
Incorrect Enable field. Enter 0 (indicating that the device is enabled) or 1 (indicating that the device is disabled). |
Check whether the Enable field of the device in the file is correct. |
|
500 |
ROMA.00111056 |
The topic_perm field cannot be empty when devices with customized topics are exported. Log in to the database and check the device whose client ID is {0}. |
The topic_perm field cannot be empty when devices with customized topics are exported. Log in to the database and check the device whose client ID is {0}. |
Based on the clientId field, check whether the topic_perm field of the custom topic corresponding to the device is empty. If the field is empty, change the value to pub or sub and export the topic again. |
|
500 |
ROMA.00111301 |
The group name {0} already exists. Change the name and try again. |
The group name {0} already exists. Change the name and try again. |
Use another name and try again. |
|
500 |
ROMA.00111302 |
The current group is associated with devices and cannot be deleted. Delete the devices first. |
The current group is associated with devices and cannot be deleted. Delete the devices first. |
Delete the devices associated with the group and try again. |
|
500 |
ROMA.00111303 |
The parent group {0} does not exist. Change the parent group and try again. |
The parent group {0} does not exist. Change the parent group and try again. |
Change the parent group and try again. |
|
500 |
ROMA.00111304 |
The group supports a maximum of five levels. Create subgroups under other groups. |
The group supports a maximum of five levels. Create subgroups under other groups. |
Change the parent group and try again. |
|
500 |
ROMA.00111601 |
The rule name {0} already exists. Change the rule name and try again. |
The rule name {0} already exists. Change the rule name and try again. |
Use another rule name and try again. |
|
500 |
ROMA.00111602 |
The product at the source does not exist. Select an existing product and try again. |
The product at the source does not exist. Select an existing product and try again. |
Select an existing product and try again. |
|
500 |
ROMA.00111603 |
The device at the source does not exist. Select an existing device and try again. |
The device at the source does not exist. Select an existing device and try again. |
Select an existing device and try again. |
|
500 |
ROMA.00111605 |
Invalid data parsing parameter. If data parsing is enabled, the query field cannot be left blank. If data parsing is disabled, the query field and search criteria must be left blank. |
Invalid data parsing parameter. If data parsing is enabled, the query field cannot be left blank. If data parsing is disabled, the query field and search criteria must be left blank. |
Check whether the rule data parsing parameter is valid. |
|
500 |
ROMA.00111606 |
If the destination type is KAFKA or ROMA_MQS and supports SSL connections, the value of mqs_sasl_ssl must be true and the username and password cannot be left empty. |
If the destination type is KAFKA or ROMA_MQS and supports SSL connections, the value of mqs_sasl_ssl must be true and the username and password cannot be left empty. |
Ensure that the username and password are not empty when the value of mqs_sasl_ssl is true. |
|
500 |
ROMA.00111607 |
The topic {0} of the destination KAFKA or ROMA_MQS does not meet the rule. Enter 3 to 200 characters, including only digits, letters, underscores (_), and hyphens (-). |
The topic {0} of the destination KAFKA or ROMA_MQS does not meet the rule. Enter 3 to 200 characters, including only digits, letters, underscores (_), and hyphens (-). |
Check whether the topic meets the rules and modify it if necessary. |
|
500 |
ROMA.00111608 |
The connection address {0} of the destination does not meet the rule. Enter 10 to 200 characters, including digits, colons (:), periods (.), and commas (,). |
The connection address {0} of the destination does not meet the rule. Enter 10 to 200 characters, including digits, colons (:), periods (.), and commas (,). |
Check whether the connection address meets the rules. |
|
500 |
ROMA.00111609 |
The application ID of the device is inconsistent with that of the rule. Enter a correct application ID. |
The application ID of the device is inconsistent with that of the rule. Enter a correct application ID. |
Enter the correct application ID of the device. |
|
500 |
ROMA.00111610 |
If the destination type is KAFKA or ROMA_MQS, the destination_type, app_id, server and topic fields must be specified. |
If the destination type is KAFKA or ROMA_MQS, the destination_type, app_id, server and topic fields must be specified. |
Check the parameters and try again. |
|
500 |
ROMA.00111611 |
Failed to connect to the destination {0}. Check whether the connection information is correct or whether the destination address is reachable. |
Failed to connect to the destination {0}. Check whether the connection information is correct or whether the destination address is reachable. |
Check whether the connection information is correct or whether the destination address is reachable. The username and password correspond to the appKey and appSecret of the application to which the topic belongs, respectively. |
|
500 |
ROMA.00111612 |
The device-level topic {0} at the source does not meet the "/v1/devices/device ID/datas" or "product serial number/out/device ID" rule. |
The device-level topic {0} at the source does not meet the "/v1/devices/device ID/datas" or "product serial number/out/device ID" rule. |
Check whether the topic meets the rules and try again. |
|
500 |
ROMA.00111613 |
The product-level topic {0} at the source does not meet the "/v1/products/product serial number/datas" or "product serial number/out/+" rule. |
The product-level topic {0} at the source does not meet the "/v1/products/product serial number/datas" or "product serial number/out/+" rule. |
Check whether the topic meets the rules and try again. |
|
500 |
ROMA.00111614 |
The topic {0} at the source already exists. Check the topic and try again. |
The topic {0} at the source already exists. Check the topic and try again. |
Change the name and try again. |
|
500 |
ROMA.00111615 |
If the destination type is DEVICE, multiple destinations can be added. If not, only one destination can be added. Check the destination type and try again. |
If the destination type is DEVICE, multiple destinations can be added. If not, only one destination can be added. Check the destination type and try again. |
Check the destination type and modify the number of records added to the destination. |
|
500 |
ROMA.00111616 |
Failed to obtain the data source from FDI. Check whether the data source name and application name are correct and whether FDI is normal. |
Failed to obtain the data source from FDI. Check whether the data source name and application name are correct and whether FDI is normal. |
Check whether the data source name and application name are correct. Check whether the FDI service is normal. |
|
500 |
ROMA.00111617 |
Failed to parse the application SQL. Enter the correct SQL field and try again. |
Failed to parse the application SQL. Enter the correct SQL field and try again. |
Enter the correct SQL field or SQL condition and try again. |
|
500 |
ROMA.00111618 |
If the destination KAFKA or ROMA_MQS does not support SSL connections, the value of mqs_sasl_ssl must be false (default value), and the username and password must be left blank. |
If the destination KAFKA or ROMA_MQS does not support SSL connections, the value of mqs_sasl_ssl must be false (default value), and the username and password must be left blank. |
Check the parameters when the destination is Kafka or ROMA_MQS and try again. |
|
500 |
ROMA.00111619 |
If the destination type is MQS, the destination_type, app_id, server, token, and topic fields must be specified. |
If the destination type is MQS, the destination_type, app_id, server, token, and topic fields must be specified. |
Check whether the parameters meet the requirements as prompted. |
|
500 |
ROMA.00111620 |
If the destination type is DEVICE, the destination_type, server, token, topic, and tag fields must be specified. |
If the destination type is DEVICE, the destination_type, server, token, topic, and tag fields must be specified. |
Check whether the parameters meet the requirements as prompted. |
|
500 |
ROMA.00111621 |
If the destination type is DIS, the destination_type, tag, and topic fields must be specified. |
If the destination type is DIS, the destination_type, tag, and topic fields must be specified. |
Check whether the parameters meet the requirements as prompted. |
|
500 |
ROMA.00111622 |
The connection address {0} of the destination does not meet the rule. Enter 10 to 200 characters, consisting only digits, colons (:), periods (.), and semicolons (;). |
The connection address {0} of the destination does not meet the rule. Enter 10 to 200 characters, consisting only digits, colons (:), periods (.), and semicolons (;). |
Check and correct the connection address of the destination. |
|
500 |
ROMA.00111623 |
The Topic Level parameter at the source of the rule is invalid. If the device name is specified, Topic Level must be Device-level. If the device name is not specified, Topic Level must be Product-level. |
The Topic Level parameter at the source of the rule is invalid. If the device name is specified, Topic Level must be Device-level. If the device name is not specified, Topic Level must be Product-level. |
Check the rule level parameter and try again. |
|
500 |
ROMA.00111624 |
The Topic Name parameter at the source of the rule is invalid. If the device name is specified, Topic Name must be specified. If the device name is left blank, Topic Name can be left blank. |
The Topic Name parameter at the source of the rule is invalid. If the device name is specified, Topic Name must be specified. If the device name is left blank, Topic Name can be left blank. |
Check whether the topic parameter is valid and try again. |
|
500 |
ROMA.00111625 |
The application ID {0} is inconsistent with the ID of the application to which the rule {1} belongs. Check the rule name and application ID and try again. |
The application ID {0} is inconsistent with the ID of the application to which the rule {1} belongs. Check the rule name and application ID and try again. |
Check whether the application ID to which the rule name belongs is the same as the application ID in the request. If they are different, change the application ID or rule name in the request. |
|
500 |
ROMA.00111626 |
The application ID is empty. When the rule does not exist, the application ID must be specified. |
The application ID is empty. When the rule does not exist, the application ID must be specified. |
Check whether the rule exists in the system. If the rule does not exist, enter the correct application ID in the request. |
|
500 |
ROMA.00111627 |
The application ID of the product is inconsistent with that of the rule. Enter a correct application ID. |
The application ID of the product is inconsistent with that of the rule. Enter a correct application ID. |
Enter the correct application ID of the product. |
|
500 |
ROMA.00111637 |
The current data plane instance version: {0} does not support this destination data source type: {1}, if you need to use this function, please upgrade the data plane to version 1.8.0 or higher. |
The data source type cannot be set to the destination in the current version. |
If this function is required, upgrade the data plane instance to a later version to support this function. |
|
500 |
ROMA.00111901 |
The destination configuration of the subscription type already exists in the current application. Cancel the enabled destination configuration and try again. |
The destination configuration of the subscription type already exists in the current application. Cancel the enabled destination configuration and try again. |
Cancel the enabled configuration of the destination and try again. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
