If you have defined a SAS libref of USER in your autoexec file for the SAS Workspace Server, you could receive the following error when you attempt to build a SAS OLAP cube in either SAS^® OLAP Cube Studio or SAS^® Data Integration Studio.

Unable to execute query: SQL passthru expression
contained these errors: ERROR: File
WORK.SASVER.DATA does not exist.

If you enable detailed logging to the workspace server, you will see the following error in the workspace server log:

1 data sasver;
2 ver= "&sysvlong";
3 run;
NOTE: The data set USER.SASVER has 1 observations and 1 variables.
NOTE: DATA statement used (Total process time):
real time 0.03 seconds
cpu time 0.03 seconds

ERROR: File WORK.SASVER.DATA does not exist.

Table WORK.SASVER is used internally to verify the SAS version of the workspace server. However, if a library of USER is assigned, SAS will reference all one-level table names as USER.table_name instead of WORK.table_name.

You can circumvent this problem in the following ways.

• Use SAS OLAP Cube Studio and its Cube Designer wizard to define OLAP cube structures and metadata only, but do not build the cubes from within OLAP Cube Studio. Once the metadata for the cube has been defined via the Cube Designer wizard, you can save out the short form of the PROC OLAP code and use SAS Enterprise Guilde or a batch SAS program to create the OLAP cube.
• Use a libref other than USER for your SAS data library defined in the autoexec file for your SAS Workspace Server.
• Within your autoexec file, route one-level table references back to WORK using the USER= option, as shown in the following code snippet:

  libname user 'c:\userlib';
  options user=work;
  

  Note: Using this method will prevent you from having a permanent location defined for one-level SAS table names.

For further information on the USER= SAS option for controlling the location of one-level table names, see SAS System Libraries.

Operating System and Release Information