Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

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 will 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.

This error can occur when the launch credentials for the pooled workspace server (used by default starting in version 4.2) cannot be used to assign the library. 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.

As a workaround, you can take one of the following actions:

• You can give the pooled workspace server launch credentials the same permissions that you have given to individual users who need to access the data. For example, you might need to add an account for sassrv on the database server.

• You can change the library definition so that it is not preassigned.

• 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 Launch Credentials.

• You can convert to a standard workspace server so that the LIBNAME statement is submitted using the credentials of the logged in user. 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 into 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 on SASApp - Pooled Workspace Server and select Properties.
4. Click the Options tab. The credentials appear in the Multiuser credentials box. These are the credentials that you might add, for example, to the 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 Choices in Workspace Server Pooling.

Operating System and Release Information