Hi,
We recently upgraded our testing environment to DataMiner v10.5 (self-hosted databases). The connection to Cassandra and OpenSearch was established successfully. However, we are encountering an issue with the monitoring protocol “Apache Cassandra Cluster Monitor V1.0.2.8”, where we are unable to connect to the hosts.
We are receiving the following errors:
2026/02/25 11:07:17.643|CSN2.txt|SLProtocol - 16948 - CSN2|2156|CManagedScript::Load|ERR|-1|Compilation failed for QAction 1
(4053,8): error CS0246: The type or namespace name 'ApacheCassandraCluster' could not be found (are you missing a using directive or an assembly reference?)
(4055,26): error CS0246: The type or namespace name 'ILoadBalancingPolicy' could not be found (are you missing a using directive or an assembly reference?)
(4061,32): error CS0246: The type or namespace name 'Host' could not be found (are you missing a using directive or an assembly reference?)
(4061,10): error CS0246: The type or namespace name 'HostDistance' could not be found (are you missing a using directive or an assembly reference?)
(4071,25): error CS0246: The type or namespace name 'Host' could not be found (are you missing a using directive or an assembly reference?)
The Cassandra monitoring protocol was working properly on previous DataMiner versions (10.2 and 10.3).
Additionally, we have the OpenSearch monitoring protocol deployed, which is working without any issues.
Note: Cassandra and OpenSearch are deployed on same Linux host
Hi Robin,
The types that are mentioned in the errors are from the SLC.CLib.Apache.CassandraDriver assembly. Can you verify that on the Agent where the element is created, this assembly is present in either:
- C:\Skyline DataMiner\ProtocolScripts\DllImport\slc.clib.apache.cassandradriver\1.0.0.1\lib\net462\SLC.CLib.Apache.CassandraDriver.dll
- C:\Skyline DataMiner\ProtocolScripts\slc.clib.apache.cassandradriver\1.0.0.1\lib\net462\SLC.CLib.Apache.CassandraDriver.dll
If the assembly is not present, you might want to reinstall the connector from the catalog.
What could have caused this is that the connector got installed on another Agent and the assemblies did not get synced (because in older DataMiner versions, the assemblies got installed in the C:\Skyline DataMiner\ProtocolScripts directory (which does not get synced) whereas in newer DataMiner versions, the assemblies get installed in the C:\Skyline DataMiner\ProtocolScripts\DllImport directory which does get synced).