If you used a symbolic link to set up a nondefault location for SAS Viya configuration files, the process of updating, upgrading, or adding software to modify SAS Viya software fails. The installation terminates, and you see the Microsoft Windows Installer function Msiexec error code 1622, as shown here:

Problem

This problem happens because the symbolic link that you created is removed during an installation step for an update or upgrade. Because the symbolic link is removed, the Windows Installer cannot write the MSI log to the SAS Viya configuration folder %ProgramData%\SAS\Viya\var\log\install, which does not exist.

The deployment of SAS Viya for Windows is supported to use %ProgramFiles%\SAS\Viya as the default folder for installation and %ProgramData%\SAS\Viya as the default folder for configuration files. You should not try to deploy the software to use nondefault folders or use a symbolic link to specify a nondefault location for SAS Viya installation or configuration files.

At one time, the SAS^® Viya^® 3.4 for Windows: Deployment Guide documented instructions for using a symbolic link to specify a nondefault location for SAS Viya configuration files. However, those instructions were later removed because of problems identified with updating and upgrading SAS Viya if a symbolic link had been used. The instructions that are provided here should be used as a workaround if you used a symbolic link to set up a nondefault location for SAS Viya configuration files when you installed SAS Viya 3.4 and you now need to update or upgrade SAS Viya software.  

Workaround

The workaround is to use a new command-line option to specify a different folder for installation logs. Packages can then install and update without errors. After the installation step is finished, the symbolic link is removed and a non-symbolic-linked SAS directory is created in the %ProgramData% folder. Copy the new files and folders in the %ProgramData%\SAS folder to the target location that you had specified when you created the symbolic link. You then must re-create the symbolic link and run Setup.bat again to configure the software. 

Before you begin the steps within this SAS Note, you must first review the section  Managing Your Software in the SAS^® Viya^® 3.4 for Windows: Deployment Guide. In this section, there are subsections that describe how to update SAS Viya, how to add software to modify SAS Viya, and how to upgrade SAS Viya. Review the subsection regarding the action that you need to take. Perform the steps here to complete the software modification or updates:

1. Check to see whether you need to download files to perform this workaround. Run the command setup.bat -installLogDir from the directory that you use to store the SAS deployment scripts. This directory is typically C:\sas\install\powershell-deployment. If the command returns the message “A parameter cannot be found that matches parameter name'installLogDir',” you need to replace three deployment script files with the files that are provided by SAS Technical Support. Otherwise, if you do not receive that error message, you can skip this step.

   Back up these three files:

   deploy.ps1                                        (located in C:\sas\install\powershelldeployment\)
   remove.ps1                                      (located in C:\sas\install\powershelldeployment\)
   SasDeploymentController.psm1      (located in C:\sas\install\powershelldeployment\library\SasDeploymentController\)
   
   Contact SAS Technical Support to obtain new copies of these files. Save the new files in the locations shown in the list above.

2. Create a folder for the installation logs. Any user who runs Setup.bat must have Read and Write access to the folder.
3. Stop all SAS Viya services. For more information, see Start and Stop All Servers and Services in SAS^® Viya^® 3.4 Administration.
4. Run the command provided for your deployment scenario. 
   
   If you are adding to or updating SAS Viya, run this command:
      setup.bat -update -installLogDir "path-to-installation-log-folder"
   
   If updates are available, you will be prompted to download and install the updates. Enter yes. Any available updates and newly added products are then downloaded and installed.
   
   If you are upgrading SAS Viya, run this command:
      setup.bat -install -installLogDir "path-to-installation-log-folder"
   
   Any available upgrades are then downloaded and installed.
5. At the end of the process, Setup.bat either exits to the command prompt or generates a prompt to reboot the machine to complete the installation. If you are prompted to do so, reboot the machine. 
6. Copy only the new files in the physical C:\ProgramData\SAS folder to the target of the symbolic link. Note: Copy only the new files so that you do not overwrite any user-modified files. Use the command provided here to complete this step:
      robocopy "%ProgramData%\SAS" "alternate-config-location" /E /XN /XO /V
7. Rename the non-symbolic-linked %ProgramData%\SAS folder to %ProgramData%\SAS.bak in case there is any content needed for reference.
8. Re-create the symbolic link with this command:
      mklink /D "%ProgramData%\SAS" "alternate-config-location"
9. Run the following command to configure the updated, new, or upgraded software:
      setup.bat -config
10. Return to the appropriate subsection in Managing Your Software. Complete any remaining steps. 

Operating System and Release Information