NI TestStand
TestStand 2025 Q2 Property Loader example fails with "Method not found" in NI_PropertyLoaderLibrary
Small update.
The issue was temporarily fixed on the initial PC by reinstalling all NI software from scratch.
On the test PC, where the Property Loader had been working the whole time, it also stopped working after a controlled Windows restart.
So I now have two independent machines with similar Property Loader plugin failures.
Environment:
- TestStand version: 2025 Q2
- Windows versions:
- Windows 11 Pro, Build 26200.8655
- Windows 11 Business, Build 26200.8655
- TestStand bitness: 64-bit
- TestStand 2024 Q4 / 24.8 is currently still working
- LabVIEW versions/runtimes:
- 24.9 was installed when it stopped working
- updated to 25.5, still not working
- Property Loader example used:
C:\Users\Public\Documents\National Instruments\TestStand 2024 (64-bit)\Examples\Built-In Step Types\Property Loader Step Type\Property Loader - Loading Limits From a Database.seq
Additional observation:
It also fails when I try to load Excel files through the same TestStand/Property Loader workflow.
This worked before the PC was restarted and back on the initial pc that had the issue.
Question:
Is this a known issue with TestStand 2025 Q2 / 64-bit TestStand on Windows 11 Pro Build 26200.8655?
If this is a known issue, is there a patch, workaround, or recommended repair/re-registration step?
Attached are screenshots of the errors.
Error in Property Loader Source 'Source 0', function 'GetImportPropertyItems'
Could not load file or assembly 'NI_PropertyLoaderLibrary, Version=25.0.0.49152, Culture=neutral, PublicKeyToken=null'. Den angivne fil blev ikke fundet.
-17500; Operation Failed.
Step 'Property Loader' of sequence 'MainSequence' in 'Property Loader - Loading Limits From a Database.seq'
Hello to all
I have stille the same Problem with TS2026 Q3
Sequence File: C:\Users\Public\Documents\National Instruments\TestStand 2026 (32-bit)\Examples\Built-In Step Types\Property Loader Step Type\Property Loader - Loading Limits From a Database.seq
Realy strang is whe I do a "Unload All Modules" the the "roperty Loader - Loading Limits From a Database.seq" is running without any Error.
I think there is still no workaround?
I will report it to the NI Support.
Hello to all with this Problem
I have contactact NI Support about this prblem in TS2026 Q3 and i got this workaround. I tested it, and it does work. However, I’m not fully satisfied with this approach, because I have around 10–20 test sequences that use the PropertyLoader, and I would need to apply the workaround manually in each of them.
Answer from NI:
Our R&D is currently working on a fix for the next software release.
Hello to all with this Problem
If got an answer from NI how to integrat it in the Process Model to avoid to fix it in every Testsequence where Propertyloaders are used.
Maybe it helps someone. Thanks to NI for the fast support👍
Here the Solution from NI support:
My recommendation is to place this step inside the Process Model that you are currently utilizing. This way, you will have to modify only a few number of Process Model files, depending on how many you are currently using.
Follow these steps to complete this:
- To review the Process Model file that you are currently using, you can easily access it by double-clicking the process model name on the bottom status bar:
- To edit a Process Model, it is recommended to copy the default Process Model file(s) from the 1st directory to the 2nd directory:
1. <TestStand>\Components\Models\TestStandModels
2. <TestStand Public>\Components\Models\TestStandModels
Edit the required files under the 2nd, public directory. Files in the 2nd directory will overwrite the files in the 1st directory, ensuring that the original files from the 1st directory are unmodified. See: Modifying Process Model Sequence Files - TestStand User Manual for more information. - As an example, let's look at the SequentialModel Process Model. You can copy the workaround step into the ProcessSetup callback. It is empty by default. By copying the step into this callback sequence, it will be called automatically by the Process Model if your sequence file (referred to as the "Client Sequence") is using this modified Process Model.
Do you also get warnings in the analyzer ? regarding plugin id ?
Something like this:
Opening the plugin step forcing it to load manually clears the error in the analyzer.
I hope that they fix this in the 2027 version to avoid workarounds and also having a custom SequentialModel
