After you apply Hot Fix P7F029 to Base SAS (SAS 9.4M9) on Windows, Base SAS can fail during startup when SAS is invoked by opening a SAS-associated file type from Windows Explorer. This issue can affect all file types associated with SAS (such as .sas, .sas7bcat, and .sas7bdat).

This issue can occur after you apply hot fixes that included P7F029, or after you install Base SAS using a SAS software order that contains P7F029.

When this issue occurs, errors similar to the following might occur in the Base SAS log:

ERROR: UNABLE TO ACCESS MESSAGE 359.1
ERROR: UNABLE TO ACCESS MESSAGE 531.1
ERROR: Critical YP Subsystem error opening message library.
ERROR: Module áoÝ  not found in search paths.
ERROR: Module áoÝ  not found in search paths.

Workaround

Complete the following steps to confirm whether this issue applies to your installation and, if necessary, resolve it.

1. Confirm whether Hot Fix P7F029 is installed.
   Generate a ViewRegistry report and review the report for P7F029. See SAS KB0036131, "Using the ViewRegistry Report and other methods to determine the software releases and hot fixes that are installed" for additional information. 
   • If P7F029 is listed in the report, continue to step 2.
   • If P7F029 is not listed in the report, contact SAS Technical Support.
     
     
2. Update the SAS Software Depot for future installations.
   Run the Retrieve Hot Fixes task in SAS^® Deployment Wizard. This task downloads the latest hot fixes to the SAS Software Depot so that future installations using that depot are not affected. See Applying Security Updates and Hot Fixes for additional information.
   
   
3. Apply Hot Fix P7F030 to the affected installation.
   Download Hot Fix P7F030 and apply it by running the Apply Hot Fixes task in SAS Deployment Manager. See Apply Hot Fixes for additional information.