Problem

After you upgrade an existing SAS^® 9.4 environment to SAS^® 9.4 M7, SAS BI Web Service might not complete successfully. This issue occurs if the SAS Web Server is configured to use secure sockets (TLS).

When this problem occurs, you see the following message in the response to a web service request. The message is also entered in the SAS BI Web Service logs [SASBIWebServicesforJava9.4.log]:

If you experience this issue, confirm that the following entries are missing from SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/sas_webapps/sas.biws.war/WEB-INF/picklist file:

• name=stax_parser
• name=xstream

If the entries exist in the picklist file, you should not follow the resolution steps below because you likely have a different issue. In this scenario, contact SAS Technical Support for assistance. If the entries are missing, complete the resolution steps below.

Problem Resolution

You can address this issue using one of these methods:

• Install Hot Fix J2L005:

  https://tshf.sas.com/techsup/download/hotfix/HF2/J2L.html#67177

• As a workaround, you can add the following JAR files to the BIWS picklist file located at SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer1_1/sas_webapps/sas.biws.war/WEB-INF/picklist.

  name=stax_parser

  version=4.0.8.0_SAS_20121211183332

   

  name=xstream

  version=1.4.11.1_SAS_20190809140402

  Note: Verify that the JAR file exists in the SAS Versioned JAR Repository. Here is an example: 

  SASHome/SASVersionedJarRepository/eclipse/plugins/stax_parser_4.0.8.0_SAS_20121211183332

After that, try to re-create the issue to ensure that these steps resolve the behavior. If the problem is not resolved, contact SAS Technical Support for assistance. 

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS BI Web Services for Java	64-bit Enabled AIX	9.4		9.4 TS1M7
		Windows 7 Ultimate x64	9.4		9.4 TS1M7
		Windows 7 Ultimate 32 bit	9.4		9.4 TS1M7
		Windows 7 Professional x64	9.4		9.4 TS1M7
		Windows 7 Professional 32 bit	9.4		9.4 TS1M7
		Windows 7 Home Premium x64	9.4		9.4 TS1M7
		Windows 7 Home Premium 32 bit	9.4		9.4 TS1M7
		Windows 7 Enterprise x64	9.4		9.4 TS1M7
		Windows 7 Enterprise 32 bit	9.4		9.4 TS1M7
		Microsoft Windows Server 2022	9.4		9.4 TS1M7
		Microsoft Windows Server 2019	9.4		9.4 TS1M7
		Microsoft Windows Server 2016	9.4		9.4 TS1M7
		Microsoft Windows Server 2012 Std	9.4		9.4 TS1M7
		Microsoft Windows Server 2012 R2 Std	9.4		9.4 TS1M7
		Microsoft Windows Server 2012 R2 Datacenter	9.4		9.4 TS1M7
		Microsoft Windows Server 2012 Datacenter	9.4		9.4 TS1M7
		Microsoft Windows Server 2008 for x64	9.4		9.4 TS1M7
		Microsoft Windows Server 2008 R2	9.4		9.4 TS1M7
		Microsoft Windows Server 2008	9.4		9.4 TS1M7
		Microsoft Windows 11	9.4		9.4 TS1M7
		Microsoft Windows 10	9.4		9.4 TS1M7
		Microsoft Windows 8.1 Pro x64	9.4		9.4 TS1M7
		Microsoft Windows 8.1 Pro 32-bit	9.4		9.4 TS1M7
		Microsoft Windows 8.1 Enterprise x64	9.4		9.4 TS1M7
		Microsoft Windows 8.1 Enterprise 32-bit	9.4		9.4 TS1M7
		Microsoft Windows 8 Pro x64	9.4		9.4 TS1M7
		Microsoft Windows 8 Pro 32-bit	9.4		9.4 TS1M7
		Microsoft Windows 8 Enterprise x64	9.4		9.4 TS1M7
		Microsoft Windows 8 Enterprise 32-bit	9.4		9.4 TS1M7
		Microsoft® Windows® for x64	9.4		9.4 TS1M7
		64-bit Enabled Solaris	9.4		9.4 TS1M7
		HP-UX IPF	9.4		9.4 TS1M7
		Linux for x64	9.4		9.4 TS1M7
		Solaris for x64	9.4		9.4 TS1M7

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

Upgrading web services to SAS 9.4M7 from previous releases results in a failure to execute an existing SOAP web service. This issue occurs only in deployments that are configured for secure sockets (TLS) for the SAS Web Server communication.

Type:	Problem Note
Priority:	medium

Date Modified:	2021-12-22 17:48:45
Date Created:	2021-12-12 12:14:47