Overview

There are multiple reasons why you might not be able to view a SAS OLAP cube. This SAS KB article is a guide to diagnosing the cause of your particular problem.

For example, review this note if the message View Cube results are not available occurs in SAS^® OLAP Cube Studio 4.2 or later. Another common error is Metadata error - The specified metadata repository or schema does not define any cubes.

Each section includes information about where to look and which items you should investigate.

Check for problems at the operating system level

• Verify that the cube files exist in the directory specified by the PATH option in the PROC OLAP code or in the Cube Designer wizard in SAS OLAP Cube Studio.
  
  
• Verify that the OLAP Server process ID contains read and execute permissions to the directory and the files that make up the cube by navigating to the directory specified by the PATH option in the PROC OLAP code or in the Cube Designer wizard in SAS OLAP Cube Studio. To do this, log on to your operating system environment using the same account that you used to start the SAS OLAP Server.
  
  • • On UNIX operating systems, the account is usually the installation account.
    • On Windows operating systems, the Windows service is normally the LocalSystem or System account.
      
      
• Verify that the SAS Trusted User account is being used to connect from the SAS OLAP Server to the SAS^® Metadata Server. The SAS OLAP Server log should contain a line similar to the following at or near the beginning of a newly started server:

New out call client connection (1) from sastrust.

• Verify that the SAS OLAP Server was started after the SAS^® Metadata Server had completed its own start-up routine.

• Verify that there are no errors in either the OLAP server log or the metadata server log that indicate a problem.

Review critical settings using SAS^® Management Console

• Verify that the OLAP schema is assigned to the application server.

1. 1. Expand Server Manager.
   2. Locate the application server (blue disk icon).
   3. Right-click the application server and select Properties.
   4. Click the OLAP Schema tab.
   5. Make sure the selected schema is correct.
   6. Click OK to save any changes that were made.
   7. Restart the OLAP server if any changes were saved.

Note: You can also do this verification in the SAS OLAP Cube Studio by completing the following steps. Right-click the OLAP Schema in the metadata folder ► click the Server Assignment tab. Make sure that the schema is correctly associated with the application server.

• Verify that the OLAP Schema is correctly associated to the application server. In some cases, the application server can lose its association with the SAS OLAP Schema even though the schema appears to be correctly assigned. In order to reassociate the schema to the application server, complete the following steps:

1. 1. Expand Server Manager.
   2. Locate the application server (blue disk icon).
   3. Right-click the application server and select Properties.
   4. Click the OLAP Schema tab.
   5. Click the New button.
   6. Supply a name (any string).
   7. Click Next ► Finish.
   8. Click OK.
   9. Restart your SAS OLAP Server process.
   10. Repeat steps 1 through 4.
   11. Select the original OLAP Schema from the drop-down list
   12. Click OK.
   13. Restart your SAS OLAP Server process.
   14. Delete the temporary OLAP Schema by using either SAS OLAP Cube Studio, SAS^® Data Integration Studio, or PROC METADATA code.
       
       

• Verify that the ID of the user who is attempting to view the cube has Read and ReadMetadata granted to the OLAP cube and ReadMetadata granted to the application server and the OLAP Schema.

1. Expand Authorization Manager.
2. Expand Resource Management.
3. Expand By Location.
4. Verify the permissions for the application sever: 
5. Right-click the application server (blue disk) and select Properties.
6. Click the Authorization tab and verify the user's permissions.
7. Expand the application server.
8. Verify the permissions for the OLAP Schema (see step 4).
9. Expand the OLAP Schema.
10. Verify the permissions for the OLAP cubes (see step 4).
    
    

• Verify that the Read and ReadMetadata permissions are not denied on any of the components that make up the cube. For example, a user can have problems viewing a cube if the user is denied ReadMetadata on the directory object.

1. Expand Authorization Manager.
2. Expand Resource Management.
3. Expand By Type.
4. Locate the object type that you want to examine.
   1. Right-click the object and select Properties.
   2. Click the Authorization tab and verify the user's permissions.

Execute a query on the cube to see more descriptive errors

Using either an interactive Base SAS^® session or SAS^® Enterprise Guide^®, submit the following PROC SQL passthru to capture a more descriptive error. Replace the macro values in the code below with the correct information for your environment.

        /* The machine name or IP address for the OLAP server */
       %let host=server.domain.com;
       /* The port number for the OLAP server */
       %let port=5451;
       /* A User ID with access to the cube */
       %let user=sasdemo;
       /* The User's password */
       %let pass=sasdemo1;
       /* The OLAP cube name */
       %let cube=Example;

       proc sql;
         connect to olap (host="&host" port=&port
                          user="&user" pass="&pass");
         select * from connection to olap (
           select [Measures].defaultmember on columns from [&cube]
         );
         disconnect from olap;
       quit;

Errors that contain Access Denied or User does not have privileges typically indicate a problem at the operating system level.

Errors that contain the word permission usually indicate that the problem is due to metadata permissions.

If the error indicates that the repository or schema does not contain cubes, see the next section.

Check for duplicate OLAP schemas

In SAS 9.1.3 Service Pack 3 and earlier, it is possible to create multiple schemas that have the same name. This will cause the OLAP server to lose the reference to the cube object. You can remove duplicate schemas in SAS OLAP Cube Studio if the schema is empty. To empty a schema, recreate the cubes in that schema using the Edit Cube Structure option in the context menu of the cube. Make sure to change the schema name before completing the wizard.

Check for problems with the shell script or config file

• If the -METAREPOSITORY option has not been specified in the OLAP server's configuration, the server will be unable to locate the schema or cubes. The preferred location for this option is the sasv9.cfg file located in the home directory of the application server. For example, the directory might be Lev1\SASMain or Lev1\SASApp. The option can also be specified directly in the OLAP Server's configuration file or shell script if necessary.

• Make sure that the -METASERVER option is pointing to the correct SAS Metadata Server.