This issue is caused by the encryption used for the ASM API password.
When first installing the ASM Agent, you are prompted for the API password. When the agent is first started, this password is encrypted using current server information for the server the agent resides on. So, if your API password on the original server was "12345", the password might encrypt as "xinVIja7nc". However this same password when used on a second server might return an encrypted value of "1oooo8EK09".
All ASM Agent versions on supported platforms.