Skip to main content
Question

Unable to Connect to my Cloud Control Room

  • September 25, 2025
  • 5 replies
  • 55 views

Forum|alt.badge.img+1

Hi, 
I am using a enterprise edition of A360. Recently I am facing issue with connecting with my local device. when ever I try to connect to the cloud Control room, after I clicking on “connect to the local device” I am getting a error popping up “An Unexpected Problem Occurred”. I have Uninstalled and re installed the Bot agent as well and tried to restart the Automation Services. Still it yielded no results. For reference refer to the attachments.
 

5 replies

Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • September 25, 2025

Hi ​@MahiCharan Reddy,

 

Kindly check the below article and see if it can help in your case.

 

A360 | Error while registering device - An unexpected problem occurred


Forum|alt.badge.img+1

Hi ​@Padmakumar . It seems I dont have access to the site you have metioned. could  you please elaborate the solution.
Thanks,

 


Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • September 25, 2025

Hi ​@Padmakumar . It seems I dont have access to the site you have metioned. could  you please elaborate the solution.
Thanks,

 

Here is the soft copy of it FYR.

 

 


Forum|alt.badge.img+1

Hi ​@Padmakumar ,

Thanks for the reply. As you have suggested I have tried the solutions mentions in the Article but nothing worked. But i was able to retrieve the logs from Node_Manager_Log file. Please refer to the screen shot of the logs for reference and suggest of there is any other route to resolve this issue.

Thanks.
 

 


Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • September 26, 2025

Hi ​@Padmakumar ,

Thanks for the reply. As you have suggested I have tried the solutions mentions in the Article but nothing worked. But i was able to retrieve the logs from Node_Manager_Log file. Please refer to the screen shot of the logs for reference and suggest of there is any other route to resolve this issue.

Thanks.
 

 

Nothing evident on this other than the already mentioned error. If none of the fixes worked, I would recommend raising a support ticket on this.