Are there any changes in the new way to generate driver packages (.dmprotocol) that makes a 9.5 system incompatible, throwing a message that says Unable to Upload DMProtocol "XXXXXXXX": No License for encrypted protocol found
Hi Edson,
can you also check if the protocol you are using meets the "minimum DMA version"?. I had a similar error message and it was due to the fact that the driver required a specific minimum DMA version which was not met.
Johan, Edson, indeed, incorrectly, the minimum version check throws the error you encounter. We’ll have to fix this to avoid more confusion.
Hi Johan, Jan,
In my testing case, the minimum version specified in the driver was lower than the DMA version. The Driver was 9.5.3, The DMA 9.5.0.0-8368
Edson, the problem you encounter is probably because encrypted drivers are only allowed on DataMiner with a specific protocol list.
Some background:
We have 3 'types' of protocol deployments:
- Fully open protocols
- Signed protocols
- Encrypted protocols
In this protocol context we also have 2 types of DataMiner licenses:
- A DataMiner that allows all protocols (default)
- A DataMiner that only allows specific protocols
The first, default DataMiner type, can run any 'fully open protocol' and 'Signed protocol'. The second version with a specific protocol list, can only run 'signed protocols' and 'encrypted protocols' which are licensed in the specific list.
Hi Edson,
I have the feeling that the license of the Agent only allows certain protocols. Would it be possible to verify that the protocol that you want to upload isn't mentioned in the license?
Hi Jens,
I installed the 9.5 CU15 locally and got the error, so the license should not be the problem.
Hi Edson,
Let me ask the obvious question here first, is the protocol you are trying to upload actually allowed to be installed on the system .i.e. is it present in the license of that user? (DataMiner > About > license)
Hi Jelle,
I’ve seen that in other systems that’s why I installed the 9.5 CU15 locally and got the error, so the license should not be the problem.
The issue was fixed by upgrading the system to 9.5 CU17 or 9.6 CU5, more info can be found at the release notes of Dataminer 9.6 under ID DMS RN 1089