The SAS Visual Analytics SDK is a collection of JavaScript libraries that web developers can use to embed SAS Visual Analytics content within custom ​web pages and web apps. This guide will help you start troubleshooting issues, as well as understand what information to provide to SAS Technical Support if you need assistance. Here are the sections:

• SAS Viya Setup
• Known Issues
• Logs and Files to Collect
  
  

SAS Viya Setup

Most issues with the SAS Visual Analytics SDK occur because the SAS^® Viya^® environment has not been set up properly. The SAS Visual Analytics SDK does not work with SAS Viya using the default configuration. It is important to ensure that the configuration settings for the sas.commons.web.security.cookies, sas.commons.web.security.cors, and sas.commons.web.security.csrf definitions are all set correctly to allow proper communication from the SAS Visual Analytics SDK to the SAS Viya Server. The instructions on how to configure these definitions can be found in SAS Viya Setup.

Known Issues

This section describes errors that you might encounter and their causes.

Unable to log on to the server


This message can occur for a variety of reasons:

• You access secure content (HTTPS) from a non-secure (HTTP) source.
• You access the SAS Visual Analytics SDK page from the local file system (for example, from the C drive on a Windows client) and not from a web server. The SAS Visual Analytics SDK page must be hosted on a web server. 
• You did not correctly set the allowedOrigins property in the sas.commons.web.security.cors definition or you did not restart the services after changing this property.
• You did not correctly set the sameSite property in the sas.commons.web.security.cookies definition. You should set it to None and restart the services.
   

An unexpected service error was encountered while attempting to fulfill the request


This message can occur if you did not correctly set the allowedOrigins property in the sas.commons.web.security.cors definition or you did not restart the services after changing this property.

 

​​​​​Cannot access the requested resource on the server. Contact your SAS administrator.


This message can occur if you did not correctly set the allowedUris property in the sas.commons.web.security.csrf definition or you did not restart the services after changing this property.

Report does not render

If no errors are observed and the report does not appear to render, the content divisions or containers within the HTML page could be overriding the height of the SAS Visual Analytics report object, causing it to be too small to appear. To work around this issue, add the height style to the SAS Visual Analytics SDK tag. Here is an example:

<sas-report
  authenticationType="guest"
  url="http://my-viya-server.com"
  reportUri="/reports/reports/c3c6befb-3981-4c9e-b011-7dc11dec5e37"
  style="height:1000px;"
></sas-report>
 

Logs and Files to Collect

If you encounter issues and need assistance from SAS Technical Support, collect the following information:

• If possible, the web page that you have created that includes the SAS Visual Analytics SDK code
• Network trace and console logging from the web browser's developer tools. For more information, see SAS Note 60268, "Using the web browser developer tools to investigate issues in SAS^® Web Applications."
• Screenshots of the following settings in SAS^® Environment Manager:
  • The allowedOrigins property in the sas.commons.web.security.cors definition
  • The sameSite property in the sas.commons.web.security.cookies definition
  • The allowedUris property in the sas.commons.web.security.csrf definition