When you use SAS^® Deployment Manager to upgrade an existing configuration of the SAS^®  middle tier (via the Update Existing Configuration Task), SAS Web Application Server fails to start. This failure can happen on the primary machine and all cluster nodes.

When this problem occurs, the following error message is generated:

This error happens when you upgrade the configuration after you apply certain SAS Web Application Server hot fixes (for example, W43006 or W43007) and you do not perform the post-installation instructions that are shown below. This error can occur also when you apply any hot fix that requires rebuilding or redeploying of web applications.

1. Leave SAS Deployment Manager running and use a separate session to make the changes in the next steps.
2. For SASServer1, navigate to SAS-configuration-directory/LevX/Web/WebAppServer/SASServer1_?/conf/Catalina/localhost.

   Note: The question mark (?) in SASServer1_? specifies a sequential integer that starts with 1 in a configuration with vertical cluster nodes. If you have custom server names, the server instance names should end with 1_?.

3. In the SASWorkflowServices.xml file, locate this line:
   <ResourceLink global="sas/jms/QueueConnectionFactory" name="jms/QueueConnectionFactory"     type="org.apache.activemq.ActiveMQConnectionFactory"/>
4. Change the TYPE= value as shown below:
   <ResourceLink global="sas/jms/QueueConnectionFactory" name="jms/QueueConnectionFactory" type="javax.jms.ConnectionFactory"/>
5. After you make the change above, return to the SAS Deployment Manager and click Retry. This change should allow the deployment manager to complete the upgrade-configuration task.

Operating System and Release Information