SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 44038: "The library for the environment is not assigned" message occurs when trying to open a risk environment in SAS® Risk Dimensions®

DetailsHotfixAboutRate It

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:

The library for the environment selected is not assigned. Would you like to assign the library reference to the environment path?
When you click on Yes, the following message appears:
The environment entered does not exist. Please check the name and retry your action - or select an environment from those listed.

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.

  1. Truncated environment name
  2. Improper deletion of 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 ToolsDelete 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:

  1. 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).
  2. 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).
  3. 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.
  4. Delete the environment (MyLib.MyEnv) by selecting ToolsDelete Environment ► select the risk environment (MyLib.MyEnv) ► OK.
  5. 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 FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Risk Dimensions Enterprise EditionMicrosoft® Windows® for x645.3_M15.49.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Datacenter Edition5.3_M15.49.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Enterprise Edition5.3_M15.49.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Standard Edition5.3_M15.49.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 for x645.3_M15.49.2 TS2M39.3 TS1M0
Microsoft Windows Server 20085.3_M15.49.2 TS2M39.3 TS1M0
Microsoft Windows Server 2008 for x645.3_M15.49.2 TS2M39.3 TS1M0
Microsoft Windows XP Professional5.3_M15.49.2 TS2M39.3 TS1M0
Windows 7 Enterprise 32 bit5.3_M15.49.2 TS2M39.3 TS1M0
Windows 7 Enterprise x645.3_M15.49.2 TS2M39.3 TS1M0
Windows 7 Home Premium 32 bit5.3_M15.49.2 TS2M39.3 TS1M0
Windows 7 Home Premium x645.3_M15.49.2 TS2M39.3 TS1M0
Windows 7 Professional 32 bit5.3_M15.49.2 TS2M39.3 TS1M0
Windows 7 Professional x645.3_M15.49.2 TS2M39.3 TS1M0
Windows 7 Ultimate 32 bit5.3_M15.49.2 TS2M39.3 TS1M0
Windows 7 Ultimate x645.3_M15.49.2 TS2M39.3 TS1M0
Windows Vista5.3_M15.49.2 TS2M39.3 TS1M0
Windows Vista for x645.3_M15.49.2 TS2M39.3 TS1M0
64-bit Enabled AIX5.3_M15.49.2 TS2M39.3 TS1M0
64-bit Enabled HP-UX5.3_M15.49.2 TS2M39.3 TS1M0
64-bit Enabled Solaris5.3_M15.49.2 TS2M39.3 TS1M0
HP-UX IPF5.3_M15.49.2 TS2M39.3 TS1M0
Linux5.3_M15.49.2 TS2M39.3 TS1M0
Linux for x645.3_M15.49.2 TS2M39.3 TS1M0
Solaris for x645.3_M15.49.2 TS2M39.3 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.