When you try to open a diagram within a SAS Enterprise Miner project, you might encounter the following error:

EMWS# is the diagram ID.  EM_name can be one of the following:

EM_NODEID
EM_HISTORY
EM_DIAGRAMEDIT
EM_DGRAPH

There are multiple potential causes of this error. This SAS note addresses some of the common causes and documents the steps to diagnose and resolve the error.

Steps to diagnose and resolve the error

1. Confirm the presence and accessibility of, and permissions on, the data set:

Make sure that the data set that is referenced by the error (“EM_name”) actually exists on the file system where the SAS Enterprise Miner project is saved. The data set should exist under the project directory/Workspaces/EMWS# directory. If the data set does exist, then try opening it outside of SAS Enterprise Miner to confirm that you can open it successfully.  Examples: use SAS Enterprise Guide or SAS Display Manager.

If the data set does not exist or, if it is inaccessible outside of SAS Enterprise Miner, then there is a good possibility that the data set is corrupted. One solution (often the quickest) is to create a new Enterprise Miner diagram.  Another solution is to restore the entire project directory from the last-working file-system backup.  Work with your system administrator to restore. Make sure that the backup that you restore has a valid copy of the data set.

If the data set exists and it is accessible outside of SAS Enterprise Miner, then check whether you have Read and Write access to the data set.  If you want to eliminate permission-related problems, then work with your system administrator to grant full access to the entire project directory recursively.  Recursive access grants you access to the project directory, subdirectories, and files.

2. Check whether the “Encoding” and “Data Representation” properties of the diagram match the encoding and operating system/bitness (32-bit versus 64-bit) of your SAS Application Server (compute server):

This error can occur when there is a mismatch between the Encoding and/or Data Representation properties of the diagram, and the corresponding attributes of your SAS Application Server.  You can check the properties of the diagram on its Property pane when you select the diagram.  Example: the following screenshot shows a diagram named “test” that has “wlatin 1” encoding and “Windows_64” (64-bit Windows) operating system/bitness:

Similarly, you can run the following code in the Program Editor window within your SAS Enterprise Miner session to check the encoding value for your workspace-server session.  View the log that is generated by the code:

The project was most likely created on a SAS (source) system with different encoding/operating system/bitness if either of the following are true:

• The encoding value that is returned by the code does not match the “Encoding” property of the diagram.

• The “Data Representation” property of the diagram does not match the bitness /operating system of your SAS Application Server.

In that case, you need to correctly migrate the project from the source system to the current SAS system using the Enterprise Miner Migrate Project macro. The macro prepares the project on the source system and restores the project to a usable form on the current SAS system.

If the error persists after following those steps, then contact SAS Technical Support.  Provide the following information:

• The SAS Enterprise Miner release. 
• The operating system and bitness of your SAS Application Server.
• A screenshot of the entire SAS Enterprise Miner window when the error occurs.  Include the diagram’s Property panel and the error message.
• Screenshots that show the presence, accessibility, and permissions, on/of the data set that is referenced by the error from Step 1.
• The complete log that is generated by the PROC OPTIONS code from Step 2.

Tips to avoid diagram-corruption problems:

One of the common causes of diagram corruption is low disk space on the file system when diagrams are in use.   Routinely delete diagrams or projects that are no longer needed to create disk space.  Consider creating model packages for important diagrams by following SAS KB0036530: "Creating a model package (SPK file) in SAS® Enterprise Miner(tm)".  You can later re-create any needed diagrams from model packages. Follow SAS KB0036529: "Using SAS® Enterprise Miner(tm) model package SPK files to view results and logs, and to re-create diagrams for further analysis" if needed.   

Operating System and Release Information