Orchestrator doesn't see runtime machine (Error #1002)

Help Orchestrator
,
1

Hello,
I need help with my orchestrator. I can’t switch license to other machine, because when I try to do that I’m getting this error: “Invalid machine name (#1002)”. It’s strange because I can’t enable license, but if it is enabled, I can’t disable it for the same reason.
Tried to remove machine and create a new one, but results are the same, first time it connects, but if i try to disable it, I’m getting this error.

2

@GOFERIS_Edgaras

Are you getting this error on assistant?

Cheers

3

Yes, on assistant also. But assistant sometimes drops different error code like #1913 and some other that I don’t remember.
My colleague just suggested me, that the problem can be with windows updates, because problem started at October 9th and affected only VM’s that had this update.
Well… the windows update thing was not the right answer, there still a problem after updates rollback :confused:

1 Like
4

I tried restart VM, reinstall UiPath Studio, create new machines, but nothing helps :frowning:

5

@GOFERIS_Edgaras ,

Try below steps:

1. Check Machine Name Formatting:

  • Ensure that the machine name you are using matches exactly with the name registered in UiPath Orchestrator. This includes checking for any extra spaces or irregular characters. You can verify your machine name by typing hostname in the command prompt on the machine.

2. Unregister the Machine:

  • Go to the UiPath Orchestrator and navigate to the Machines section. Try to unregister the machine that is giving you issues. If it’s still appearing, you can try to clear your machine from the Orchestrator interface.
  • If it doesn’t allow you to unregister, you may need to reach out to your Orchestrator administrator for assistance with clearing it.

3. Creating a New Machine:

  • After deregistering the current machine, create a new machine in the Orchestrator by providing a valid and matching machine name. Ensure the new setup adheres to any naming conventions established in your organization.

4. Reinstall UiPath Robot:

  • On the local machine, try uninstalling and then reinstalling the UiPath Robot. During installation, ensure that you specify the correct machine name to match what is in Orchestrator.
  • After reinstalling, ensure that you configure and connect to the Orchestrator properly again.

5. Check Machine Key:

  • Verify that you are using the correct Machine Key when trying to connect to Orchestrator. This key is specific to each machine and is required to authenticate and connect successfully.

6. Orchestrator Version:

  • Make sure you are using a compatible version of UiPath Studio and Robot that corresponds to the Orchestrator version. Compatibility issues might lead to connection problems or invalid machine notifications.

7. UiPath License:

  • If your UiPath license is tied to a specific machine, and you are trying to switch it, ensure that it is not within a locked state or reaching its limit for activation. Check with UiPath support if there are license restrictions that you should be aware of.

8. Firewall/Network Issues:

  • Ensure that there are no firewall or network restrictions that might be blocking communication between your machine and the Orchestrator.

9. Checking for Duplicate Machines:

  • Sometimes, duplicate machine entries can exist that can lead to confusion. Check if you have any duplicate entries in the Orchestrator and remove the one that is causing the issue.
6

Hello,
I’m sorry that i didn’t reply earlier. Checked and tried all of suggestions and there was no difference, still the same problem.
But after few hours I wanted to show to my colleague what’s happening and all of a sudden everything just started working like nothing happened. I don’t even know what was the root cause of this. Magic? :smiley:
There were no change in out system or network.

7

@GOFERIS_Edgaras ,you can mark as a solution if you found useful.

8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.