Hi, some troubleshooting tips that may help:

1. 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.
2. If deployed to the DMS as an Automation script, find the associated script in Cube > Automation and:
   1. 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".
   2. 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.
   3. 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.
   4. 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.

Let us know if you need further assistance.