When you use the Import Data dialog box from SAS^® Visual Data Builder or SAS^® Visual Analytics Designer in order to load data to the SAS^® LASR™ Analytic Server, you might see the following error: 

This error can occur when SAS Visual Analytics fails to connect to the pooled workspace server to retrieve the list of importers. In most cases, the error message includes a Details button. The additional information clearly indicates that SAS Visual Analytics failed to connect to the pooled workspace server. However, when you encounter the issue described in this SAS Note, then the error message does not have a Details button. In addition, the object spawner log does not show any attempt to connect to the pooled workspace server. 

You can encounter this problem if you used custom context root names when you interactively deployed SAS Visual Analytics. For example, you specified to use VDB instead of the default SASVisualDataBuilder. 

Click the Hot Fix tab in this note to access the hot fix for this issue.

Next Steps If You Are Not Using Custom Context Names

The issue in this SAS Note applies specifically to sites that are using custom context root names for SAS Visual Analytics. If you are not using custom context root names, then you first need to verify the following: 

• If the error occurs only when you are using SAS Visual Analytics Designer 7.5, and you see the additional error "The application was unable to retrieve the list of capabilities" when you click Close in the message, then you are encountering a different issue. See SAS Note 67544,"SAS Visual Analytics Designer fails to import data because the list of importers and capabilities cannot be retrieved." 
• Your object spawner is listening.
• Your software license is up to date. 
• The user who sees the message is in a role with self-serve import capabilities. 

If you cannot resolve the issue, then contact SAS Technical Support for assistance. 

Operating System and Release Information

A fix for this issue for SAS Visual Analytics 7.51 is available at:

A fix for this issue for SAS Visual Analytics 7.5 is available at: