3490365 - Unable to log on: Could not connect to server XXX. Please check that the server name is correct, and that the server is running. - SAP Data Services 4.x

• Cluster system.
• Issue during the system migration
• Virtual hostnames point to the old servers before the migration, and then the same virtual hostnames point to the new servers after the migration, then they point back to the old server names after the new server shutting down.
• In Server manager, Repository Manager, CMC repository configuration, use the virtual host name as the server name.
• In the old system, the job schedules are no longer working with the below errors. Manually executing the jobs works however.
• Error in al_rwjoblauncher.log when schedule jobs run on the old server:
  (14.2.14.3744) 05_21_2024 04:04:05 (14904):     *** RWJL_EXIT called.
  (14.2.14.3744) 05_21_2024 04:04:05 (14904):     *** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220)
  (14.2.14.3744) 05_21_2024 04:04:05 (14124):     Unable to log on: Could not connect to server <new CMS server name>.  Please check that the server name is correct, and that the server is running.
   
  (14.2.14.3744) 05_21_2024 04:04:05 (14124):     *** RWJL_EXIT called.
  (14.2.14.3744) 05_21_2024 04:04:05 (14124):     *** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220)
• With the virtual hostname, the Al_rwjoblauncher looks for the new CMS server name by mistake.
• Nslookup command shows that the virtual host name correctly points to the 4.2 servers
• The schedule jobs run successfully if changing the user running the task in Windows task scheduler from SYSTEM to <ADMIN_USER>
• Using SYSTEM user to ping the virtual host name returns the correct old server IP address.

SAP Data Services 4.x

Data Services, registry, server name, virtual hostname, al_rwjoblauncher , KBA , EIM-DS-DEP , Deployment, Installation, Upgrade , Problem