Skip to content

Warning and Error Messages

Message Type (Warning/Error) Detailed Reason Troubleshooting
Timed Out. Please check your configuration Alt text If valid certificate and key are uploaded, with correct configuration details are entered in edit pop up wrong scope id and clicked on provision.
Alt text		 Please provide correct scope id and configuration details and click provision.
Timed Out. Please check your configuration and make sure your device is enrolled. Alt text If “Create Individual Enrollment” is selected "No" and provisioning fails, then the error message is displayed.
Alt text		 Device needs to be enrolled at the Azure portal before provisioning.
Provision failed Alt text When an incorrect/invalid certificate is uploaded, then the error message is displayed.
Alt text		 Correct/valid certificate needs to be uploaded.
The certificate is not a valid base64 string value Alt text When an incorrect encoding of certificate is used for provisioning.
Alt text		 Correct encoded certificate to be used.
Provisioning service “CloudConnectorDPS” does not gave authorization rule. Alt text When an incorrect certificate and “DPS Connection String” used.
Alt text		 Correct certificate and DPS connection string value to be used
Invalid connection string. Alt text - If valid certificate and key are uploaded, with correct configuration details are entered in “Edit Client Configuration” dialog box and invalid "DPS Connection String" and click provision.
- If invalid certificate and key are uploaded, with correct configuration details are entered in “Edit Client Configuration” dialog box and invalid "DPS connection String" and click provision.
Alt text		 User correct DPS connection string value.
Disconnected Alt text If only certificate and key are uploaded without any configuration details in “Edit Client Configuration” dialog box up and without deploy. Enter all the missing details in provision and configure tabs and click deploy.
Enter all the missing details in provision and configure tabs and click deploy. Alt text If only certificate and key are uploaded without any configuration details in “Edit Client Configuration” dialog box and with deploy. Enter all the missing details in provision and configure tabs and click deploy.
The Registration ID does not match the common name of the certificates. Please give the same name used for generating certificates. Alt text If valid certificate and key are uploaded, with correct configuration details are entered in“Edit Client Configuration” dialog box wrong "Registration ID" and clicked on provision. Enter valid "Registration ID" and it should be same as common name provided while creating the certificate
Error registering device: NotConnectedError: rhea: connection disconnected Error while connecting with Azure portal. Please check your proxy details or device certificate and key. Alt text If valid certificate and key are uploaded, with correct configuration details are entered in “Edit Client Configuration” dialog box wrong "Global Device Endpoint" and click provision. Enter correct "Global Device Endpoint" and click provision.
The Registration ID does not match the common name of the certificates. Please give the same name used for generating certificates. Alt text If right configuration details are entered in “Edit Client Configuration” standard tab but invalid certificate and key are uploaded in advanced tab. Enter valid certificates, where "Registration ID" matches the common name which is used while creating the certificate
Error registering device: Error: error: 0909006C:PEM routines: get_name:no start line Alt text If right configuration details are entered in “Edit Client Configuration” standard tab with correct certificate but wrong key are uploaded in advanced tab. Enter the valid key.
The Registration ID does not match the common name of the certificates. Please give the same name used for generating certificates. Alt text If right configuration details are entered in “Edit Client Configuration” standard tab with correct key but invalid certificate are uploaded in advanced tab. Enter valid certificates, where "Registration ID" matches the common name which is used while creating the certificate
The Registration ID does not match the common name of the certificates. Please give the same name used for generating certificates. Alt text If invalid certificate and correct key are uploaded in “Add Client” dialog box and added correct details in “Edit Client Configuration” dialog box and click on provision Enter valid certificates, where "Registration ID" matches the common name which is used while creating the certificate
Error registering device:Error: error: 0B080074:x509 certificate routines: X509_check_private_ key:key values mismatch Alt text If valid certificate and wrong key are uploaded in “Add Client” dialog box and added correct details in “Edit Client Configuration” dialog box and click on provision Enter the valid key.
Error registering device: NotConnectedError: rhea: connection disconnected Error while connecting with Azure portal. Please check your proxy details or device certificate and key Alt text Enter correct details in “Edit Client Configuration” standard tab, wrong proxy host and port in advanced tab Enter correct proxy host and port.
Error registering device: NotConnectedError: rhea: connection disconnected Error while connecting with Azure portal. Please check your proxy details or device certificate and key Alt text Enter correct details in “Edit Client Configuration” standard tab, correct proxy port but wrong proxy host in advanced tab Enter correct proxy host.
Error registering device: NotConnectedError: rhea: connection disconnected Error while connecting with Azure portal. Please check your proxy details or device certificate and key Alt text Enter correct details in “Edit Client Configuration” standard tab, correct proxy host but wrong proxy port in advanced tab Enter correct proxy port.
Operation: Connection failed. error is : Connection refused Alt text Enter correct details in “Edit Client Configuration” standard tab and advanced tab but add proxy and remove http 8883 port in IEM and IED and click deploy
Alt text		 Add http 8883 port in IEM and IED
Operation: Connection failed. error is : Connection refused Alt text Operation: Connection failed. error is : Connection refused Add http 8883 port in IED
Operation: Connection failed. error is : Connection refused Alt text Enter correct details in “Edit Client Configuration” standard tab and advanced tab but add proxy and http/https 8883 port in IEM and remove port in IED and deploy Add http/https 8883 port in IED
Operation: Connection failed. error is : Connection refused Alt text Enter correct details in“Edit Client Configuration” standard tab and advanced tab but remove all proxy in IEM and IED and deploy Add proxy in IEM and IED
Disconnected, Error Code from Broker : 5, Error message : The connection was refused. Alt text If correct data entered in standard and advanced tab deploy(client connected), now go to Azure portal and delete device. No retry policy available for Azure client if the device is deleted from the Azure portal.
Error registering device: CA certificate not found. Error while connecting with Azure portal. Please check your proxy details or device certificate and key Alt text If correct data entered in standard and advanced tab deploy( client connected), then in Azure portal and delete enrollment(ex: ashadps). Now navigate in UI to “Edit Client Configuration” > select No for "Individual enrollment" and click on provision. Device needs to be enrolled at the Azure portal before provisioning.
No error displayed(getting loading icon) Alt text If invalid certificate authority is uploaded instead of Baltimore and deployed Upload the valid Baltimore certificate.
Registration ID is already configured for another client. Alt text If you try to configure a new client in same UI with the same certificate details and click on provision. Use a new valid certificate to create new client.