When you upgrade an existing SAS 9.4 environment or you install a new SAS 9.4 environment, you might receive an error message in SAS^® Deployment Wizard during the Update Content or Load Content steps. 

For SAS 9.4M6, Rev. 940_20w26 and later, the error is as shown below: 

For releases earlier than SAS 9.4M6, Rev. 940_ 20w26, the error is as follows: 

The following sections explain the source of this problem and offer suggested troubleshooting steps. 

Problem Source

This failure can occur during the Load Content or Update Content steps if there is an issue in creating a connection to certain SAS^® web applications (for example, SAS^® Content Server and SAS^® Web Infrastructure Platform client access). The root cause for this failure can result from a variety of issues, including, but not limited to, the following:

• SAS^® 9.4 Web Server does not run or it fails to start properly. Potential reasons for these issues includes the following (although there might be other reasons as well): 
  • an issue with the Transport Layer Security (TLS) configuration for SAS Web Server
  • incorrect reverse-proxy configuration for SAS Web Server 
• SAS^® Web Application Server (SASServer1_1) does not run, fails to start, or it fails to start properly. Potential reasons for these issues might include the following (although there might be other reasons as well): 
  • a dependency for the SAS Web Application Server (the cache locator, SAS Web Infrastructure Platform Data Server, and so on) does not run or does not function properly.
  • a dependency for the SAS Web Application Server (for example, the cache locator) runs, but it does not accept connections from SASServer1_1.
  • a configuration issue with SAS Web Application Server. For example, external reverse-proxy configuration settings or Integrated Windows Authentication configuration settings are not preserved properly in the SASServer1_1 server.xml file after an update.
  • a necessary certificate is not loaded properly into the SAS Security Certificate Framework.
• A system resource issue occurs (for example, a lack of sufficient RAM or disk space) that impacts the middle-tier services (SAS Web Application Server, the cache locator, and so on), potentially leaving them unable to respond to requests.
• Incorrect internal or external connection properties are defined for SAS web applications in SAS^® Management Console. 

Troubleshooting Tips

If you experience the error that is described in this note, the steps that are outlined below can assist you in narrowing down the problem. These steps are not an exhaustive list of every root-cause scenario that can contribute to this error. Instead, they provide a guide for checking the various components of your environment that can contribute to this behavior. If the steps below do not help you to resolve the issue, proceed to the Contact SAS Technical Support section.

1. Perform a cursory review of the middle-tier log files for any obvious errors. The steps that follow go into more detail about how to check different components. However, SAS Technical Support recommends an initial review of your middle-tier log files, specifically the following logs:

   Check for any obvious errors. Search the SAS Knowledge Base to see whether any errors that you encounter are known, documented issues. If no obvious errors are apparent, proceed with the next steps to check the different components in more detail.

   • SAS-configuration-directory/Lev1/Web/WebAppServer/SASServerX_Y/logs/server.log 
   • SAS-configuration-directory/Lev1/Web/WebAppServer/SASServerX_Y/logs/gemfire.log 
   • SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_41415/gemfire.log (Or SAS-configuration-directory/Lev1/Web/geode/instances/ins_41415/gemfire.log if using SAS 9.4 M8)
   • SAS-configuration-directory/Lev1/Web/WebServer/logs/error_date.log
   • SAS-configuration-directory/Lev1/Web/activemq/data/*.log
2. Ensure that all middle-tier services are running. Verify that the SAS Web Server, SAS Web Application Server, JMS Broker, and Cache Locator services all show their status as UP. (Note that the services can have a status of UP and still exhibit problems, but ensuring that they are running is a good first step.) See the Checking the Status of Servers section in the SAS^® 9.4 Intelligence Platform: System Administration Guide, Fourth Edition for more information about how to check this. If any of the services are NOT running, shut down all middle-tier services and restart them in the correct order. You can see the Operating Your Servers section in the SAS^® 9.4 Intelligence Platform: System Administration Guide, Fourth Edition for more information about starting services in the proper order. If your attempts to restart the services fail and one or more services still show as not running, proceed to step 3. If all the services appear to be up and running, proceed to step 4.
3. If any of the services fail to start, check the logs for that service (listed below). This is not a comprehensive list of all logs that might be indicative of this issue, but it provides a starting point of investigation for each service.) Review the logs and identify any potential errors that might inhibit that service from starting. Some known start-up issues are documented in SAS Knowledge Base, so you can search for more information on your error messages there if you identify any such issues.
   • SAS Web Application Server instances:
     • SAS-configuration-directory/Lev1/Web/WebAppServer/SASServerX_Y/logs/server.log
     • SAS-configuration-directory/Lev1/Web/WebAppServer/SASServerX_Y/logs/gemfire.log
   • Cache Locator: SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_41415/gemfire.log (Or SAS-configuration-directory/Lev1/Web/geode/instances/ins_41415/gemfire.log if using SAS 9.4 M8)
   • SAS Web Server: SAS-configuration-directory/Lev1/Web/WebServer/logs/error_date.log
   • JMS Broker: SAS-configuration-directory/Lev1/Web/activemq/data/activemq.log
4. If the services appear to be running, it can be helpful to check the splash-screen URLs for both the SAS Web Server and the SAS Web Application Server. This can test if those services are listening on their ports and are responding to a very basic request.
   1. Check the SAS Web Server URL, as follows, using the appropriate protocol (HTTP or HTTPS), hostname, and port for your environment: http(s)://host-name:port/
      • If SAS Web Server is responding, this URL should return a basic page that says Congratulations! You have successfully set up SAS Web Server. 
      • If you do not see this page, it indicates that SAS Web Server is not listening or responding on the host name and port that you entered in your URL. Verify that SAS Web Server is running and check the SAS Web Server  error_date.log file (in SAS-configuration-directory/Lev1/Web/WebServer/logs/) for any indication as to why SAS Web Server.
   2. Check the SAS Web Application Server SASServer1_1 URL, as follows, using the appropriate protocol (HTTP or HTTPS), host name, and port for your environment: http(s)://host-name:port/  (Note that the default HTTP port for SASServer1_1 is 8080, and the default HTTPS URL is 8443. So this URL is likely either http://host-name:8080/ or https://host-name:8443/, depending on whether you have HTTPS configured for SASServer1_1.)
      • If SASServer1_1 is responding, this URL should return a basic page that says Congratulations! You have successfully set up SAS Web Application Server. If you do see this page, proceed to checking the URLs in step 5.
      • If you do not see this page, it indicates that SASServer1_1 is not listening or responding on the host name and port that you entered in your URL. Verify that SASServer1_1 is running and check the SASServer1_1 server.log file (in SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/) for any indication as to why SASServer1_1 is failing.  
5. If all the services appear to be running and the SAS Web Server and SASServer1_1 URLS are working, test the specific endpoints that are implicated in this issue. Test whether you can access the following URLs in a browser:
   1. Access the URL that is provided in the error message in the SAS Deployment Wizard [http(s)://host-name:port/SASWIPClientAccess/rest/types/objects] and look up the specific object type that is mentioned. In the case of this example, the object type ID is 6040.

      If this URL fails, check the SASWIPClientAccess9.4.log file (which resides in SAS-configuration-directory/Lev1/Web/Logs/SASServer1_1/) for errors. Also check for errors in the server.log file that resides in SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/ for errors in deploying SASWIPClientAccess. (Note these logs are a suggested starting point for review. Other log analysis in SAS-configuration-directory/Lev1/Web/Logs/SASServer1_1/* or SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/* might be necessary, depending on what the preliminary review of the SASWIPClientAccess9.4.log and server.log files reveal.) If you receive an error in this step, proceed to step 7 to validate the SASWIPClientAccess connection properties.

   2. Access the SAS Content Server URL http(s)://host-name:port/SASContentServer/dircontents.jsp to verify whether your SAS^® Content Server is up and running. If you are prompted to log on when you try to access this page, use the sasadm@saspw user ID and the associated password. 

      If this URL fails, check for errors in the SASContentServer9.4.log file that resides in SAS-configuration-directory/Lev1/Web/Logs/SASServer1_1/. Also check the server.log file that resides in SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/ for errors in deploying SASContentServer. (Note these logs are a suggested starting point for review. Other log analysis in SAS-configuration-directory/Lev1/Web/Logs/SASServer1_1/* or SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/* might be necessary, depending on what the preliminary review of the SASContentServer9.4.log and server.log files reveal.) Proceed to steps 6 and 7 to further verify the SAS Content Server if you receive a failure in this step.

6. Confirm that the SAS Content Server validates successfully from the middle-tier machine. See the Validate the SAS Content Server section of the SAS^® 9.4 Intelligence Platform: System Administration Guide, Fourth Edition for details about how to verify this. 
7. Verify that the connection properties are correct for this environment. In particular, it is beneficial to check the SASContentServer, SASWIPClientAccess, and SASLogon properties. You can check these properties in SAS Management Console. For more information, see also the Specify Connection Properties section in SAS^® 9.4 Intelligence Platform: Middle-Tier Administration Guide, Fourth Edition. In addition, the Contact SAS Technical Support section below contains a link to a SAS program that you can use to output all of the internal and external connection properties from this environment. If you notice or suspect a problem with the connection properties, you can use this SAS program as a tool to assist in reviewing all of them. (If you have any questions about interpreting the output from this program, proceed to the Contact SAS Technical Support section and send the output to SAS Technical Support for assistance.)

If the steps above help you to identify an issue with a middle-tier component in your environment and you can resolve that issue, click Retry in SAS Deployment Wizard to retry the Load Content step or the Update Content step and proceed past the error that you encountered originally.

Contact SAS Technical Support 

If the steps above do no help resolve the error, contact SAS Technical Support for assistance. Provide the following information when you contact SAS Technical Support:

• Your SAS release and operating system.
• A screen capture of the error message that you receive in SAS Deployment Wizard.
• A detailed explanation of the issue that you experienced, including the results of the various troubleshooting steps above. This information is very beneficial in terms of identifying the troubleshooting that is required to resolve your issue. (For example, if you have issues with starting your services in step 2, indicate which services are not starting. If you get to step 4 and receive an error when you validate those URLS, provide the exact error message that you receive along with a screen capture.) 
• Execute the getttcpipconnections SAS program and send the results that the program generates. Note: Before you run this program, you need to edit it by modifying the options section at the top of the program to match the metadata connection information for this environment. 
• The following logs and files:
  • SAS-configuration-directory/Lev1/Logs/Configure/*
  • SAS-configuration-directory/Lev1/Web/WebAppServer/SASServerX_Y/logs/server.log
  • SAS-configuration-directory/Lev1/Web/ WebAppServer/SASServerX_Y/logs/catalina.out  [This file only exists in linux deployments.]
  • SAS-configuration-directory/Lev1/Web/ WebAppServer/SASServerX_Y/logs/gemfire.log
  • SAS-configuration-directory/Lev1/Web/ WebAppServer/SASServerX_Y/logs/localhost_access_log.*.txt
  • SAS-configuration-directory/Lev1/Web/Logs/SASServer1_1/*
  • SAS-configuration-directory/Lev1/Web/gemfire/instances/ins_41415/gemfire.log (Or SAS-configuration-directory/Lev1/Web/geode/instances/ins_41415/gemfire.log if using SAS 9.4 M8)
  • SAS-configuration-directory/Lev1/Web/WebServer/logs/error*.log
  • SAS-configuation-directory/Lev1/Web/activemq/data/*.log

  For some of the logs listed above, you might see several versions of the log file in the directory listed as those roll over automatically. Please ensure when sending in these logs that they cover the time frame of when you received the error.

  Note that SAS Technical Support might follow up with additional requests for more information depending on your issue, but providing this data up front will be greatly beneficial in allowing initial troubleshooting to occur based on the data provided when the track is opened.