Table of Contents

General Main Release 10.4.0 CU21

Note

For known issues with this version, refer to Known issues.

Tip

Enhancements

SLLogCollector: Memory dumps will be taken first & new option to skip the BPA tests [ID 43588]

Each time the SLLogCollector tool is run, by default, it will order the Standalone BPA Executor tool to execute all BPA tests available in the system. From now on, a checkbox will allow you to have those BPA tests skipped.

Also, when ordered to include memory dumps, up to now, the SLLogCollector tool would first run the BPA tests and collect all logging, and would then take the memory dumps. From now on, it will take the memory dumps first.

OPC communication is End of Life [ID 43785]

From now on, OPC communication should no longer be used in DataMiner connectors. Instead, QActions should be used, for example like in the Generic OPC Data Access connector.

Automation: Engine class now exposes the public property ScriptName [ID 43840]

From now on, the Engine class exposes the public property ScriptName.

This means that, in an Automation script, it will now be possible to retrieve the name of that script.

PDF reports configured in the Dashboards app can now also be sent if recipients are only specified in the CC and/or BCC fields [ID 43844]

Up to now, an PDF report configured in the Dashboards app could only be sent if recipients were specified in the To field.

From now on, it will also be possible to send PDF reports if recipients are only specified in the CC and/or BCC fields.

Note

Currently, PDF reports configured in DataMiner Cube still require recipients to be specified in the To field.

BPA test 'Cube CRL Freeze': Enhanced performance [ID 43854]

Because of a number of enhancements, overall performance of the the Cube CRL Freeze BPA test has increased.

This BPA test will identify client machines and DataMiner Agents without internet access where the DataMiner Cube application experiences a significant freeze during startup. This freeze is caused by the system attempting to verify the application's digital signatures with online Certificate Revocation Lists (CRLs).

DataMiner upgrade: Enhanced warning when an upgrade package cannot be found [ID 43916]

Up to now, when a DataMiner upgrade package could not be found, the following warning message would appear:

"WARNING! Upgrade ID [guid] no longer exists"

This message has now been replaced by the following one:

"WARNING! Upgrade package with ID [guid] no longer exists"

DxMs upgraded [ID 43961]

The following DataMiner Extension Modules (DxMs), which are included in the DataMiner upgrade package, have been upgraded to the indicated versions:

  • DataMiner Orchestrator 1.8.0

For detailed information about the changes included in those versions, refer to the DxM release notes.

QActions: Variables will now also be logged when a NotifyProtocol call fails [ID 43967]

When SLScripting executes a NotifyProtocol call, this can potentially lead to issues in SLProtocol when the variables are not in the correct format. Entries like NotifyProtocol with xxx failed. 0x800xxxxx can then appear in the error logging.

As entries like the one mentioned above make it hard to investigate exactly why a NotifyProtocol call has failed, from now on, these log entries will also include the values of the variables that were used in the NotifyProtocol call.

Note

When a NotifyProtocol call returns a 0x800706BA, RPC_S_SERVER_UNAVAILABLE error, that means that the SLProtocol process was not active and that the NotifyProtocol call was not the cause of the issue. Therefore, the values of the variables will not be included with this specific error is thrown.

Fixes

Parameter or DCF information would become unavailable to remotely hosted elements after a DataMiner connection had been re-established [ID 43765]

After a DataMiner connection had been re-established (due to e.g. a network issue, a failover switch, etc.), in some rare cases, an issue could occur that would cause parameter or DCF information to be unavailable to remotely hosted elements.

SLNet would wait too long before closing a connection [ID 43851]

In some rare cases, SLNet would incorrectly wait for 2 hours before closing a connection. As a result, SLNet and SLDataMiner would keep a large number of unused connections in memory for too long.

Timeout of queries against a Cassandra database was set incorrectly [ID 43912]

The timeout of queries against a Cassandra database was set incorrectly. This timeout has now been set to 10 minutes.

Visual Overview in web apps: Cube running as a service within SLHelper would not load the common server settings from ClientSettings.json [ID 43941]

Up to now, when DataMiner Cube was running as a service within the SLHelper process, it would not load the common server settings from C:\Skyline DataMiner\users\ClientSettings.json when it is unable to retrieve its own user settings.

From now on, regardless of whether DataMiner Cube can retrieve its own user settings, it will load the common server settings from C:\Skyline DataMiner\users\ClientSettings.json.

Notices regarding incorrect baseline values would no longer be generated when an element was started after being swarmed or migrated [ID 43970]

When an element that had been swarmed or migrated by means of a DELT package was started up, up to now, the following notices would no longer be generated when incorrect baseline values were found:

  • The fixed value (%g) is invalid. It is lower than nominal value (%g), and in the higher range. This value will not be used for alarm creation.
  • The fixed value (%g) is invalid. It is higher than nominal value (%g), and in the lower range. This value will not be used for alarm creation.

These notices will now be generated again.

Up to now, after elements had been swarmed or migrated by means of a DELT package, in some cases, Automation script matrix actions associated with those elements could fail.

Improve this page