Cannot connect Systemlink Datafinder Instance in DIAdem

[zombae]

Hi, 

I am trying to decimate TDMS measurment files stored in the SystemLink server that are older than a Year by a factor of 10 

I have found the following ways of doing this :-

1. Write a Jupyter notebook to connect to a datafinder instance and run a analysis automation routine 

2. Create a Analysis automation routine in DIAdem and upload this as a  Analysis Automation Instance. 

3. Create a python script which downloads the files from SystemLink server using the SystemLink python API, decimate and reupload them.    

System configuration

VM(WIN 11) - running the SystemLink server V25 Q2 Patch 1.

Laptop (WIN 11)- running DIAdem v 25 Q4.

I am trying to get a DIAdem to connect to a Datafinder instance which I have created in my SystemLink server but I keep getting this error.

I have reviewed the following documentation :

Creating a datafinder instance.

https://www.ni.com/docs/en-US/bundle/systemlink/page/creating-configuring-data-indexing.html

Finding data from DIAdem and LabVIEW

https://www.ni.com/docs/en-US/bundle/systemlink/page/connecting-with-data-index.html?srsltid=AfmBOop...

Please me know of a better way of doing the task metioned above or any suggestion that might help me resolve the error mentioned above

P.S I get this reply when I ask nigel about this error. Tried all the steps didn't help

[Brad_Turpin]

Hi zombae,

When you say, "I have found the following ways of doing this", do you mean that you have tried each of these and they have all worked, or do you mean that these are ideas you've had, but you decided to pursue connecting DIAdem instead?

1. Write a Jupyter notebook to connect to a datafinder instance and run a analysis automation routine 

2. Create a Analysis automation routine in DIAdem and upload this as a  Analysis Automation Instance. 

3. Create a python script which downloads the files from SystemLink server using the SystemLink python API, decimate and reupload them. 

I see from the "_hierarchy" suffix in your error message that you are attempting a "blue" DataStore connection to the DataFinder from DIAdem.  Have you tried instead to connect to the DataFinder with the classic "yellow" DataFinder approach?

Can you open a Data Navigator page in SystemLink to that DataFinder?

What Workspace is the DataFinder associated with?  What are your permissions (Roles), as listed in the Access Control section of SystemLink, for that Workspace?

Brad Turpin

Principal Technical Support Engineer

NI / Emerson

[Brad_Turpin]

Hi again zombae,

If you want to perform this 10-fold decimation routinely on all data files that are > 1 year old, it does seem like using an Analysis Automation Procedure (either JupyterHub or DIAdem) would be best suited to make this happen.

Is there a use case that requires DIAdem to connect to the DataFinder?  If you just want to develop the code to create the *.anp file in DIAdem, you can manually copy a few > 1 year TDMS files into your local Search Areas for the My DataFinder that ships with DIAdem and use that to create the *.anp file.  That's actually the recommended approach, even more so than using the actual target DataFinder to create the *.anp file.

Brad

[ChrisFarmerWIS]

Hi Brad,

I'll jump in whilst Abhishek is busy - he'll reply later...

---

When you say, "I have found the following ways of doing this", do you mean that you have tried each of these and they have all worked, or do you mean that these are ideas you've had, but you decided to pursue connecting DIAdem instead?

---

These were ideas he had initially. But we decided to pursue Diadem as the customer does not presently have a TDM Analysis module license, so we were exploring the Diadem approach,

[zombae]

Hi Brad,

Can you open a Data Navigator page in SystemLink to that DataFinder?

Yes I am able to see the datafinder instance in the Data Navigator.

What Workspace is the DataFinder associated with?  What are your permissions (Roles), as listed in the Access Control section of SystemLink, for that Workspace?

The Datafinder is indexing all the work spaces. The account being used is the admin account which has access workspace owner role. I have now create a new role "Server Admin" and added all privilages to it. I will test it again and see if that changes anything. 

As Chris mentioned these are the ideas which I am trying to implement.

I see from the "_hierarchy" suffix in your error message that you are attempting a "blue" DataStore connection to the DataFinder from DIAdem.  Have you tried instead to connect to the DataFinder with the classic "yellow" DataFinder approach?  

I have tried to use the yellow My datafinder I dont have any issues with that. But I will need to overwrite the files stored on the server and that why I would like to connect to Datafinder instance running on the SystemLink server to find the files. As Chris mentioned the client doesnt currently have access to the TDM Analysis module. So I would like to run the script in DIAdem.

The error mentioned above comes on only when I follow the steps 

• In SystemLink, navigate to:
  Data Administration → Data Indexing → Dashboard → DataFinder Instances
• Select My Data → Connect → Export Client Configuration
• Export the .urf file to my PC.
• In NI DIAdem, go to Find → Open DataFinder Instance:
• Click Import, select the downloaded .urf file, and click Open:
• After the import completes, the instance appears in the list.
• Asks for the username and password, I tried the username that I setup in TDM configuration and the local windows account where the SystemLink Server is running
• Select the data and click OK — this is when the error occurs:

                    

I Also have a ticket open with NI Support and they have been able to replicate this issue on their end. 

[Brad_Turpin]

Hi zombae,

What is the ticket number that you have open?  I'd like to confer with whoever is handling that.  Any time you export a *.urf file, you get both a regular DataFinder option as well as the "_hierarchy" option added to the list, like this:

The regular option shows with a "yellow" cog icon, while the "_hierarchy" option shows with a "blue" cog.  These 2 options use separate connection technology, so that's why I'm wondering what happens when you choose the yellow option in DIAdem.

Brad

[zombae]

Hi Brad I only get the yellow cog option. 

I will email you the ticket number