General Main Release 10.7.0 – Changes (preview)
Important
We are still working on this release. Some release notes may still be modified or moved to a later release. Check back soon for updates!
Important changes
The following changes may have an impact on your system, so please make sure to check these before you upgrade:
- SNMP trap binding values will now only display plain ASCII characters [ID 44527]
- Service template definitions will no longer be stored alongside services [ID 45370]
- Scheduler: Swarmed tasks could execute actions configured for another task [ID 46728]
- GQI: GQI via SLHelper disabled by default [ID 46927]
- Service & Resource Management: Support for legacy reservations removed [ID 46931]
- Document Intelligence: Assistant permission checks [ID 46944]
- DataMiner upgrade: Prerequisite check for the end of SLHelper GQI support [ID 46957]
- DataMiner upgrade: Prerequisite checks for End of Support and End of Life features [ID 46984]
- DataMiner startup: MySQL requires an explicit End of Support override [ID 47000]
- SLNet: Support for .NET Remoting removed [ID 47004]
- QActions: JScript and VBScript are no longer supported [ID 47010]
- Security: Atlassian Crowd authentication is no longer supported by default [ID 47014]
- Security: RADIUS authentication is no longer supported by default [ID 47018]
- DataMiner start-up: Cassandra 3.x and earlier require an End of Support override [ID 47024]
- Connectors: dllName and DirectConnection are no longer supported by default [ID 47028]
- DataMiner startup: Elasticsearch requires an explicit End of Support override [ID 47033]
- Automation: Script Runner could load an incorrect assembly version [ID 47069]
- Legacy Reports and Dashboards: Upgrade prerequisite and IIS cleanup [ID 47135]
Changes
Breaking changes
SNMP trap binding values will now only display plain ASCII characters [ID 44527]
When the system receives a trap binding value of type OctetString, that value will either be automatically converted into characters (e.g., 0x41 will become "A") or remain in a hexadecimal string format (e.g., when the value contains a byte that is not printable like 0x02, which is an STX control character).
Up to now, hexadecimal values above the ASCII range (i.e., values >= 0x7F) were considered printable characters, and were not converted into a hexadecimal string. This would cause issues with, for example, the Unicode control character 0x8C, which would be displayed as a question mark. In such cases, complex QAction code would then be required to have it converted back into a hexadecimal value.
Also, DataMiner is not aware of whether a binding value actually contains text (e.g., a MAC address consisting of octets) or, if the value contains text, how that text was encoded (e.g., Windows code page 1252, UTF-8, UTF-16, etc.).
From now on, hexadecimal values outside of the ASCII range will be considered non-printable characters, and will remain in hexadecimal string format.
This is a breaking change.
Up to now, text containing characters that were encoded in extended ASCII (i.e., Windows code page 1252) were converted from raw octets into string text. For example, the French word "hélicoptère" would be received correctly. From now on, that same word will be received as hexadecimal string "68e96c69636f7074e87265", and a QAction will need to convert it back into a string using the correct encoding.
Service template definitions will no longer be stored alongside services [ID 45370]
Up to now, service templates were stored alongside services in the C:\Skyline DataMiner\Services and C:\Skyline DataMiner\RemoteServices folders. Each service template also had exactly one DataMiner Agent actively hosting the service template.
In preparation of service swarming, service template definitions have now been moved into a new C:\Skyline DataMiner\ServiceTemplates folder, which will be synchronized across the cluster. A service template no longer has a dedicated hosting agent, which means that they now remain available even if DataMiner Agents are down.
Service & Resource Management: Support for legacy reservations removed [ID 46931]
Support for legacy Resource Manager reservations has been removed from the DataMiner server. From now on, use ReservationInstance objects instead of legacy reservations.
The related types remain available in SLNetTypes so existing projects can still compile. However, the following API members have been marked as obsolete:
- The create, read, update, and delete (CRUD) methods for all three features in
ResourceManagerHelper. - The error data related to these features in
ResourceManagerErrorData. - The messages for the CRUD operations.
- The
ResourceManagerConfigInfoMessage.ConfigInfoType.ForceCleanupenum value, which was only used to clean up reservation-related files.
SLNet will now throw a DataMinerException for CRUD requests related to these features or for a ForceCleanup request.
For compatibility with older DataMiner server versions, the legacy reservation methods in ResourceManagerHelper will still send requests to SLNet.
Document Intelligence: Assistant permission checks [ID 46944]
Each Document Intelligence request from SLNet now includes connection information so the Assistant can check the Intelligence Usage permission.
Important
Document Intelligence in DataMiner 10.6 is incompatible with Assistant versions that enforce these permission checks (i.e., Assistant 4.0.0 or newer).
QActions: JScript and VBScript are no longer supported [ID 47010]
Support for JScript and VBScript in QActions has reached End of Life and has been removed. An element that uses a connector containing a QAction with JScript or VBScript encoding will now go into an error state.
The default *.js and *.vbs files in C:\Skyline DataMiner\ProtocolScripts are no longer included in upgrade packages and will be removed during an upgrade.
In addition, the SLSite COM component will be uninstalled during an upgrade.
Legacy Reports and Dashboards: Upgrade prerequisite and IIS cleanup [ID 47135]
Legacy Reports and Dashboards are no longer available from DataMiner 10.7.0/10.7.1 onwards. The VerifyNoLegacyReportsDashboards upgrade prerequisite will now block an upgrade from a version earlier than 10.7.0 if these modules are enabled.
The check reads the effective LegacyReportsAndDashboards soft-launch option from the SLNet section of C:\Skyline DataMiner\SoftLaunchOptions.xml. An explicit setting takes precedence over all. If neither option is present, the modules are considered disabled.
Before retrying the upgrade, migrate any required legacy functionality and do one of the following:
- Set
LegacyReportsAndDashboardstofalse. - Remove
LegacyReportsAndDashboards, providedallis not enabled.
Malformed XML or file-access errors will also block the upgrade. The prerequisite will not modify the configuration automatically. The configuration check will be skipped if the currently installed DataMiner version is already 10.7.0 or later.
In addition, IIS configuration will now remove existing legacy /Reports and /Dashboards application entries and will no longer create or restore them, regardless of the soft-launch settings. The modern /Dashboard application and modern reporting/PDF functionality will remain unaffected.
Enhancements
SLNet: Trend graphs in Cube will now also correctly display behavioral change points for table column parameters without advanced naming [ID 41751]
Because of a number of enhancements made in SLNet, trend graphs in DataMiner Cube will now also correctly display behavioral change points for table column parameters without advanced naming.
Automation: Engine class now has an OnDestroy handler that will allow resources to be cleaned up when a script ends [ID 43919]
An OnDestroy handler has now been added to the Engine class. This handler will allow resources to be cleaned up when a script ends.
Multiple handlers can be added. They will run synchronously, and if one handler throws an error, the others will keep on running.
New parameter caches for client apps [ID 43945]
Two new parameter caches are now available for client apps (e.g., DataMiner Cube):
- ProtocolParameters (linked to GetProtocolParameter on the client connection)
- ElementProtocolParameters (linked to GetElementProtocolParameter on the client connection)
Both caches are added on the connection object, and have the ability to cache in memory (for the current session) and on disk (for a next session).
Automation: All methods that use parameter descriptions have now been marked as obsolete [ID 43948]
All methods in the Skyline.DataMiner.Automation namespace that use parameter descriptions have now been marked as obsolete.
Service & Resource Management: New resource manager settings to configure the number of start action threads and simultaneous actions [ID 44056]
Because of a number of enhancements, overall performance has increased when starting multiple bookings in parallel.
Also, in the resource manager, it is now possible to configure the number of start action threads and simultaneous actions.
| Setting | Description |
|---|---|
| MaxAmountOfThreads | The number of threads the resource manager will use to start bookings. By default, 6 threads will be used. To restore this setting to the default value, set its value to null. Note: The number of threads must at least be set to 2 in order for the scheduler to be able to start an action and keep a thread available for asynchronous continuations. |
| MaxAmountOfParallelTasks | The number of parallel actions the resource manager will start on the threads. By default, the number of parallel action is set to 7. To restore this setting to the default value, set its value to null. |
The following example shows how you can configure this from an automation script.
private void UpdateResourceManagerConfigSettings()
{
var setConfigMessage = new ResourceManagerConfigInfoMessage(ResourceManagerConfigInfoMessage.ConfigInfoType.Set)
{
ResourceManagerAutomationSettings = new ResourceManagerAutomationSettings()
{
ResourceManagerAutomationThreadSettings = new ResourceManagerAutomationThreadSettings()
{
MaxAmountOfParallelTasks = 30,
MaxAmountOfThreads = 8
}
},
};
engine.SendSingleResponseMessage(setConfigMessage);
}
In most cases, these settings can keep their default value, unless performance has to optimized when multiple concurrent bookings have to be started. In order to increase performance, the number of threads and parallel tasks can be increased, provided the DataMiner Agent and the database can handle the increased load.
Note
- When the above-mentioned settings have been changed, the resource manager must be restarted.
- Only users with Modules > System configuration > Tools > Admin tools permission are allowed to change the above-mentioned settings.
- If the
SkipDcfLinkssetting is set to true, we recommend that you do not set MaxAmountOfParallelTasks too high. DCF link creation can be an expensive operation. Performing a large number of action in parallel might decrease performance.
Enhanced visibility on SLNet connection issues [ID 44069]
Visibility on SLNet connection issues has been enhanced:
When a dashboard cannot be loaded because a DataMiner Agent is offline, an appropriate error message will now appear in that dashboard.
A new log file named SLNetConnectionsMonitor.txt will now keep a historic record of all SLNet connection states.
Augmented Operations: Server-side support for new flatline detection modes [ID 44094]
When, in DataMiner client applications (e.g., DataMiner Cube), you are configuring the Augmented Operations alarm settings for a particular parameter in an alarm template, from now on, it will be possible to choose between the following flatline detection modes:
| Mode | Description |
|---|---|
| Smart flatline alarming | In this mode, SLAnalytics will automatically determine when a flatline period is anomalous by comparing it to the parameter's historical behavior. A new flatline period will only trigger an alarm if it is significantly longer than previously observed flat periods. |
| Absolute flatline alarming | In this mode, you can define a fixed duration threshold (in seconds) for when a flatline event should trigger an alarm. Additionally, you can assign a severity level to the generated flatline alarm event. |
See also: Alarm templates: New flatline detection modes in Augmented Operations alarm settings [ID 44191]
DataMiner upgrade: Web-only upgrades with version 10.6.x or above will now require the DMA to have version 10.5.x or above [ID 44103]
From now on, it will no longer be allowed to perform web-only upgrades with version 10.6.x or above on DataMiner Agents with a version below 10.5.x.
This means, that any DataMiner Agent on which you want to perform a web-only upgrade with version 10.6.x or above will first have to be upgraded to version 10.5.x or above.
dataminer.services: Restrictions when adding a DMA to a DMS [ID 44171]
From now on, when you try to add a DataMiner Agent to a DataMiner System, the operation will fail in the following cases:
- The DataMiner Agent is cloud-connected, but the DataMiner System is not.
- The DataMiner Agent and the DataMiner System are cloud-connected, but they do not have the same identity, i.e., they are not part of the same cloud-connected system.
If the DataMiner System is a STaaS system, adding a DataMiner Agent will also fail if the DataMiner Agent is not cloud-connected.
SLWatchdog will now report SLNet/SLDataGateway TPL ThreadPool and 'time dilation' issues as run-time errors [ID 44186]
From now on, whenever the TPL ThreadPool of SLNet or SLDataGateway would get stuck or a "time dilation" would occur on your system (for example, when a freeze of a virtual machine would cause sleep actions to take longer than anticipated), SLWatchDog will report these issues as a run-time error.
Scheduler will now be able to start more than 10 synchronously running automation scripts [ID 44200]
Up to now, using Scheduler, it would only be possible to start a maximum of 10 synchronously running automation scripts.
From now on, it will be possible to start more than 10 synchronously running automation scripts.
Relational anomaly detection: GetRADParameterGroupInfoResponseMessage now also includes the ID of the RAD parameter group [ID 44237]
The response to a GetRADParameterGroupInfoMessage will now also include the ID of the RAD parameter group.
Service & Resource Management: Enhanced communication between resource managers across DataMiner Agents [ID 44279]
A number of enhancements have been done with regard to the communication between resource managers across DataMiner Agents. This will especially enhance performance when starting multiple bookings on non-master DMAs.
Automation: Entrypoint ID added to the 'Finished executing script' log entry [ID 44382]
The entry added to the SLAutomation.txt log file when an automation script has finished will now contain the entrypoint ID.
In the following example, the entrypoint ID can be found at the end of the entry between brackets (11):
2025/12/18 13:40:00.546|SLAutomation.exe 8.0.1415.2|22300|16908|CAutomation::Execute|INF|0|Finished executing script: 'script_RT_USER_DEFINABLE_APIS_BodySizeLimit_RT_USER_DEFINABLE_APIS_BodySizeLimit_MaxResponseBodySize' (ID: 7) - SUCCEEDED - Execution took 00.308s. (11)
DataMiner backup: 'Ticketing Gateway Configuration' removed from the list of backup options [ID 44401]
As the Ticketing app is End of Life as of DataMiner 10.6.x, Ticketing Gateway Configuration has now been removed from the list of backup options.
DataMiner backup: Scheduler configuration will now be included in full and configuration backups [ID 44584]
From now on, the Scheduler configuration found in C:\Skyline Dataminer\Scheduler will be included in the following pre-configured backups:
- Full backup (without database)
- Configuration backup (without database)
If you create a custom backup, the Scheduler configuration will be included only if you selected the DataMiner settings option.
DataMiner Objects Models: Selected subset of fields from DomInstance objects will now be read from the repository API [ID 44600]
Since DataMiner 10.6.0/10.6.1, it is possible to read only a selected subset of fields from DomInstance objects. In order to further enhance performance, from now on, those subsets will be read from the repository API.
Currently, the repository API will still request the full objects from the database and extract the required values.
Note
When a field value is requested, the type defined in the field descriptor will be used. In order to determine that type, field descriptor IDs should be unique across section definitions in a DOM module.
NotifyMail.html has been updated in order to better support both classic Microsoft Outlook and new Microsoft Outlook [ID 44617]
The C:\Skyline DataMiner\NotifyMail.html file, i.e., the email report template, has been updated to better support both classic Microsoft Outlook and new Microsoft Outlook.
SLDataGateway: Job queue updates will now be logged in SLJobQueues.txt [ID 44661]
Up to now, log entries regarding SLDataGateway job queue updates would be logged in the C:\Skyline DataMiner\Logging\SLDbConnection.txt file.
From now on, these log entries will be logged in the C:\Skyline DataMiner\Logging\SLDataGateway\SLJobQueues.txt file instead.
Connector synchronization enhancements [ID 44715]
A number of enhancements have been made with regard to the synchronization of connectors within a DataMiner System:
The first time you upload a version of a new connector, it will automatically be set as production version. Up to now, when a connector version was automatically set as production, this would trigger a synchronization of that version. From now on, the new connector will be synchronized within the cluster, and when a DataMiner Agent detects that it is the first version, it will set it as the production version.
Up to now, when a parent connector exported child connectors (as is the case with DVE connectors), these exported child connectors would be synchronized within the cluster when the parent connector was added or modified. From now on, only the parent connector will be synchronized, and each DataMiner Agent will then generate the child connectors.
From now on, a protocol.xml file that is generated based on the active function.xml file will no longer be synchronized when the function is activated.
Note
The midnight sync has not been altered.
Enhanced logging for connections towards SLNet [ID 44765] [ID 45359]
A number of improvements have been made to SLNet logging, particularly to help troubleshoot unexpected disconnects between SLNet instances and between SLNet and DataMiner Cube.
New log files
In the C:\Skyline DataMiner\Logging folder, you can now find the following new log files:
| Log file | Description |
|---|---|
| SLNetConnections.txt | An entry will be added each time an SLNet to SLNet connection encounters a timeout. |
| SLCubeConnections.txt | An entry will be added each time a Cube to SLNet connection encounters a timeout. |
If information logging is set to Level 4, the log entries will also mention if a message is waiting until other calls have finished. Up to 10 active calls are allowed at any given time.
Existing log files
ConnectionDiagnostics in
C:\Skyline DataMiner\Logging\SLNet\ConnectionDiagnosticswill now also report which calls were in progress at a certain point in time.SLHangingCalls.txt will now contain more detailed information:
- Apart from blocking calls, it will now also log asynchronous calls.
- The entries will now mention the exact message that is hanging, rather than the wrapping
EncryptedMessage.
Note
- Log entries can also be added to SLNetConnections.txt and SLCubeConnections.txt for SLNet connections created elsewhere. To do so, provide a
LoggerProvidertoSLNetTypesDiagnostics.AddLoggerProvider(). - When a Cube connected to a system without server-side
SLNetTypesDiagnosticsconnects to a system with server-sideSLNetTypesDiagnostics, the SLCubeConnections.txt log file will not be populated. Restart Cube if you want that log file to be populated.
Security enhancements [ID 44804] [ID 45582] [ID 46665]
A number of security enhancements have been made.
Enhanced SSH logging [ID 44975]
A number of enhancements have been made to the SSH logging:
From now on, when an SSH connection times out for one of the following reasons, an entry will be added to the element log:
- Host name could not be resolved.
- User authentication failed.
In the SSH logging, it will now clearly be indicated which operations have been performed. For example, during authentication, the logging will now clearly state which authentication methods have been used and what the results were.
In the SSH logging, most entries will now mention the session ID associated with the entry. As this same session ID is also mentioned in element log entries, users will find it much easier to find out which log entries are related.
Also, an issue has been fixed. When a host name could not be resolved to an IP address, up to now, the SSH connection would incorrectly try to connect to localhost. From now on, when the host name could not be resolved, the connection will fail.
SLLogCollector: New option to collect DLL file information [ID 45044]
The SLLogCollector tool now has a new Collect DLL info option. If enabled, all packages will include the following information retrieved from all DLL files found in the C:\Skyline DataMiner\Files and C:\Skyline DataMiner\ProtocolScripts folders:
- Name
- Version
- Culture
- Public key
- Dependencies
By default, the Collect DLL info option is disabled.
DataMiner Object Models: SLDataGateway will now try to read only the selected fields from an OpenSearch or Elasticsearch database [ID 45151]
When SLDataGateway is retrieving DOM data from an OpenSearch or Elasticsearch database, from now on, it will attempt to retrieve only the selected fields using the native field projection capabilities of these databases. This will considerably enhance data transfer efficiency and overall performance.
This optimization will leverage the indexed field values to avoid transferring complete objects when only specific fields are needed.
If selected field retrieval is not supported by the database, the system will automatically fall back to retrieving the full object and extracting the required values. This currently applies to STaaS and to queries that require post-filtering or post-sorting.
By default, the value type will be the field type defined by the exposer. When a field value is explicitly requested, the type defined in the field descriptor will be used instead.
Important
To ensure correct type resolution, field descriptor IDs must be unique across all section definitions within a DOM module. Non-unique IDs may result in incorrect type mapping and unexpected behavior.
Swarming can now be enabled for a smart-serial element in server mode [ID 45173]
In a DataMiner protocol, you can now indicate that swarming should be allowed for an element with a smart-serial connection in server mode.
By default, swarming is not allowed for such elements. However, if your element can communicate with its data source at startup to specify where data should be sent, you can now safely enable swarming by adding the following configuration to the protocol.xml file:
<Swarming>
<BypassChecks>
<Check>smartSerialAsServer</Check>
</BypassChecks>
</Swarming>
Correlation: GetAvailableCorrelationRulesMessage response now also includes grouping information [ID 45187]
When a GetAvailableCorrelationRulesMessage is sent to SLNet, the response will now also include information regarding the grouping defined in the correlation rules.
DataMiner upgrade: .NET Framework 4.8 will no longer be installed [ID 45196]
From now on, during a DataMiner upgrade, Microsoft .NET Framework 4.8 will no longer be installed.
On most machines running DataMiner, this will already be installed. If, for any reason, you need to install this package, it can be downloaded from the official download page.
DataMiner upgrade: A number of default Visio stencils will no longer be included [ID 45202]
From now on, a DataMiner upgrade package will no longer contain the following Visio stencil files:
- AppearTV DC1000.vss
- AppearTV DC1100.vss
- AppearTV MC3000.vss
- AppearTV MC3100.vss
- AppearTV SC2000.vss
- AppearTV SC2100.vss
- BridgeTech.vss
- Nimbra300.vss
- Nimbra600.vss
- NimbraNodes.vss
- United States Maps (US units).vss
- World Maps (Metric).vss
- World Maps (US units).vss
Note that the following stencil files will still be deployed:
- Buttons.vssm
- Icons.vssx
- KPI.vssm
- SkylineNewDrawing.vsdx
Note
The above-mentioned stencil files that are no longer included in DataMiner upgrade packages will not automatically be removed from existing systems.
Automation: Compiled assemblies generated during syntax checks will no longer be loaded into memory [ID 45214]
Up to now, when a syntax check was performed on an automation script (e.g., by clicking Validate in a script's C# block in DataMiner Cube), the compiled assembly would be loaded into the SLAutomation memory.
From now on, compiled assemblies generated during syntax checks will no longer be loaded into memory.
SLLogCollector: Only BPA tests deployed by default will be rerun each time a log package is created [ID 45228]
Up to now, each time SLLogCollector created a log package, it would rerun all BPA tests deployed on the system. From now on, it will only rerun the BPA tests deployed by default.
Note
Each time a log package is created, all BPA test results available on the system will still be included in that package. This means that all results from non-default BPA tests will also be included, even when, from now on, these tests are no longer rerun when a package is created.
Number of smart-serial messages allowed to enter has now been limited [ID 45273]
In order to protect DataMiner against a continuously growing queue of incoming smart-serial messages, the number of smart-serial messages that are allowed to enter per element with smart-serial connections has now been limited.
If more than 200 MB of messages are waiting in the queue, a notice alarm will be generated, and a log entry will be added to the SLErrorsInProtocol.txt file. This is meant as a warning. As soon as the queue drops below 150 MB again and the maximum limit is not breached, the notice alarm will be cleared.
If more than 300 MB of messages are waiting in the queue, an error alarm will be generated, and a log entry will be added to the SLErrorsInProtocol.txt file. As the maximum limit was breached, the queue will no longer accept any additional messages.
Once the maximum limit has been breached, the queue will need to drop below 200 MB before new messages can be added again. As soon as the queue drops below 200 MB, the error alarm will become a notice alarm. Note that, even when the queue would be empty, the notice alarm will not be cleared. It will serve as an indication that part of the communication was lost.
Note
- We strongly advise you to restart the element when the limit has been breached. When certain messages within a data stream get dropped because the maximum queue limit was breached, an incomplete data stream may get processed, which could then produce unexpected results.
- The alarm not only mentions the limit that was reached (in MB). It also mentions the number of messages that are present in the queue. This number of messages is not always equal to the number of responses to be processed. For example, in some cases, Windows can combine multiple received UDP packets into one when adding packets to the receive buffer, causing SLPort to then add a single message to the queue.
DxMs upgraded [ID 45304] [ID 45347] [ID 45392] [ID 45506] [ID 45944] [ID 46119] [ID 46565]
The following DataMiner Extension Modules (DxMs), which are included in the DataMiner upgrade package, have been upgraded to the indicated versions:
- DataMiner ArtifactDeployer 1.10.0
- DataMiner CloudGateway 3.5.0
- DataMiner CoreGateway 2.14.17
- DataMiner DataAPI 1.4.6
- DataMiner FieldControl 2.12.2
- DataMiner Orchestrator 1.11.0
- DataMiner SupportAssistant 1.9.3
For detailed information about the changes included in those versions, refer to the DxM release notes.
DataMiner upgrade: Clients can now also connect to the orchestrating Agent when it has finished upgrading locally [ID 45312]
When you upgrade an entire DMS, every DMA will upgrade itself locally, and one of them, the so-called orchestrating Agent, will give you progress updates. This orchestrating Agent is the Agent from which the upgrade was triggered.
Up to now, while a full DMS upgrade was in progress, you could connect with a client application (e.g., DataMiner Cube) to any of the Agents that had finished upgrading locally, except the orchestrating Agent. Even when that Agent had finished upgrading locally, it would not be possible to connect to it. From now on, this will be possible.
SLNetConnectionsMonitor.txt will now log all state changes of all SLNet connections [ID 45316]
Up to now, only the general state of the entire cluster when an Agent connected or disconnected would be logged in the SLNetConnectionsMonitor.txt file.
From now on, all state changes of all SLNet connections between Agents in the cluster will be logged in the SLNetConnectionsMonitor.txt file.
Automation: Enhanced memory usage when compiling development packs and script libraries [ID 45333]
Because of a number of enhancements, memory usage has improved when compiling development packs and script libraries.
SLAnalytics: Enhanced performance when detecting flatline events [ID 45376]
Because of a number of enhancements, overall performance has increased when detecting flatline events, especially on systems with a large number of monitored parameters.
Standalone BPA Executor will now return exit code 1 or 2 when issues were detected [ID 45433]
Up to now, the Standalone BPA Executor tool would always return exit code 0, regardless of whether the BPA tests it had run had detected any issues. In situations where the tool had been integrated into another process (e.g., a DataMiner upgrade, an SLLogCollector run, etc.), this would make it hard to determine whether a BPA test had failed or not.
From now on, the Standalone BPA Executor tool will return one of the following exit codes when issues were detected:
| Exit code | Description |
|---|---|
| 1 | Unexpected errors have occurred. |
| 2 | BPA tests have detected issues. |
DataMiner Object Models: SLDataGateway will now try to read only the selected fields from a STaaS database [ID 45503]
When SLDataGateway is retrieving DOM data from a STaaS database, from now on, it will attempt to retrieve only the selected fields using the native field projection capabilities of these databases. This will considerably enhance data transfer efficiency and overall performance.
This optimization will leverage the indexed field values to avoid transferring complete objects when only specific fields are needed.
If selected field retrieval is not supported by the database, the system will automatically fall back to retrieving the full object and extracting the required values.
By default, the value type will be the field type defined by the exposer. When a field value is explicitly requested, the type defined in the field descriptor will be used instead.
Important
To ensure correct type resolution, field descriptor IDs must be unique across all section definitions within a DOM module. Non-unique IDs may result in incorrect type mapping and unexpected behavior.
Database migration from Cassandra Cluster to STaaS is now allowed on systems with Swarming enabled [ID 45507]
From now on, it is possible to migrate the database of a Swarming-enabled system from Cassandra Cluster to STaaS.
Note
- This migration will be a snapshot migration, not a live migration.
- Migrating the database will only be possible if the system is online, cloud-connected, and has an active Cassandra Cluster database.
User-Defined APIs can now also be triggered by sending a PATCH request method [ID 45542]
To trigger a user-defined API, up to now, you had to send a GET, PUT, POST, or DELETE request method to the UserDefinableApiEndpoint DxM.
From now on, it will also be possible to trigger a user-defined API by sending a PATCH request method.
SLManagedScripting: AssemblyLoad event handler will also log the location of the loaded assembly [ID 45547]
From now on, the AssemblyLoad event handler in SLManagedScripting will also log the location of the loaded assembly (if available).
Automation: Script library hint paths will only be sent to the script compilation engine the first time they are required [ID 45560]
Previously, when a script library was added to a DataMiner System, its hint paths were automatically sent to the automation script compilation engine, even when the library was not used by any automation script.
From now on, script library hint paths will only be sent to the automation script compilation engine the first time they are required, i.e., when a script referencing the library in question (either directly or via another library) is executed for the first time.
SLNetClientTest tool: Enum field dropdown boxes in 'Build Message' tab will now be sorted alphabetically [ID 45610]
Up to now, each enum field dropdown box in the Build Message tab would show the enum values in the order in which they are defined in the enum.
In order to make it easier to look up values when, for example, building a message, from now on, the enum field dropdown boxes in the Build Message tab will show the enum values in alphabetical order.
Caution
Always be extremely careful when using the SLNetClientTest tool, as it can have far-reaching consequences on the functionality of your DataMiner System.
'Check Time Server' BPA test has now been merged with the 'DataMiner Agent Minimum Requirements' BPA test [ID 45631]
In order to combine all system requirements specified in DataMiner Compute Requirements, the Check Time Server BPA test has now been merged with the DataMiner Agent Minimum Requirements BPA test.
Note
From now on, the DataMiner Agent Minimum Requirements BPA test will be executed only once across the entire DataMiner System. The test results from the individual Agents in the cluster will be aggregated.
SLLogCollector: Extra logging and progress updates while files are being archived [ID 45650]
In some cases, SLLogCollector can get stuck while archiving files.
To improve visibility during archiving, SLLogCollector will now log which file is currently being archived and update the busy message with the number of files copied so far.
SLAutomation: Enhanced startup after a DataMiner restart or upgrade [ID 45651]
Up to now, after a DataMiner restart or upgrade, in some cases, SLAutomation could unexpectedly stop working while initializing internal components.
A number of enhancements have now been made to prevent any initialization issues during SLAutomation startup.
'DataMiner Agent Minimum Requirements' BPA test: Enhanced time server check on hybrid clusters [ID 45661]
When the 'DataMiner Agent Minimum Requirements' BPA test checked the time server settings on hybrid clusters (i.e., clusters that include DaaS Agents as well as self-managed Agents), the existing checks were too strict. DaaS Agents always use VM Time as time server, whereas self-managed Agents typically use the local domain controller as time server.
From now on, the BPA test will compare the server times of all Agents in the cluster:
- If the server times differ from 1 to 5 seconds, this will be flagged as a warning.
- If the server times differ more than 5 seconds, this will be flagged as an issue.
SLLogCollector: Users can now choose whether to use the 'Output pending calls' option [ID 45722]
Up to now, when you opened the SLLogCollector, the Output pending calls option would automatically be selected when any of the running processes have runtime errors linked to elements. Users would not have any control over this option. From now on, they will.
If you want SLLogCollector to collect all pending calls for a number of the specific elements, do the following:
Select the Output pending calls option.
Click Load elements, and select all elements of which you want the pending calls to be collected.
Elements with runtime errors will be automatically selected.
Note
- The Output pending calls option will still automatically be selected when any of the running processes have runtime errors linked to elements.
- Clearing the Output pending calls option will only hide the element selection grid. The current selection will not be cleared, so when you select the Output pending calls option again, everything is restored without any need to reload the elements.
Cassandra Cluster Migrator tool now supports migrating Credentials Library credential types [ID 45824]
The Cassandra Cluster Migrator tool (SLCCMigrator.exe), which migrates data to Cassandra Cluster from MySQL or Cassandra Single, now also supports migrating credential types that inherit from ACredentialConfig, i.e., all credential types that can be created in the Credentials Library.
Automation: Improved save logic for automation scripts [ID 45836]
A number of enhancements have been made to the save logic of automation scripts:
- A per-script execution reference is now kept, so deletion of an in-use script DLL is deferred until all script executions have ended.
- When a script is updated while another instance is still running, a new DLL is created as before, while the old DLL is kept until the running instance finishes.
- Local save logic no longer deletes DLL files that were triggered by its own file-change event.
- A newly saved script now waits until its (re)compilation is complete before it is executed.
CloudFeed DxM has been upgraded to Microsoft .NET 10 [ID 45849]
The CloudFeed DxM has been upgraded to Microsoft .NET 10.
SLLogCollector will now automatically be configured to include a memory dump of SLPort and SLSNMPManager when a runtime error was detected in SLProtocol [ID 45865]
From now on, when you open the SLLogCollector tool, the tool will automatically be configured to include a memory dump of the SLPort and SLSNMPManager processes when a runtime error was detected in SLProtocol.
Enhanced performance when upgrading the ModelHost DxM [ID 45967]
Because of a number of enhancements, overall performance has increased when upgrading the ModelHost DxM.
ModelHost DxM has been upgraded to Microsoft .NET 10 [ID 45988]
The ModelHost DxM has been upgraded to Microsoft .NET 10.
DOM: Server-side support for string list FieldDescriptors [ID 46051]
When using DOM in scripts, ad hoc data sources, etc., from now on, it will be possible to specify a List<string> type on a normal FieldDescriptor. Up to now, only single fields were allowed. Now, multiple string values will also be supported.
UserDefinableApiEndpoint DxM has been upgraded to Microsoft .NET 10 [ID 46066]
The UserDefinableApiEndpoint DxM has been upgraded to Microsoft .NET 10.
DataMiner upgrade: Legacy NAS and NATS services and files would not be removed [ID 46094]
Up to now, a DataMiner upgrade could leave behind the legacy NAS and NATS services as well as the C:\Skyline DataMiner\NATS folder.
From now on, on systems that have already been upgraded successfully to a DataMiner 10.6 version at some point in time, a new upgrade action named CleanupNatsServices will make sure these legacy services and that folder are removed. This ensures that the BrokerGateway-managed NATS solution can be used without the obsolete components.
DataMiner Taskbar Utility: Event colors now align with DataMiner Cube [ID 46130]
The colors used by the DataMiner Taskbar Utility for upgrade events now align with the colors used by DataMiner Cube. This makes it easier to identify the status of events such as Finished, Success, LocalComplete, UploadComplete, UpgradeComplete, Notice, and Error.
Load, save, and delete actions for services have been rerouted from SLXml to the StorageModule DcM [ID 46134]
In preparation of service swarming, all load, save, and delete actions for services have been rerouted from SLXml to the StorageModule DcM.
Automation: GetAvailableAutomationScripts now returns additional script information [ID 46140]
The GetAvailableAutomationScripts call now returns the following additional information for each script:
IsInteractive: Indicates whether the script can show UI elements.CanBeExecuted: Indicates whether the script can be run on its own. Scripts that only contain reusable libraries returnfalse.
User-Defined APIs: IIS rewrite rules are now validated and repaired by the UserDefinableApiEndpoint DxM [ID 46143]
The UserDefinableApiEndpoint DxM now owns the IIS rewrite rule that reroutes requests sent to /api/custom to the endpoint. It now validates the rule when the process starts and keeps checking it while the service runs, repairing it automatically if needed.
If the rewrite rule is missing, disabled, or no longer matches the expected routing behavior, the DxM will restore it with the correct configuration. This ensures that user-defined API requests keep working even if the IIS configuration has been changed outside the installer.
Scheduler: SkipStartedInformationEvent is now returned when retrieving scheduled tasks [ID 46161]
When you retrieve scheduled tasks using a GetInfoMessage with type set to "SchedulerTasks", the returned AutomationScriptInstance will now include the SkipStartedInformationEvent property.
This will allow you to verify whether the property was enabled when the scheduled task was saved.
Jobs module: All server-side code has now been removed from the code base [ID 46163]
The Jobs module has been end-of-life since DataMiner 10.5.0. All server-side code related to this module has now been removed from the code base.
CloudStorageMigrationFinalize script will now migrate all credentials stored in the Credentials Library [ID 46204]
The CloudStorageMigrationFinalize script, which should be run when migrating existing data to STaaS, will now migrate all credentials stored in the Credentials Library.
DataMiner backup: A default description is now generated when no description is specified [ID 46206]
When you create a backup without specifying a description, DataMiner will now generates one automatically.
The description will include the name of the predefined backup setting and the DataMiner ID, matching the behavior of the DataMiner Taskbar Utility.
User-Defined APIs: Optional notice generation when token rate limits are reached [ID 46244]
On ApiToken objects, you can now enable notice generation when a token reaches its configured rate limit by setting ApiTokenRateLimit.GenerateNotice to true.
When enabled, one notice can be generated per token when its rate limit is reached. Notices are not cleared automatically. If you clear a notice manually and the token hits its rate limit again, a new notice can be generated.
Swarming: Alarm ID usage analysis can now be skipped when enabling swarming [ID 46340]
When enabling swarming using an EnableSwarmingRequest, you can now skip the analysis of alarm ID usage by setting AnalyzeAlarmIDUsage to false, similar to a SwarmingPrerequisitesCheckRequest.
By default, the analysis will still be performed. Skipping it can considerably speed up the request, but you should only do so if you have already analyzed and resolved any alarm ID usage beforehand.
SLScripting executable and dependencies now stored in a separate folder [ID 46346]
The SLScripting.exe executable and its dependencies are now stored in C:\Skyline DataMiner\Files\SLScripting\x86 instead of C:\Skyline DataMiner\Files.
This reduces the risk of QActions loading assemblies from C:\Skyline DataMiner\Files instead of using the assemblies provided by their specific NuGet dependencies.
If an assembly cannot be found, C:\Skyline DataMiner\Files is still used as a fallback folder.
SRM: Reservation instance property updates are now performed by the DMA hosting the booking [ID 46534]
Previously, when a ReservationInstance (booking) property was updated, the SRM Master DMA performed the update regardless of which DMA received the request. On large or heavily loaded clusters, this could make the master a bottleneck.
From now on, the DMA hosting the booking will perform the property update. Before the update, the SRM Master DMA grants a short-lived lock for the booking to coordinate concurrent updates. This reduces the processing load on the master and improves the performance and scalability of property updates, particularly on larger clusters.
Property updates will continue to be validated and applied in the same way, and other DMAs and clients will still be notified. This change does not affect end-user or scripting behavior.
SNMP: Empty community strings are now supported for SET operations [ID 46535]
When the SnmpPollingSnmpPlusPlusOnly soft-launch option is enabled, you can now use an empty community string for SNMP SET operations.
SLLogCollector now lists files in the Scripts folder [ID 46545]
Log Collector packages now include a Scripts.txt file listing the files in C:\Skyline DataMiner\Scripts and its subfolders, excluding .txf files. For each file, it includes the creation date as recorded on the system and the last modified date.
STaaS traffic can now use a single hostname and IP address [ID 46570]
All STaaS traffic from DataGateway will now pass through a single endpoint per region. This will allow you to whitelist a single hostname (https://*.dataminer.services/) or a single IP address per region for STaaS traffic, without having to request additional hostnames or Microsoft Azure IP addresses from support.
If this single endpoint is not reachable, DataMiner will continue to use the existing endpoints.
SLLogCollector now collects additional Elasticsearch and OpenSearch cluster information [ID 46618]
SLLogCollector now collects additional diagnostic information from configured Elasticsearch and OpenSearch clusters, including aliases, shard health and placement, disk allocation, cluster settings, ongoing recoveries, and pending cluster tasks.
The generated package now includes the following files in the Elastic folder for the configured database cluster:
_cat.aliases.txt_cat.shards.txt_cat.allocation.txt_cluster.settings.json_cat.recovery.txt_cat.pending_tasks.txt
Protocol: NotifyDataMiner(Queued) failures are now logged without internal offsets [ID 46709]
When a NotifyDataMiner(Queued) method invoked through the SLProtocol interface failed, up to now, the log included the internal offset added to the notify type.
From now on, the log will show the original notify type without the offset.
STaaS: Support for direct-write-only entity types [ID 46711]
DataGateway can now handle STaaS entity types configured for direct writes only, without an Event Hub configuration. This allows blob storage data types to be written directly through the Ingest API instead of Event Hub.
Automation: Clearer error messages when saving scripts [ID 46713]
Error messages returned when saving an automation script now provide more details about what went wrong.
For example, when you import a script in DataMiner Cube and a dummy references an unavailable protocol or protocol version, the error message will now identify the dummy, protocol, and version instead of showing a generic error.
TCP server ports: Multiple elements can now receive data from the same allowed IP address [ID 46784]
When multiple elements listen on the same TCP server port and explicitly list a client's IP address in their allowed IP addresses, all of those elements will now receive the data sent by that client. Previously, only one element would receive the data.
Only one element can still respond to the client. This enhancement is intended for scenarios where multiple elements need to receive data without responding.
If an element explicitly lists a client's IP address as allowed, elements that do not explicitly list that IP address will still not receive data from that client.
SLScripting can no longer run as a service [ID 46869]
From now on, SLScripting will no longer be able to run as a service. It will always run as a server instead.
GQI: GQI via SLHelper disabled by default [ID 46927]
GQI via SLHelper is now disabled by default in favor of the GQI DxM. Legacy GQI requests will return an error directing you to use the GQI DxM instead.
As a temporary fallback, you can re-enable GQI via SLHelper by adding the following option to the SLNet section of C:\Skyline DataMiner\SoftLaunchOptions.xml and restarting DataMiner:
<SLNet>
<EndOfSupport.SLHelperGQI>true</EndOfSupport.SLHelperGQI>
</SLNet>
The legacy GQI implementation in SLHelper will be removed completely in a later version.
BrokerGateway: Increased timeout for applying manual configurations [ID 46949]
The fixed timeout for the BrokerGateway applymanualconfig call has been increased from 5 minutes to 30 minutes.
DataMiner upgrade: Prerequisite check for the end of SLHelper GQI support [ID 46957]
A new upgrade prerequisite will check whether DataMiner Agents running a version older than 10.7.0 are ready for the end of support for GQI via SLHelper. It will check two independent requirements:
- The Web API must use the GQI DxM. If the effective
gqi:useDxMsetting isfalse, the upgrade will be blocked. - There must be no GQI log activity within the last 30 days, unless the
EndOfSupport.SLHelperGQIsoft-launch option is enabled to temporarily allow continued use of GQI via SLHelper. Otherwise, the upgrade will be blocked.
The prerequisite will report detected issues and inspection errors together with corrective actions. Enabling the soft-launch option will not bypass the Web API requirement.
The check will be skipped on DataMiner Agents already running version 10.7.0 or higher.
DataMiner upgrade: Prerequisite checks for End of Support and End of Life features [ID 46984]
DataMiner upgrades to version 10.7.x will now check for features that have reached End of Support or End of Life.
End of Support features
If any of the following features is in use, the upgrade will be blocked unless its corresponding case-sensitive soft-launch option is set to true in SoftLaunchOptions.xml:
| Feature | Soft-launch option |
|---|---|
| MySQL as the main database | EndOfSupport.MySQL |
| Elasticsearch 6.8 or earlier | EndOfSupport.Elastic |
| Cassandra 3.x or earlier | EndOfSupport.Cassandra3 |
| Atlassian Crowd authentication or user and group management | EndOfSupport.Crowd |
| RADIUS authentication | EndOfSupport.RADIUS |
End of Life features
The upgrade will be blocked if either of the following configurations is present:
- .NET Remoting explicitly enabled in MaintenanceSettings.xml for communication between DataMiner Agents or between DataMiner Cube and SLNet.
- A two-site redundant indexing cluster (EMCO).
These checks have no soft-launch override. Remove or migrate these configurations before upgrading.
DataMiner startup: MySQL requires an explicit End of Support override [ID 47000]
From now on, a DataMiner Agent using MySQL as its main database will no longer start unless the EndOfSupport.MySQL soft-launch option is set to true. If the option is missing or not set to true, DataMiner will stop and log an error.
To temporarily continue using MySQL, add the following case-sensitive option to C:\Skyline DataMiner\SoftLaunchOptions.xml and restart DataMiner:
<EndOfSupport.MySQL>true</EndOfSupport.MySQL>
Consider migrating to Cassandra Cluster or Storage as a Service (STaaS) instead.
SLNet: Support for .NET Remoting removed [ID 47004]
Support for .NET Remoting, which has reached End of Life, has been removed from SLNet.
The legacy .NET Remoting connection option has also been removed from the SLNetClientTest tool.
In SLNetTypes, related settings and methods have been marked as obsolete. They remain available for clients that need to connect to older DataMiner servers that still support .NET Remoting.
See also: DataMiner upgrade: Prerequisite checks for End of Support and End of Life features [ID 46984]
Security: Atlassian Crowd authentication is no longer supported by default [ID 47014]
From now on, Atlassian Crowd authentication is no longer supported by default. This includes authenticating users against a Crowd server and importing users and groups from a Crowd server.
If Crowd is configured as the external authentication method in DataMiner.xml (<ExternalAuthentication type="CROWD">) and the EndOfSupport.Crowd soft-launch option is not set to true, the DataMiner Agent will log the reason and stop during startup. Without this override, saving Crowd external authentication settings will also be rejected.
To temporarily continue using Atlassian Crowd, add the following case-sensitive option to C:\Skyline DataMiner\SoftLaunchOptions.xml on every DataMiner Agent that uses Crowd, and restart DataMiner:
<SLNet>
<EndOfSupport.Crowd>true</EndOfSupport.Crowd>
</SLNet>
Security: RADIUS authentication is no longer supported by default [ID 47018]
From now on, RADIUS authentication is no longer supported by default. This includes authenticating users against a RADIUS server.
If RADIUS is configured as the external authentication method in DataMiner.xml (<ExternalAuthentication type="RADIUS">) and the EndOfSupport.RADIUS soft-launch option is not set to true, the DataMiner Agent will log the reason and stop during startup. Without this override, saving RADIUS external authentication settings will also be rejected.
To temporarily continue using RADIUS, add the following case-sensitive option to C:\Skyline DataMiner\SoftLaunchOptions.xml on every DataMiner Agent that uses RADIUS, and restart DataMiner:
<SLNet>
<EndOfSupport.RADIUS>true</EndOfSupport.RADIUS>
</SLNet>
DataMiner start-up: Cassandra 3.x and earlier require an End of Support override [ID 47024]
From now on, a DataMiner Agent using Cassandra 3.x or earlier as its main database will no longer start unless the EndOfSupport.Cassandra3 soft-launch option is set to true. If the option is missing or not set to true, DataMiner will stop and log an error. Creating a migration target that uses a Cassandra 3.x or earlier will also be blocked without this override.
To temporarily continue using a Cassandra 3.x or earlier, add the following case-sensitive option to C:\Skyline DataMiner\SoftLaunchOptions.xml and restart DataMiner:
<EndOfSupport.Cassandra3>true</EndOfSupport.Cassandra3>
Connectors: dllName and DirectConnection are no longer supported by default [ID 47028]
The following connector features have reached End of Support and are now disabled by default:
- The
dllNameoption in theoptionsattribute of a QAction. - Logger tables of type
DirectConnection.
During a DataMiner upgrade, the new VerifyEndOfSupportConnectors prerequisite check will block the upgrade if it detects connector versions that use either feature, unless the corresponding soft-launch option is enabled.
Before upgrading, configure affected elements to use connector versions that no longer contain these features, and remove detected connector versions that are no longer in use.
If no compatible connector version is available, you can continue using an affected connector by activating the corresponding soft-launch option before upgrading:
EndOfSupport.DllNamefor thedllNameoption.EndOfSupport.DirectConnectionfor logger tables of typeDirectConnection.
After the upgrade, uploading and using a connector with either feature will cause its elements to fail to start unless the corresponding soft-launch option is enabled.
Note
The prerequisite check also detects JScript and VBScript QActions. These have reached End of Life and have no soft-launch override. See also QActions: JScript and VBScript are no longer supported [ID 47010].
DataMiner startup: Elasticsearch requires an explicit End of Support override [ID 47033]
From now on, a DataMiner Agent using Elasticsearch as its search database will no longer start unless the EndOfSupport.Elastic soft-launch option is set to true. If the option is missing or not set to true, DataMiner will stop and log an error. Creating a migration target that uses Elasticsearch as its search database will also be blocked without this override.
To temporarily continue using Elasticsearch, add the following case-sensitive option to C:\Skyline DataMiner\SoftLaunchOptions.xml and restart DataMiner:
<EndOfSupport.Elastic>true</EndOfSupport.Elastic>
Consider migrating to OpenSearch or Storage as a Service (STaaS) instead.
User-Defined APIs: Requests now routed through API Gateway [ID 47107]
The UserDefinableApiEndpoint DxM now registers its /api/custom route with the API Gateway at startup. Requests to this route are now proxied through the API Gateway instead of relying on an IIS URL Rewrite rule.
The DxM no longer creates, validates, or repairs the IIS rewrite rule. Existing rules are left unchanged and can still route unencrypted HTTP requests on existing deployments. New deployments do not receive a rewrite rule and only support triggering APIs over HTTPS.
By default, the module registers with a module-specific rate limit of 6000 requests per minute. To configure a different limit:
Add the following setting to appsettings.custom.json, adjusting the value as required:
{ "ApiGatewayRegistration": { "RateLimitPerMinute": 3000 } }Restart the DataMiner UserDefinableApiEndpoint service.
The API Gateway request inactivity timeout is set to the configured NATS timeout plus 5 seconds, allowing the endpoint's timeout error response to reach the caller.
Important
This UserDefinableApiEndpoint version requires API Gateway 0.11.0 or later, which supports module-specific rate limits. With an older API Gateway version, the default shared limit of 60 requests per minute will also apply to user-defined API triggers. Also, with an older API Gateway version, the API Gateway request inactivity timeout will be set to 100s.
Remaining legacy Annotations reference removed [ID 47122]
The following remaining reference to the legacy Annotations module, which has reached end of life, have been removed:
- ISAPI filtering no longer takes
/annotations/into account.
Fixes
SLAnalytics would not receive 'swarming complete' notifications for swarmed DVE child elements [ID 43984]
Up to now, SLAnalytics would incorrectly not receive any "swarming complete" notifications for swarmed DVE child elements. As a result, alarm focus calculations for DVE child elements would be restarted from scratch instead of being fetched from the database.
Service & Resource Management: A capability could incorrectly be set to a null value [ID 44125]
In some cases, a capability could incorrectly be set to a null value.
From now on, when a capability is booked, it will no longer be possible to set its value to null.
Failover: Problem when reloading the scheduled tasks [ID 44234]
After a Failover switch, in some cases, the new online agent would incorrectly not reload the scheduled tasks that the former online agent had in memory.
SLAnalytics: Flatline anomaly alerts would incorrectly not be triggered for parameters that are only updated once every 24 hours [ID 45033]
Up to now, flatline anomaly alerts would incorrectly not be triggered for parameters that are only updated once every 24 hours.
SLLogCollector: Problem when running BPA tests [ID 45053]
When the SLLogCollector tool was configured to execute all BPA tests available in the system when collecting log packages, up to now, in some cases, executing those BPA tests would fail and cause them to report a wide variety of exceptions.
From now on, when the SLLogCollector tool detects that it is not possible to execute the BPA tests, it will skip their execution and collect the results of their last successful run.
An alarm will now be generated when a protocol connection acting as a server failed to bind to the socket [ID 45241]
When a protocol connection that acted as a server failed to bind to the socket during startup, up to now, this would only get logged (with debug level 1). From now on, this will be assigned error level 0.
Also, the element will go into an error state, and an alarm indicating a failing binding will be generated.
Service & Resource Management: Problem when the Agent with the lowest DMA ID was removed from a DataMiner System [ID 45281]
Up to now, when the Agent with the lowest DMA ID had been removed from a DataMiner System, the Resource Manager would incorrectly still consider the removed Agent the master DMA and would still attempt to communicate with it. As a result, master synchronization requests would fail, producing errors like the following one:
System.AggregateException: One or more errors occurred. ---> Skyline.DataMiner.Net.Exceptions.DataMinerException: Fatal error while sending request [MasterSyncRequestMessage for message of type SetReservationInstanceMessage from XXX] to master DMA XXX, max retries reached. ---> Skyline.DataMiner.Net.MasterSync.MasterSyncerException: Could not use the connection to master DMA XXX
From now on, when the Agent with the lowest DMA ID was removed from the DataMiner System, the Resource Manager will correctly re-evaluate and update the master DMA when it receives a master synchronization request.
SLNet/SLDataGateway: Paging requests via SLNetInternalRepository could fail when the paging cookie expired mid-session [ID 45550]
In some cases, paged retrievals of DOM instances or booking instances could fail with an InvalidOperationException when the server-side paging cookie expired before all pages were fetched. In GQI-powered low-code apps, this could then surface as a random error:
Select failed, could not read the objects from the database: System.InvalidOperationException: The provided cookie was not found among the live paging handlers of this storage type. Maybe it has already been deleted.
From now on, SLDataGateway will gracefully reset an expired paging cookie instead of throwing an error. When the cookie is no longer found among the live paging handlers, a fresh paging session will automatically be started.
Also, SelectPagingHelper will now maintain a set of all object IDs received across pages. When a paging session restarts due to a cookie renewal, previously returned objects are filtered out, preventing duplicates from being returned.
Automation: Problem with dependency order when recompiling script libraries [ID 45673]
Up to now, when a script library was updated, the dependency order was always assumed to be correct. However, in cases where libraries were loaded in a different order, a library could be recompiled before one of its dependencies.
For example, when Library A depended on Library B, and Library B was recompiled after Library A, then Library A would remain linked to an older version of Library B. This would cause an issue when, after the DataMiner Agent was restarted, the outdated DLLs were removed. Library A would then reference a DLL file that no longer existed.
From now on, the recompilation flow will ensure that libraries are recompiled in the correct dependency order, preventing references to outdated dependency versions.
When DataMiner was stopped, the SLAnalytics process could get stuck while being stopped [ID 45910]
When the DataMiner software was stopped, in some cases, the SLAnalytics process could get stuck while being stopped.
StorageModule DxM would fail to start because of a WebSocket issue [ID 45933]
Because of a WebSocket issue, in some rare cases, the StorageModule DxM would fail to start. As a result, DataMiner would not be able to start up.
SLAutomation could stop unexpectedly when Engine methods were used from different threads [ID 45955]
In some cases, SLAutomation could stop unexpectedly when automation scripts used Engine methods from different threads at the same time.
This was caused by non-thread-safe access to cached element information, e.g., when engine.FindElement and engine.CreateExtraDummy were called concurrently.
Access to that cache has now been made thread safe.
Note
The Engine object itself is still not thread safe. Scripts should not use the same Engine instance from more than one thread at a time.
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.
ManagerStore: Fixed limit logic when adding objects from the DatabaseCacheLayer [ID 46205]
When DOM reads were executed, the result from the database could be enriched with objects that were still present in the DatabaseCacheLayer. This cache keeps recently written objects available before they are fully indexed in the database, but in some cases it did not correctly keep the configured query limit in mind when paged reads were carried out.
This could cause more objects than expected to be returned in the result, especially when data was still available in the cache for a later page. The limit is now reapplied correctly when objects are added from the DatabaseCacheLayer, and the number of objects already returned on previous pages is tracked correctly.
This fixes the issue for paged DOM reads with a configured limit, ensuring the returned result always respects the requested limit even when cached objects are added to the response.
Spectrum preset update events did not work when the preset name contained a dot [ID 46241]
Up to now, the spectrum preset update event on parameter SPA_SPARAM_PRESET_UPDATE (PID 64216) could fail when the preset name contained a dot (.).
Existing behavioral change points could no longer be retrieved after a DataMiner Agent restart [ID 46271]
In some cases, after SLAnalytics had restarted, an existing change point on a parameter could no longer be returned once a new change point was detected on that same parameter.
This was caused by an internal ID collision. Change point IDs restart from zero after a restart, and the retrieval logic could incorrectly treat a new change point with a reused ID as a duplicate.
Change points are now also distinguished by creation time. As a result, previously detected change points remain retrievable after a restart.
Failover: NodeId in ClusterEndpoints.json could be cleared after an online agent restart [ID 46329]
Up to now, when the offline agent in a Failover setup was not running and the online agent was restarted, the NodeId field for the offline agent in ClusterEndpoints.json could be set to null.
From now on, the field will retain its existing value when it cannot be retrieved from the offline agent.
Automation scripts and QActions: An unsuitable DLL version could be selected from hint paths [ID 46412]
Up to now, when no exact DLL match was found in the hint paths while resolving assemblies for automation scripts or QActions, the first matching DLL was selected. This could result in an older, incompatible version being selected.
From now on, the highest compatible DLL version in the requested range will be selected. If no version in that range is available, the highest available version will be selected.
Automation: Script Runner could fail to load assemblies required by a script [ID 46443]
Up to now, Script Runner could fail to load a script when it depended on an assembly that was not copied to its dedicated assembly folder. This could happen for dependencies that were not anticipated, such as Skyline.DataMiner.Storage.Types.dll.
From now on, if an assembly cannot be found in C:\Skyline DataMiner\Files\SLAutomation.ScriptRunner, Script Runner will also look for it in C:\Skyline DataMiner\Files.
Change point history retrieval could cause overall performance to decrease [ID 46524]
Up to now, retrieving change point history could cause performance to decrease because change points stored under the deprecated (v1) change point custom data type were fetched and merged with data from the current store. DataMiner will now read change points exclusively from the current data store.
As a result, change points that were only ever written under the old v1 partition scheme will no longer be returned. This affects only pre-migration data; systems using the current change point storage format are unaffected.
STaaS: Failing aggregate count queries would incorrectly return 0 instead of throwing an exception [ID 46546]
On systems using STaaS, up to now, a failing aggregate count query could incorrectly return 0 instead of throwing an exception. From now on, the query will throw an exception when it fails.
Service & Resource Management: Resources with time-dependent capabilities could be ineligible when ignoring a booking [ID 46576]
When requesting eligible resources while ignoring a booking and its service definition node, a resource with a time-dependent capability could still be considered unavailable if it was used in that booking.
From now on, the Resource Manager will take ignored booking into account when determining whether such resources are eligible.
Spectrum: Measurement point cycle was not loaded when DONT_APPLY_SETTINGS was passed [ID 46630]
Up to now, when you loaded a preset with both the SPA_PRESET_DONT_APPLY_SETTINGS and SPA_PRESET_LOAD_MEASUREMENT_POINT_CYCLE flags, the measurement point cycle would not be loaded.
From now on, passing the SPA_PRESET_LOAD_MEASUREMENT_POINT_CYCLE flag will load the measurement point cycle regardless of whether the SPA_PRESET_DONT_APPLY_SETTINGS flag is also passed.
SLNet: Edge managers could fail to initialize when NATS was unavailable at startup [ID 46700]
Up to now, if NATS was unavailable when DataMiner started, the EdgeScriptedConnectorManager and EdgeNodeLifecycleManager could fail to initialize. From now on, both managers share a MessageBroker instance from MessageBrokerCache, created on the first request instead of during OnInitialize. This prevents a temporary NATS outage at startup from leaving the managers uninitialized.
Scheduler: Swarmed tasks could execute actions configured for another task [ID 46728]
Previously, editing a scheduled task that had been swarmed could cause action IDs to be reused. As a result, multiple scheduled tasks could reference the same action, causing one task to execute actions configured for another task.
Newly assigned actions will now be stored in the database using their complete IDs (DataMiner ID + action ID), ensuring that each action is uniquely identified. The legacy action ID columns will continue to be updated for downgrade compatibility.
Caution
- To correct scheduled tasks that were swarmed and edited in a version without this fix, recreate them in a version that includes the fix. Editing them again will not resolve the issue.
- This fix is not rolling compatible. Upgrade all DataMiner Agents to a version that includes this fix. Until all Agents have been upgraded, avoid editing scheduled tasks swarmed across Agents running older versions, as this could cause action IDs to be reused.
Visual Overview in web apps: SLHelper could stop responding after a session startup failure [ID 46744]
Previously, when Windows failed to create a window while SLHelper was starting a Cube session for a mobile visual overview, the automatic startup retry could leave the session in an invalid state. Cleaning up that session could then cause SLHelper to stop responding, blocking all mobile visual overview requests for all dashboards and users until SLHelper was restarted.
Each startup retry will now use a new, isolated environment, and a session will only be considered started once it is running. Cleaning up a failed or unresponsive session will no longer block SLHelper. If a session cannot be started after several attempts, only the mobile visual overview requesting that session will fail; other sessions will remain unaffected.
CCAEndpoint initialization is now retried after failures [ID 46752]
If initialization of CCAEndpointManager or CCAEndpointHandler fails, DataMiner will now keep retrying.
The retry scheduler will increase the delay between attempts up to a maximum of 60 seconds.
Failover: Memory and CPU spikes on offline Agents when updating services or elements [ID 46875]
When services or elements were updated in a DataMiner cluster, offline Agents in a Failover setup would experience a memory and CPU spike in the StorageModule process for each update. The size of the spike depended on the number of services and elements in the cluster.
Both online and offline Agents will now keep their XML-based services in memory at all times. The service cache in the StorageModule backend will only be reinitialized during a Failover switch or in exceptional circumstances.
DataMiner upgrade: SLNet garbage collection settings could be overwritten [ID 46905]
During a DataMiner upgrade, the <runtime> section of SLNet.exe.config was replaced with the version from the upgrade package. This could overwrite the machine-specific gcServer and GCHeapCount settings.
API Gateway: Missing proxy routes after a restart could cause persistent HTTP 404 errors [ID 46956]
After API Gateway restarted, requests to modules proxied through it could keep returning HTTP 404 errors. This could affect DataAPI, Orchestrator, Assistant, and EdgeManager.
Concurrent module registrations could overwrite newer routing configuration with an older snapshot, leaving proxy routes missing. Routing configuration updates are now processed sequentially to prevent this.
User-Defined APIs: Endpoint startup could be blocked when NATS was unavailable [ID 46997]
The UserDefinableApiEndpoint DxM could remain blocked during startup when the NATS service was unavailable. As a result, API callers would not receive a response explaining the connection failure.
The endpoint will now start while its NATS connections are being established. API triggers received before the message broker is initialized will return HTTP 503 with error code 1006 and the message "Service not ready yet, try again later."
Connection attempts will continue in the background. Once NATS is available and initialization succeeds, API triggers will be forwarded normally and cloud status reporting will resume.
Automation: Script Runner could load an incorrect assembly version [ID 47069]
Previously, Script Runner searched the protocol scripts folders by default. An assembly in one of these folders could be loaded instead of the version explicitly referenced by a script.
From now on, Script Runner will no longer add C:\Skyline DataMiner\ProtocolScripts or C:\Skyline DataMiner\ProtocolScripts\DllImport as default assembly hint paths. Script-specific references will take priority, with C:\Skyline DataMiner\Files remaining the fallback.
Important
If a script executed by Script Runner needs a DLL from either protocol scripts folder, you must add an explicit reference to that DLL in the script. These folders will no longer be searched automatically.