Installation Note 54229: Application virtualization issues that might occur with SAS® Software streamed packages
 |  |  |  |
Below are issues known to occur with application virtualization packages for SAS Software that use products such as Microsoft App-V and VMware ThinApp. This note is intended for the qualified sequence engineer who is performing the sequencing and creating packages.
Microsoft App-V
Issue: The 'sas.iomprovider.1' provider is not registered on the local machine.
The 'sas.iomprovider.1' provider error message is known to occur with a SAS® Enterprise Guide® package.
To correct this issue, do the following:
- If the local SAS installation is not virtualized, install it on the sequencer machine.
- On the client machine, install the local SAS installation in the same location as on the sequencer machine.
Issue: Stored processes and tasks do not display results.
After you have packaged the SAS® Add-In for Microsoft Office, and an end user at the client machine attempts to run stored processes or tasks, the stored processes or tasks do not run.
Explanation: During sequencing, if an AMOOptions.xml file is placed in the SAS Add-In for Microsoft Office installation directory, the resulting package has a hardcoded path to the location in which the results are stored. A user's stored processes or tasks cannot access the results path because the location is based on the location of the sequence engineer's AppData folder.
Sample Screenshots
Here are sample screenshots of the Hello World stored process and a Describe List Data task.
Hello World
No results are shown for Hello World:
Describe List Data task
The task seems to run, but no content is displayed. This message appears:
Resolution: Do not place an AMOOptions.xml and AMOOptionsRecovery.xml in the SAS Add-In for Microsoft Office installation directory on the sequence machine. If the two files exist in the SAS Add-In for Microsoft Office installation directory, remove them during sequencing to build and complete the package.
If a customized AMOOptions.xml file is mandatory, the workaround is to remove the contents of PathToResultsFiles string in the AMOOptions.xml file. Here are examples:
Before: <PathToResultsFiles>C:\Users\user\Documents\My SAS Files</PathToResultsFiles>
After:<PathToResultsFiles></PathToResultsFiles>
Once the end user accesses the streamed application, the PathToResultsFiles string is populated per that user's specific location for the results to write to.
VMware ThinApp
Currently, there are no reported issues to address.
Additional Information
- Paper: Tips and Techniques for Deploying SAS® in an Application Virtualization Environment
- Virtualization support policy: SAS® Product Support for Virtualization Environments.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | N/A | Microsoft Windows 8 Enterprise 32-bit | ||
| Microsoft Windows 8 Enterprise x64 | ||||
| Microsoft Windows 8 Pro 32-bit | ||||
| Microsoft Windows 8 Pro x64 | ||||
| Microsoft Windows 8.1 Enterprise 32-bit | ||||
| Microsoft Windows 8.1 Enterprise x64 | ||||
| Microsoft Windows 8.1 Pro | ||||
| Microsoft Windows 8.1 Pro 32-bit | ||||
| Windows 7 Enterprise 32 bit | ||||
| Windows 7 Enterprise x64 | ||||
| Windows 7 Professional 32 bit | ||||
| Windows 7 Professional x64 | ||||
| Windows 7 Ultimate 32 bit | ||||
| Windows 7 Ultimate x64 | ||||
| Type: | Installation Note |
| Priority: | medium |
| Date Modified: | 2014-12-21 20:52:13 |
| Date Created: | 2014-09-30 08:44:32 |