Hi,
We've updated the NuGet in an automation script to a newer version and saved it as a compiled script in order to be sure that all dependencies will be uploaded to the DataMiner system.
When installing the script via the DataMiner Application Package we can see that everything is uploaded correctly and hitting the validate button results in 0 errors. However, when we try to run the script it throws System.MissingMethodExceptions.
The solution was to restart the SLAutomation process. Since we were using a staging environment this didn't really have an impact. However, we will have to deploy it to production some day and restarting the SLAutomation process in not desired since it could impact other components such as SRM.
Would there be an alternative? Or is this a known issue?
Server version : 10.3.8.0-13183
Client version : 10.3.2325.2012-78ede0fb
Launcher version : 10.3.2324.534-f6dadc78
Thanks in advance.
Kind regards,
After investigation, this is a combination of factors.
First, the NuGet 'A' that was referenced in the Automation script had a dependency on another NuGet package 'X'. However, another version of NuGet 'X' was also referenced in the Automation script. If you expose types from 'X' in NuGet 'A' (e.g. by providing a method that e.g. has as argument a type from 'X', then you can have the mentioned exception if the versions differ. More information can be found here.
Second, the fact that it worked after a DataMiner restart was due to the way default install script is currently implemented. A task has been created to update this behavior: https://collaboration.dataminer.services/task/227329.
Hi Jason,
I believe this relates to an issue we have encountered in the past where sometimes DataMiner is still linking and holding onto the old NuGet version. When you update everything validates fine but when executing it fails.
We have been working on a permanent fix, however, there is currently none and the workarounds consist of either restarting DataMiner (as you mentioned) or making sure that when you upload the new versions no other scripts are still pointing to the old version.
Feel free to get in touch if you need assistance with this issue @ support.data-acquisition@skyline.be.
Hi Joao,
In our case the script was using version 1.0.8-pre and we created a 1.0.8 version of that NuGet. So it’s dll name but they are not really the same as they are stored in 2 different folders.
Kind regards,
Although they could be in different folders when the code gets loaded into the process memory it is referenced by its assembly name and the full path becomes “secundary”. (see DCP203165)
The task (DCP203165) you’re referring to states that you could have duplicate assemblies loaded.
However version 1.0.8-pre and 1.0.8 are exactly the same so I assume it should be able to find that method since it was already there in version 1.0.8-pre.
Could it be that we are facing 2 different problems related to the same component/module?
It could be that the issue you are experiencing is not the same, but I still believe it could be related to the task I linked.
In the linked task, the issue is due to multiple versions being loaded into memory, and then when it comes time to select which one to use for the specific automation or connector it may not choose the correct one.
But probably the best is to reach out to our TechSupport team and DataAcquisition to investigate if the issues are related or a different thing we have not encountered before
Thanks for the intense investigation.