Operations Control Logger 23โ.5 release notes
- Last UpdatedSep 10, 2026
- 2 minute read
New features and enhancements
This version incorporates the following changes and enhancements:
-
Upgraded gRPC version to 1.81.1
-
Enabled remote gRPC communication between aaLogger and Logger components.
-
Added PCS certificate-based secure communication between aaLogger and Logger components.
-
Updated Log Viewer with new snap-in and taskbar icons.
Resolved Issues
Operations Control Logger 23.5 includes corrections for the issues listed in the following table. These issues are listed by their Defect ID (IMS number), any assigned Service Request (SR) or Case Number with a brief description of the defect.
|
Defect ID |
Description |
|
3895279 |
SP2020R2SP1P01 was not compatible with Operations Control Logger 23.5. |
|
3886299 |
After upgrading to Logger version OCL 23.5 on a system with Batch Management 2023, Configurator could not configure Batch Management Events. |
|
3849005 |
After upgrading or installing Logger version Operations Control Logger 23.5 (from Operations Control Logger 22.1) on a System Platform All-in-One machine, the IDE crashed during Galaxy deployment. |
Known Issues
This section describes known issues in this release of Operations Control Logger.
|
Defect ID |
Description |
Workaround |
|
3932870 |
During the upgrade of Operations Control Logger on a node running SP2023, the Install Toolkit displays a service stop window where the name of the process and 'in use by application' details are missing. |
Not applicable |
|
4952013 |
During a upgrade, Log Viewer SP2023 R2 SP2 cannot connect to remote nodes running pre-SP2023 R2 SP2 versions, because older Logger Services do not support gRPC. |
Use the locally installed Log Viewer on the non-upgraded node to access its logs. or Enable Compatibility Mode by setting the Support RPC registry key value to 1 and restart the machine.
Important: Compatibility Mode disables some gRPC security enhancements and operates in a non-authenticated mode. Use this setting only as a temporary measure during the upgrade process. The recommended solution is to upgrade all nodes to a version that supports gRPC communication. |