In SAS Web Report Studio, when attempting to view a report, the objects in the report might be missing, and you might see error details similar to the following.

[a12768071117920.282713169742006_0_0] Error Rendering the Report

ERROR: Libname xxxxx is not assigned.
	at com.sas.iquery.execution.instructions.SASSubmitHandler.execute(SASSubmitHandler.java:207)
	at com.sas.iquery.execution.instructions.AbstractSASSubmitInstruction.submitLanguageInstructions(AbstractSASSubmitInstruction.java:109)
	at com.sas.iquery.execution.instructions.AbstractSASSubmitInstruction.execute(AbstractSASSubmitInstruction.java:44)
	at com.sas.iquery.execution.instructions.SASSubmitInstruction.execute(SASSubmitInstruction.java:87)
.........

Note that the library error appears for the first object in the report that cannot be rendered. Error details for additional objects might contain content such as the following:

Root Cause:   java.lang.NullPointerException
	at com.sas.report.render.optimizer.models.ChildQueryBuilder.createQuery(ChildQueryBuilder.java:507)
	at com.sas.report.render.optimizer.SectionOptimizer.retrieveChildQuery(SectionOptimizer.java:303)
	at com.sas.report.render.optimizer.SectionOptimizer.getChildQuery(SectionOptimizer.java:357)
	at com.sas.report.render.optimizer.Optimizer.getChildQuery(Optimizer.java:139)

Note: If the error includes garbage characters such as ÿÿÿÿh¡ú in the LIBNAME statement, then see SAS Note 14862.

Note: These errors can occur in SAS Web Report Studio even though you can successfully submit the LIBNAME statement in SAS^® Enterprise Guide^®.

What causes the issue

This problem can occur when the launch credentials for the pooled workspace server (used by default beginning with release 4.2) cannot be used to assign the library because the account does not have the appropriate permissions, either operating system permissions or metadata permissions. Typically, sassrv (the login for the SAS General Servers group) is the account that is used to launch the server. To determine which account is used at your site, see How to verify the pooled workspace server launch credentials.

Resolving the issue

The first step is to verify that the SASUSERS metadata group is granted ReadMetadata access to the library. Any group with a login, such as SAS General Servers, is a member of SASUSERS, so denying ReadMetadata permission to SASUSERS causes the LIBNAME error.

If metadata permissions for SASUSERS are not the issue, then one of the following actions should resolve the issue:

• You can give the pooled workspace server launch credentials the same operating system permissions that you have given to individual users who need to access the data. The correct resolution is specific to your site. However, one way to accomplish this is to examine the settings for an account that has the required access, and then edit the pooled workspace server account to match those settings. For example, if the account that you are using as an example gains access through membership in a group in the operating system, then add the pooled workspace server account to the same operating system group. As part of the solution, you might need to create the pooled workspace server account (for example, sassrv) on the database server.

• You can change the library definition so that it is not pre-assigned.

• You can change the launch credentials for the pooled workspace server to a user who can successfully submit the LIBNAME statement. The new credentials must meet the requirements in "Criteria for a Designated Launch Credential" in the SAS Intelligence Platform: Security Administration Guide. You can find a link to the guide on the SAS^® Intelligence Platform Product Documentation page. Click the tab for your release of SAS^®, and then look under "Administration Documentation."

• You can convert to a standard workspace server so that the LIBNAME statement is submitted using the credentials of the logged in user. The user must still have all of the necessary metadata permissions on the library such as ReadMetadata, as well as operating system permissions. This option will negatively impact performance. For information about switching to a standard workspace server, see SAS Note 37422.

How to verify the pooled workspace server launch credentials

To determine which credentials are being used for the pooled workspace server, perform these steps:

Note: SASApp is the default server context name. Your server context might have a different name.

1. Log on to SAS^® Management Console with an account that has permission to access the Server Manager plug-in.
2. Navigate to Server Manager ► SASApp ► SASApp - Logical Pooled Workspace Server ► SASApp - Pooled Workspace Server.
3. Right-click SASApp - Pooled Workspace Server and select Properties.
4. Click the Options tab. The credentials appear in the Multiuser credentials box. For example, these are the credentials that you might add to an Oracle user group in your operating system.

CAUTION: If you decide to change the credentials for the pooled workspace server, then you must restart your object spawner for the change to take effect.

For more information about benefits and risks of using pooled workspace servers, see the topic "Choices in Workspace Server Pooling" in the SAS Intelligence Platform: Security Administration Guide. You can find a link to the guide on the SAS^® Intelligence Platform Product Documentation page. Click the tab for your release of SAS^®, and then look under "Administration Documentation."

Testing access to the library

To test access to the library, submit the LIBNAME statement for the pre-assigned library in SAS Enterprise Guide using the pooled workspace server credentials. For example, your LIBNAME statement might look like this:

Submit the LIBNAME statement on the same server context that is used by SAS Web Report Studio. For example, submit the statement on SASApp.

You can copy the LIBNAME statement from SAS Management Console by temporarily deselecting the Library is Pre-Assigned option, and then selecting Display LIBNAME statement. After you copy the statement, restore the option. If the copied statement includes a USER and PASSWORD, replace them with the pooled workspace server credentials.

Operating System and Release Information