Troubleshooting SAS Web Applications

The following table lists some SAS Web application errors and what to do to resolve them.

Troubleshooting the SAS Web Applications
Error	Explanation	Resolution
SAS Web Report Studio or the SAS Information Delivery Portal displays a “Cannot find server” error.	Either your servlet container or Web application server is not running. There is problem with the URL that you are using to start the application.	Make sure that your servlet container or Web application server is running. If it is not running, start it. This will probably solve the problem. If the server is already running, the problem could be with the URL that you are using to start the Web application. Use the correct URL: `http://`host-name`:`port-number`/`application-name. Make sure that the host name is the fully qualified name of the host on which your servlet container or Web application server is running. Make sure that the port number identifies the port on which the server is listening. For the JBoss Application Server, this will normally be port 8080. Finally, make sure that the application name in the URL matches the actual name of the Web application (including case).
Each time your Web application requests a new page, there is a long delay.	When a Java Server Page (JSP) is requested for the first time, you can expect a significant delay. When all of your JSPs have been converted to compiled servlets, the problem will be resolved.	Tune your servlet container or Web application server. For example, if you are using the WebLogic Server, the server might be checking (on a per application basis) for updated JSPs and updated compiled servlets. You can suppress these checks by setting an application's JSPPageCheck and ServletReloadCheck properties to -1. See your server vendor's documentation for similar tips.
The SAS Information Delivery Portal displays a “Could not authenticate user” error.	The user is not registered in the metadata repository. On Windows, if the user that is trying to log on is registered in the metadata, but the user name is not domain qualified, the user will not be able to log on.	In SAS Management Console, add a login to the Person object that contains at least a user name. On Windows, make sure the user name has the form host\user-ID or domain\user-ID. For more information, see About User Administration in SAS Intelligence Platform: Security Administration Guide.
SAS stored processes run from the SAS Add-In for Microsoft Office, but do not run from the SAS Information Delivery Portal.	The SAS Services Application might not be running.	Start the following in this order: WebDAV Server, SAS Services Application, and your servlet container or Web application server. For more information, see Operating Your Servers in SAS Intelligence Platform: System Administration Guide.
You are unable to start the SAS Services Application.	Another application might be using the same port as the SAS Services Application (by default, 5091).	Configure the SAS Services Application to listen on a different port.
You receive a server error when accessing the Help menu from a SAS Web application.	SAS Help Viewer Metadata Configuration is not configured.	Rerun the SAS Deployment Wizard to install and configure SAS Help Viewer Metadata Configuration. For more information, see Install and Configure SAS Interactively.
An error page appears when you access the Help menu from a SAS application or the Help menu item for a SAS application does not display.	The online Help for the SAS application was not installed or the SAS Help Viewer Metadata Configuration Web application was not rebuilt after the online Help was installed.	Verify that the online Help was installed. If not, install it using the SAS Deployment Wizard. Once the Help is installed, rebuild the SAS Help Viewer Metadata Configuration Web application using the SAS Deployment Manager and redeploy the SAS Help Viewer Metadata Configuration EAR. For more information, see Install and Configure SAS Interactively and Rebuilding the SAS Web Applications in SAS Intelligence Platform: Middle-Tier Administration Guide.
The SAS Deployment Wizard displays a message similar to the following: Configuration Update Failure The update was not successful for one or more products in the following configuration directory: /myconfig/Lev1 Would you like to retry the update for this configuration directory?	The deployment wizard is running in update mode, and after the installations are updated, the wizard iterates over all the configuration directories to run the deployment manager to update each one. If you encounter an error or if you cancel an update before it completes, the deployment wizard displays this failure message.	Stop the SAS Application Servers (for example, the object spawner) and the Web application servers (JBoss) before clicking Retry. Clicking Retry reconfigures all products, not just the one that failed. (Metadata does not need to be restored to a pre-configuration backup to succeed.)