Hello,
I've recently implemented two new ad hoc data source scripts. They were successfully deployed and worked immediately on a system with a standalone DMA. However, upon deploying them to a DMS with two DMAs, I encountered an issue: these scripts are not appearing in the data source list when attempting to create a new query in a dashboard.
Both the standalone DMA and the DMS run the same DataMiner version. I'm aware that sometimes there's a delay before ad hoc data source scripts appear in the dashboard's data source list, but it has been over a day with no success.
Has anyone faced a similar issue or can offer insights on why these scripts are not available in the DMS environment? Any suggestions or troubleshooting tips would be greatly appreciated.
Thank you!
Hi, some troubleshooting tips that may help:
- Manually stop the SLHelper.exe process if it exists.
It will automatically start up again when needed and reload all the data source from scratch.
This could help when another old or invalid data source is loaded that prevents your ad hoc data source from being loaded correctly. - If deployed to the DMS as an Automation script, find the associated script in Cube > Automation and:
- Verify the code compiles on the DMS by clicking Validate at the bottom right of the C# code block.
You should get a validation popup saying "No errors". - Verify that in the Advanced options of the script, the "Compile as library with name" option is still checked and contains a valid library name.
- Verify that a build of the script is present in C:\Skyline DataMiner\Scripts\Libraries on both agents. There should be a file with format <script-name>.<library-name>.<timestamp>.R.dll.
If not, try making a small change to the script or its options, so you can click "Save script" again and trigger a rebuild. - If your script defines DLL references, make sure these can be found in C:\Skyline DataMiner\Files. There is a known issue that GQI does not correctly load assembly located in other places.
You can also use the Fusion Log tool on the SLHelper.exe application to investigate if there are any issues resolving assemblies.
- Verify the code compiles on the DMS by clicking Validate at the bottom right of the C# code block.
Let us know if you need further assistance.
Hi Santiago,
This is indeed a related known issue and the main reason why we could not allow loading assemblies from other places yet.
Currently, GQI uses the default load path to make sure only a single version of each assembly is loaded. This version will be deterministic, but requires that all data sources use that same version.
If we want to allow loading assemblies from other places, we need to make sure first that they are isolated, otherwise loading multiple versions of a data source could conflict with the framework and other data sources.
Hello Ronald,
Thanks for the tips. I found out the issue was because the scripts we already had in the system were on version 1.1.1.1 of Skyline.DataMiner.Core.DataMinerSystem.Common, but the new ones I added are using version 1.1.1.4.
I got everything working by making sure all scripts use the same version, either by updating the old ones to 1.1.1.4 or by changing the new ones to 1.1.1.1.
is this one of the known issues related to assemblies located in other places?