Table of Contents

General Main Release 10.5.0 CU20

Note

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

Important

Before you upgrade to this DataMiner version:

Tip

Changes

Enhancements

MessageBroker library has been upgraded to Microsoft .NET 10 [ID 44205]

The MessageBroker library has been upgraded to Microsoft .NET 10.

NATSMigration: Prerequisite checks added [ID 45668] [ID 46125]

Each time the NATSMigration tool is run, it will perform the following prerequisite checks:

  • DataMiner version check: Version must be at least Main Release 10.5.0 [CU4] or Feature Release 10.5.7 [CU1].
  • IIS binding check for 0.0.0.0:443, with optional hostname restrictions. A valid configuration requires a binding for 0.0.0.0 or, when multiple bindings exist, at least one binding to 127.0.0.1.
  • The server must run a recent Windows OS and TLS 1.2 must be available.
  • At least one of two ciphers must be available for managed NATS communication.

User-Defined APIs: UserDefinableApiEndpoint DxM health status is now reported to dataminer.services [ID 46356]

The UserDefinableApiEndpoint DxM now reports its health status to dataminer.services.

When it can validate or repair the IIS rewrite rule for user-defined APIs, it reports a healthy status. If the rule cannot be repaired, it reports an unhealthy status.

VerifyDotNetVersion prerequisite check will no longer check whether .NET 8 is installed [ID 46579]

From now on, the VerifyDotNetVersion prerequisite check will no longer check whether .NET 8 is installed when you install or upgrade DataMiner.

Microsoft .NET 10 remains required.

Fixes

Deleted-service information events would no longer have the service impact of the deleted service [ID 46195]

Up to now, when a service was deleted, the generated deleted-service information event would incorrectly no longer have the service impact of that deleted service.

Stopping an element with a logger table could cause SLProtocol to stop unexpectedly [ID 46299]

Up to now, in some rare cases, stopping an element with a logger table could cause the SLProtocol process hosting the element to stop unexpectedly.

DIS: DIS Inject could not trigger QAction execution on parameters unknown to SLNet [ID 46304]

Up to now, DIS Inject could not trigger QAction execution through parameters that are only known in SLProtocol and not in SLNet, such as dummy parameters.

From now on, DIS Inject will be able to trigger QActions through those parameters as well. Parameters that are known in SLNet will still be validated against the parameter security level.

Failover: SLASPConnection could fail to initialize after a Failover switch [ID 46350]

After a Failover switch, SLASPConnection could fail to initialize correctly when the DataMiner Agent came back online. This could cause the following issues:

  • The legacy Reporter could be unavailable when the LegacyReportsAndDashboards soft-launch option was enabled.
  • Incoming notifications could remain in memory without being processed, causing a memory leak.
  • The reporter page in DataMiner Cube and the distribution, alarm count, and timeline components in the Dashboards app could show outdated information.

SRM: Conflicting bookings incorrectly could be created during bulk creation [ID 46351]

Up to now, bulk creation of booking instances could incorrectly create instances identified as conflicting when the force quarantine flag was disabled.

NATSReset.exe could throw an InvalidOperationException after the IP address of a DataMiner Agent had changed [ID 46360]

Up to now, after the IP address of a DataMiner Agent had changed, running NATSReset.exe could throw an InvalidOperationException.

NATSMigration and NATSRepair could omit errors from the final error overview [ID 46362]

Up to now, some errors encountered by NATSMigration.exe or NATSRepair.exe could incorrectly be missing from the error overview at the end of the command-line output.

STaaS: Ordering DOM entries by optional fields could throw a CRUD exception [ID 46377]

On systems using STaaS, up to now, ordering DOM entries by an optional field could throw a CRUD exception when one or more entries did not contain that field.

SLSNMPManager could stop unexpectedly when testing a connection with SNMPv3 credentials [ID 46438]

Up to now, testing a connection that used SNMPv3 credentials from the Credential Library with SHA-224, SHA-256, SHA-384, or SHA-512 authentication could cause the SLSNMPManager process to stop unexpectedly.

SNMP: Community credentials could be lost when an automation script modified an element [ID 46537]

Up to now, when an automation script modified an element that used community credentials from the Credential Library on its main connection, the element could lose those credentials if the script did not change them. From now on, the credentials will be retained.

SLScripting could stop working due to recursive assembly resolution logging [ID 46572]

In some cases, when SLScripting tried to log that a different version of an assembly had been loaded than the requested version, the logging could trigger another resolution attempt for the same assembly. This could result in a recursive loop that caused SLScripting to stop working.

A safeguard has now been introduced in the version mismatch logger and the resolve failure logger to prevent this recursive behavior.

Problem when APIGateway was shut down [ID 46619]

Up to now, when the APIGateway module was shut down, it would stop working unexpectedly and throw an ObjectDisposedException.

Improve this page
Advanced search syntax