Fixed Known Issues

Fixed Known Issues

This page outlines known issues that have been fixed in releases after 9.1.0.0.

Found in Version

Fixed in Version

Case ID

Internal ID

Summary

Found in Version

Fixed in Version

Case ID

Internal ID

Summary

Pre-release

9.1.2.0

39011
40350
41464

XE-10946

Fixed Known Issues

Pre-release

9.1.3.0

 

XE-5535

Fixed Known Issues

9.1.0.0

9.1.3.0

 

XE-11203

Fixed Known Issues

9.1.0.1

9.1.1.0

43386

XE-8906

Fixed Known Issues

9.1.1.0

9.1.3

44663

44765

XE-8934

Fixed Known Issues

SAP CC Notification Agent TLS Feature Not Working

The fields in SAP CC Notification Agent Configuration for configuring TLS connection are, Enable Secured

Connection, Keystore Path, and Keystore Password. These fields should not be enabled and used for now as it will

cause the agent to fail to connect to the SAP CC server.

Installation is Reported as Successful Even if the Platform Fails to Start

In some circumstances during installation the installer may report as successful when the platform has not started.

Error Occurs When Performing Multiple Installations on a Host with Different UNIX User IDs

The /tmp/syslog/syslog-debug.log file is created when a host machine contains an MZ 9 installation.

This file will be overwritten by any subsequent MZ 9 installations that are performed on the same host machine with a different UNIX user ID. However, the attempt to overwrite this file will fail and cause errors to the subsequent installations.

To solve this issue, modify the platform.xml file setting by using the mzsh topo open platform command. Edit the platform.xml file, and change the directory to use another directory using the following property:
<property name="mz.syslog.debuglogfile.filedir" value="[the directory]"/>.

mzsh topo show pico-view Does Not Display Full Information

The mzsh topo show pico-view does not show the pico names in the output. Picos can be viewed in the Desktops.

Legacy Desktop Issues

In the Legacy Desktop an exception may occur when you first log in to the Platform. If you log in again the exception is not shown.