The GUM “Load Policies” not working on Windows Server 2016

94 views
2
1 Comment

Hello,

I have an issue with the Generic Unsolicited Message Processor (GUM) protocol on a Windows Server 2016 DataMiner Agent.

The Load Policies button does not work on Server 2016, while it works correctly on another DataMiner Agent running on Windows Server 2026.

I compared both systems and found the following:

  • Both Agents are running exactly the same DataMiner version:
    • SLDataMiner: 10.5.2443.26402-793e45fa
    • SLNet: 10.5.2443.26832-d54e521b
  • The GUM Protocol.xml is identical on both systems (same SHA256 hash).
  • The GUM protocol requires the following dependencies:
    • Skyline.DataMiner.Core.DataMinerSystem.Protocol 1.1.1.8
    • Skyline.DataMiner.Core.DataMinerSystem.Common 1.1.1.8
  • On the working Server 2026 these dependencies are present under:
    C:\Skyline DataMiner\ProtocolScripts\DllImport\
  • On Server 2016 these 1.1.1.8 versions are completely missing from ProtocolScripts\DllImport.

The Server 2016 has other versions of these assemblies, for example 1.1.1.4, 1.1.1.10, 1.1.1.12 and 1.1.1.13, but not 1.1.1.8.

The QAction compilation on Server 2016 fails with errors such as:

<code>CS0234: The type or namespace name 'Protocol' does not exist in the namespace 'Skyline'

CS0234: The type or namespace name 'DataMinerSystem' does not exist in the namespace 'Skyline.DataMiner.Core'</code>

After the compilation failure, we also see:

<code>No CodeBuilder found</code>

The GUM Protocol.xml explicitly references the 1.1.1.8 dependencies.

I also checked the installed AppPackages, but none of the installed packages on the working Server 2026 appears to contain DataMinerSystem version 1.1.1.8. There is also no .dmprotocol package available on the server.

My question is:

What is the correct/recommended way to install or deploy the following dependencies on the Server 2016 DataMiner Agent?

<code>Skyline.DataMiner.Core.DataMinerSystem.Protocol.dll 1.1.1.8
Skyline.DataMiner.Core.DataMinerSystem.Common.dll 1.1.1.8</code>

Should they be installed through a specific DataMiner package, protocol package, DataMiner upgrade/hotfix, or another mechanism?

I would prefer not to manually copy the DLLs from the Server 2026 Agent unless this is an officially supported approach.

Thank you.

Br.

Jarek

Joaquim Almeida [SLC] [DevOps Enabler] Answered question
Miguel Obregon [SLC] [DevOps Catalyst] commented

Hi Jaroslaw,
I could not find this connector in the catalog. Can you provide us the link?

1 Answer

0
376 0 Comments

Hi Jarek,

This one was sorted out through a support ticket, so sharing the outcome here for anyone experiencing the same symptoms.

The missing DataMinerSystem 1.1.1.8 assemblies were not a DataMiner or Windows Server 2016 problem. Those DLLs belong to the DataMiner Class Library and are deployed automatically to C:\Skyline DataMiner\ProtocolScripts\DllImport when the connector that references them gets installed. There is no separate package, upgrade or hotfix that delivers them, and manually copying the DLLs from another Agent is not supported.

In this case, it turned out the wrong connector package file had been installed on the Server 2016 Agent. Reinstalling the connector using the correct package deployed the 1.1.1.8 assemblies, the QActions compiled again, and the GUM "Load Policies" button started working.

BR,

Joaquim

Joaquim Almeida [SLC] [DevOps Enabler] Answered question
You are viewing 1 out of 1 answers, click here to view all answers.