Under certain circumstances, running the Update Host Name Reference task from SAS Deployment Manager causes the system to fail. The issue occurs when either SAS^® Visual Process Orchestration or SAS^® Federation Server is already deployed in the environment in which SAS Deployment Manager is running. During any subsequent updates, the system might fail in these or other SAS Deployment Manager tasks.

Click the Hot Fix tab in this note to access the hot fix for this issue.

After you apply the hot fix, no action is required if you have not already run the Update Host Name Reference task. If you have either SAS Visual Process Orchestration or SAS Federation Server deployed and have run the Update Host Name Reference task in the past, then you need to apply the hot fix and run the Update Host Name Reference task again. 

Important: Provide both the same short name and fully qualified domain name that you supplied during the previous execution of the Update Host Name Reference task.

The update host name task does not change all occurrences of the old host name(s) to new host name(s) for some Data Management Server components. However, the task does not fail. After running the update host name task, SAS Visual Process Orchestration might fail to start. Likewise, when applying maintenance or an update, SAS Federation Server might fail to start. The associated hot fix prevents this problem for subsequent update host name tasks, and it prevents future failures when maintenance is applied.

The associated hot fix, does not, however, correct the problem on systems where the Update Host Name Reference task has already been run. If your servers are failing to start immediately after running the Update Host Name Reference task, navigate to the dmserver.log file that resides in the SASHome/DataFluxDataManagementServer/2.6/dmserver/var/server_logs/ folder and search for the old host name. If you find references to the old host name, then your system is affected by this issue. To resolve the problem, you can apply this hot fix and run the task again or you can fix the problem manually by completing the steps below:

For SAS Visual Process Orchestration Runtime Server:

1. Back up and modify the app.cfg configuration file in the SASHOME/SASVisualProcessOrchestrationServer/2.1/poserver/etc folder and replace the host name with the correct target host name in the following directive:
   base/auth_server_loc = iom://old-host-name:8561
2. Back up and modify the dmserver.cfg configuration file in the SASHOME/SASVisualProcessOrchestrationServer/2.1/poserver/etc folder and replace the source host name with the correct target host name in the following directive:
   dmserver/name = Process Orchestration Runtime Server – old-host-name

For SAS Federation Server:

To resolve this problem for SAS Federation Server, see SAS Note 60586: "SAS^® Data Management Server fails to start during an update."

Operating System and Release Information

A fix for this issue for SAS Federation Server Configuration 4.1_M1 is available at:

A fix for this issue for SAS Visual Process Orchestration Server Configuration 2.1 is available at: