When performing an upgrade-in-place to SAS 9.4M7, you might encounter an issue with the post-update task for SAS Environment Manager. The vfabrchyperc_postapplyUpdate_yyy-mm-dd-xx.xx.xx.log file might show messages similar to the following:
[hypericserverTarget] 2022-03-30 14:29:38,785 [main] INFO com.sas.appserver.utils.AntProcessInvoker - Working Directory: C:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\hqapi1-client-6.0.2\bin[hypericserverTarget] 2022-03-30 14:29:38,785 [main] INFO com.sas.appserver.utils.AntProcessInvoker - Working Directory: C:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\hqapi1-client-6.0.2\bin[hypericserverTarget] [exec] java.lang.NoClassDefFoundError: org/jasypt/encryption/StringEncryptor[hypericserverTarget] [hypericserverTarget] [exec] at java.lang.Class.getDeclaredMethods0(Native Method)
...
[hypericserverTarget] 2022-03-30 14:29:39,192 [main] WARN com.sas.appserver.vfabrchyperc.HypericServer - Failed to query user list in EVManager database:
[echo] IN insertWarning !!!
[echo] valueToUse=Failed to query user list in EVManager database:
...
2022-03-30 14:29:39,348 [main] ERROR com.sas.sdw.SDWExceptionHandler - com.sas.sdw.SDWException: org.xml.sax.SAXParseException; systemId: file://C/SAS/Config/Lev1/Web/SASEnvironmentManager/server-5.8.0-EE/hqapi1-client-6.0.2/bin/user.xml; lineNumber: 1; columnNumber: 1; Premature end of file.
...
[hypericserverTarget] 2022-02-15 11:14:42,185 [main] INFO com.sas.appserver.utils.AntProcessInvoker - Working Directory: D:\SASConfig\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\hqapi1-client-6.0.2\bin
[hypericserverTarget] [exec] Error running command: Connection refused: connect
[hypericserverTarget]
[hypericserverTarget] [exec] java.net.ConnectException: Connection refused: connect
...
2022-02-15 11:14:51,586 [main] ERROR com.sas.sdw.SDWExceptionHandler - com.sas.sdw.SDWException: org.xml.sax.SAXParseException; systemId: file://D/SASConfig/Lev1/Web/SASEnvironmentManager/server-5.8.0-EE/hqapi1-client-6.0.2/bin/user.xml; lineNumber: 1; columnNumber: 1; Premature end of file.
If SAS Environment Manager fails to start after a UIP to SAS 9.4M7, a message similar to the following might appear in the SAS-configuration-directory/LevN/Web/SASEnvironmentManager/server-5.8.0-EE/logs/wrapper.log file:
INFO | jvm 1 | 2022/01/17 14:02:46 | WrapperStartStopApp Error: Unable to locate the class org.hyperic.bootstrap.HQServer: java.lang.ClassNotFoundException: org.hyperic.bootstrap.HQServer
Also, the Tomcat release might not have been updated correctly. You can confirm this by checking the Tomcat release in the SAS Environment Manager configuration directory:
- Navigate to SAS-configuration-directory/LevN/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/ directory.
- Locate the tomcat-x.x.xx.A.RELEASE file. The Tomcat release should be updated from tomcat-9.0.10.A.RELEASE to tomcat-9.0.31.A.RELEASE.
If you encounter the above warnings and errors in the vfabrchyperc_postapplyUpdate_yyy-mm-dd-xx.xx.xx.log file and the Tomcat release is not updated, the proposed workaround is to reconfigure SAS Environment Manager by completing the following steps.
Note: Before you begin, it is suggested that you take a full backup of the environment, such as a snapshot.
Note: If SAS Environment Manager is currently configured for SSL in your environment, make a copy of the current hyperic.keystore file and save it in an accessible directory that is not within SAS-configuration-directory/LevN/Web/SASEnvironmentManager/server-5.8.0-EE/*. As a reminder, even if you create a backup of the hyperic.keystore file, SSL must be configured again (see steps for SAS KB0036365 for Windows systems or SAS KB0036366 for UNIX systems).
Steps to Remove and Reconfigure SAS Environment Manager
- Stop the SAS middle-tier services
- For UNIX systems, there is a sas.servers.mid script that you can use in the SAS-configuration-directory/LevN/ directory.
- For Windows systems, you need to shut down the SAS middle-tier services in proper order (see the Starting Servers in the Correct Order section in the SAS® 9.4 System Administration Guide).
- Do not stop all SAS services, the Metadata Server and Web Infrastructure Platform Data Server must be running.
- On the middle-tier host where SAS Environment Manager is configured, run SAS® Deployment Manager.
- Select Remove existing configuration.
- When prompted to select products, select the following:
- SAS Environment Manager Configuration (Do NOT select SAS Environment Mgr Mid-Tier 2.x, because this is a different product.)
- SAS Environment Manager Enablement Kit Plug-in (Do NOT select SAS Environment Manager Enablement Kit Server, because this is a different product.)
- SAS Job Monitor Hyperic Plug-in
- Continue through the prompts to remove the configuration for the selected items.
- Once SAS Deployment Manager finishes removing the configuration, launch SAS Deployment Manager again.
- Select Uninstall SAS Software.
- Select ONLY SAS Environment Manager to uninstall.
- Continue through the prompts.
- Once the uninstall completes, take a backup of your metadata (a full system backup is also sufficient if you are able). See the About Backing Up and Restoring Your SAS Content section in the SAS® 9.4 System Administration Guide for metadata backup steps.
- From your middle-tier machine, launch SAS® Deployment Wizard from your M7 depot.
- Run the setup.exe file for Windows systems.
- Run the setup.sh file for UNIX systems.
- Select Install SAS Software ► Planned Deployment. Select both install and configure software on this prompt.
- When prompted for products to INSTALL, select only SAS Environment Manager.
- When prompted for products to CONFIGURE, select the following products:
- SAS Environment Manager
- SAS Environment Manager Enablement Kit Plugin
- SAS Job Monitor Hyperic Plugin (only select it if you had to remove it the first time)
- If SAS Environment Manager Plug ins for Foundation Servers is selected by default, then it is alright to leave it selected.
- Continue through the prompts to perform the re-install and configure.
Note: If you are prompted for a hyperic.keystore file at any point, because you had SAS Environment Manager setup for SSL previously, then browse to the backup copy of the hyperic.keystore file that was made before these steps were performed.
If you encounter any issues during this process, open a track with SAS Technical Support and provide the Configure logs from the SAS-configuration-directory/Lev/Logs/Configure/* directory.