Problem Note 44038: "The library for the environment is not assigned" message occurs when trying to open a risk environment in SAS® Risk Dimensions®
 |  |  |  |  |
In the Initial Risk Environment window in the SAS Risk Dimensions GUI, the following message might appear when you attempt to open a risk environment from the Existing environment list:
There are two known causes for this behavior. In each case, a discrepancy exists between the metadata entry and the physical file system information for a risk environment.
Truncated Environment Name
This problem occurs when the metadata entry for the environment name does not match the actual environment name. A common occurrence is with risk environments that are created in SAS® Risk Management for Insurance or SAS® Risk Management for Banking. In some cases, the names for those environments are truncated when they are registered in the metadata repository. This results in a mismatch with the actual environment name.As a workaround, instead of opening the risk environment from the initial Existing environment list, use the New Library button to define a library for the risk environment that you want to access. Next, open the risk environment by selecting the newly defined library from the environment list.
Click the Hot Fix tab in this note to access the hot fix for this issue. The hot fix is for SAS Risk Dimensions 5.3_M1.
Improper Deletion of Risk Environment
This error message also occurs if you manually delete the SAS library in which the risk environment is stored. The SAS Risk Dimensions GUI reads risk environment information from the metadata repository. When you manually delete a SAS library from the physical file system, only the physical directory is deleted. The metadata entry still exists.The workaround is to re-create the SAS library and the risk environment by using the same names. Then properly delete the risk environment by using Tools ► Delete Environment in the SAS Risk Dimensions GUI or by using the DELETE statement in PROC RISK.
For example, suppose the error occurs for the MyLib.MyEnv risk environment in the C:\temp folder. Use the following instructions to re-create and then properly delete the environment:
- Ensure that the directory (C:\temp) exists for the risk environment that is to be deleted (MyEnv). If it does not exist, then create an empty directory to that path (that is, create C:\temp).
- In the SAS Risk Dimensions GUI, create a new environment that has the same library name (MyLib), path (C:\temp), and risk environment name (MyEnv) that was previously used for the risk environment. You might need to use the New Library button to create the library (MyLib).
- Open a different environment, or otherwise restart the SAS Risk Dimensions GUI without opening a risk environment. You cannot delete the environment that you currently have open.
- Delete the environment (MyLib.MyEnv) by selecting Tools ► Delete Environment ► select the risk environment (MyLib.MyEnv) ► OK.
- The environment (MyLib.MyEnv) should no longer exist metadata repository. If you do not want the empty directory that you just created (C:\temp), then delete it.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Risk Dimensions Enterprise Edition | Microsoft® Windows® for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Standard Edition | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2008 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2008 for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Microsoft Windows XP Professional | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Windows 7 Enterprise 32 bit | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Windows 7 Enterprise x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Windows 7 Home Premium 32 bit | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Windows 7 Home Premium x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Windows 7 Professional 32 bit | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Windows 7 Professional x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Windows 7 Ultimate 32 bit | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Windows 7 Ultimate x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Windows Vista | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Windows Vista for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| 64-bit Enabled AIX | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| 64-bit Enabled HP-UX | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| 64-bit Enabled Solaris | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| HP-UX IPF | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Linux | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Linux for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
| Solaris for x64 | 5.3_M1 | 5.4 | 9.2 TS2M3 | 9.3 TS1M0 | ||
A fix for this issue for SAS Risk Dimensions Server Component 5.3_M1 is available at:
http://ftp.sas.com/techsup/download/hotfix/HF2/F03.html#44038A fix for this issue for Risk Dimensions 5.3_M1 is available at:
http://ftp.sas.com/techsup/download/hotfix/HF2/F04.html#44038A fix for this issue for SAS Risk Management for Insurance 2.1_M1 is available at:
http://ftp.sas.com/techsup/download/hotfix/HF2/F90.html#44038| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2012-02-20 15:30:19 |
| Date Created: | 2011-08-17 22:50:28 |