You would need to re-install the agent on the new server and then re-name it. Please implement the steps and share the outcome.
I tried to re-install the agent and it is giving same error.
Please verify the Kb on how to re-register the Agent:
Did anyone figure out how to fix this? I'm having the same issue after the Windows server that ran the agent was replaced. This has been extraordinarily frustrating to find a solution. Everything I try just gives me the same error yet I don't find anywhere in the cloud console that references this name.
I hadn't tried that kb article before. I followed its instructions and get the same error.
When I look at my runtime environments, sm-et is not there.
I've tried manually adding a new sm-et environment thinking the agent would link to it and that didn't work either. sm-et must exist somewhere and I just can't see it??
Can we use alternate name? Does that help?
If not then we need to follow up with support ticket to resolve the issue.