PC 재부팅 한 후에 라이선스 연결이 끊어지는 문제가 발생했습니다.
라이선스 연결은 Orchestrator 연결 방식으로 하고있는데 다시 연결할 때는 해당 버튼이 비활성화 된 채로 연결을 할 수가 없었습니다.
Orchestrator에 연결 버튼이 비활성화 되는 문제는 어떤 상황에서 발생하는지 알 수 있을까요?
This behavior is usually the result of the way the Robot is configured and how it handles its orchestration connection over restarts. In many cases, the “Connect to Orchestrator” button is only enabled when the robot isn’t already “configured” to connect automatically. For example:
• Automatic Connection Mode:
If the Robot is set up to connect using a machine key or configured through Orchestrator settings (especially in unattended scenarios), then after a PC reboot the Robot might still “remember” these settings even though the license validation failed. Because the connection details have been pre‐populated, UiPath disables the manual “Connect” button to avoid accidental mismatches.
• Stale or Cached Settings:
Sometimes after a reboot, the local Robot service can have cached or “stuck” state information. That is, it believes it’s still connected (or in the process of connecting) to an Orchestrator instance—even if the license isn’t being properly claimed. In this situation, the UI will show the connection as “not connected” but disable the Connect button so that it isn’t possible to restart the connection process manually until the state is cleared.
• License/Activation Anomalies:
If a robot loses its license connection (perhaps due to a transient issue with the Orchestrator or the network after a reboot), the underlying license management system might prevent changes until the situation is remedied. In such cases, you may have to either restart the robot service or “quit” the connection entirely (for example, via a “Quit” or “Disconnect” option) before you can attempt a reconnection.
What to Do:
- Verify that the Robot service is running normally, and check if restarting the Robot service (or even the whole machine) helps clear any stale connection state.
- If you’re using the machine key method (where the connection information is stored in configuration files), ensure that your Orchestrator URL and machine key are correct and that the Orchestrator instance is reachable.
- Sometimes signing out of UiPath Assistant and then signing back in can force the reloading of configuration and re-enable the connection button.
The key point is that a disabled “Connect to Orchestrator” button is often an indication that the robot is in a state where the connection parameters are being maintained (or waiting for license validation) even though the actual connection (or license retrieval) has failed. This design prevents the user from inadvertently altering the configuration in an unsupported state.
If these troubleshooting steps don’t help resolve the issue, you might check the UiPath logs for more insight or consider submitting a support ticket with UiPath, as there may be a deeper configuration or service issue at play.
LLM helped me to write this but it’s validated by me ↩︎
Hi @jhkang
라이센스가 비활성화되었거나, 머신이 등록되지 않았거나, 네트워크 문제로 인해 비활성화될 수 있습니다. Orchestrator URL과 머신 키가 올바른지 확인하고, 로봇 서비스가 실행 중인지 점검하며, 사용자가 적절한 권한을 가지고 있는지 확인하세요.
도움이 되셨다면, 해결책으로 표시해 주세요.
행복한 자동화 되세요.
one thing might be you might already be signed in..first you need to hit signout and then connect would be enabled back
cheers