Did anyone got this warning in the Log Before? "The platform id 4 specified as a paramter to Connect doesn't match the platform id 3 of the host"

This error is filling the Log, it occurred  6700 times and I don't know what could be the reason

Parents
  • There is a mismatch in the information in the PlatformNodes registry key. This is uncommon, but here are some possible causes:

    • An orphaned node that is currently up and running, disrupting platform-to-platform communications.
    • A problem with global data cache distribution that prevented PlatformNodes from being synchronized across all nodes in the galaxy.
    • DNS/network issues that caused the machine name to get resolved to an incorrect IP address.
    • Other issues.

    Here are some steps you can perform to narrow down the issue:

    1. On the node where the warning is logged (Node A), launch regedit and navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ArchestrA\Framework\Platform\PlatformNodes\Platform4, and get the “Machine” value. It contains the name/address of platform 4 (Node B).
    2. Ping the address of the target machine and see what IP address it resolves to. Is the IP address what you expect? If not, check your DNS/network. If yes, continue with next steps.
    3. Go to the machine identified in the previous steps (Node B).
    4. Determine if you expect to have a platform running on this node. If yes, continue with the next steps.
    5. On Node B, launch regedit and navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ArchestrA\Framework\Platform\PlatformNodes\Platform0 and check the Id entry. Based on the warning message, it should show 3.
    6. Go to your Galaxy repository machine. Launch OCMC -> Platform Manager. Find the platform with “Node Name” equal to “Node B“. What is the “Platform ID” for that entry? Is it 3 or 4? If the “Platform ID” is 4, then redeploy “Node B”. If the "Platform ID" is 3, redeploy “Node A”.
Reply
  • There is a mismatch in the information in the PlatformNodes registry key. This is uncommon, but here are some possible causes:

    • An orphaned node that is currently up and running, disrupting platform-to-platform communications.
    • A problem with global data cache distribution that prevented PlatformNodes from being synchronized across all nodes in the galaxy.
    • DNS/network issues that caused the machine name to get resolved to an incorrect IP address.
    • Other issues.

    Here are some steps you can perform to narrow down the issue:

    1. On the node where the warning is logged (Node A), launch regedit and navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ArchestrA\Framework\Platform\PlatformNodes\Platform4, and get the “Machine” value. It contains the name/address of platform 4 (Node B).
    2. Ping the address of the target machine and see what IP address it resolves to. Is the IP address what you expect? If not, check your DNS/network. If yes, continue with next steps.
    3. Go to the machine identified in the previous steps (Node B).
    4. Determine if you expect to have a platform running on this node. If yes, continue with the next steps.
    5. On Node B, launch regedit and navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ArchestrA\Framework\Platform\PlatformNodes\Platform0 and check the Id entry. Based on the warning message, it should show 3.
    6. Go to your Galaxy repository machine. Launch OCMC -> Platform Manager. Find the platform with “Node Name” equal to “Node B“. What is the “Platform ID” for that entry? Is it 3 or 4? If the “Platform ID” is 4, then redeploy “Node B”. If the "Platform ID" is 3, redeploy “Node A”.
Children
No Data