What are the possible causes for ending up with a DMA ID = 0 or -1 during the installation process of subscription licenses?
Is it only failing to complete the steps beyond step 2, or are there other causes to consider that can lead to an invalid ID?
If possible, a consolidated list of causes may help in troubleshooting related license issues.
Hi Jordy,
DMA ID = -1 is the initial value on a fresh install. If it remains on that value, it means registration either never occurred, or failed.
The easiest way to asses what went wrong, is looking at the configurator log file in C:\Skyline DataMiner\logging\ConfiguratorTool. There you can find all steps executed, including any calls that are sent to the registration server, along with the responses.
Some reasons could be:
- The provided API key is invalid
- The dms name and/or url are already in use
- The dms name and/or url are too long (should not exceed 30 characters)
The above is however checked in the configurator, which means they should effectively block configuration before anything is done. Which means it is actually very unlikely these would cause a successful configurator run that leads to a -1.
Other reasons why you would not get a valid DMA ID:
- There was a problem registering the DMS on the dataminer.services Cloud Platform
- There was a problem fetching the Cloud Tokens
- There was a problem registering STaaS
Ending up with a DMA ID = 0 seems odd though. Do you have an example of such a case?