GetModelAbsolutePath Returns False on New Computer

Updated May 3, 2018

Reported In


  • TestStand

Issue Details

I moved my application to a new computer, and the engine call SeqFile.GetModelAbsolutePath method used in my custom user interface is now returning exists=false, when it didn't before.


1. Determine the path of the process model file is being used on the old computer where the application was working. This can be found by opening the sequence file in the TestStand Sequence Editor. The bottom of the Sequence Editor will show the process model being used. Hover with the mouse over the Model: field to get the full path.

2. Confirm that the process model file exists at this path on the new computer. If it does not, one of the following could be the cause of the issue:
  • You do not have the same bitness of TestStand installed on both computers. 32-bit TestStand will put the default TestStand files (including default process models) into C:\Program Files (x86), while 64-bit TestStand will put those files into C:\Program Files.
  • You are using a custom-made process model file that needs to be deployed to the new computer. These are generally stored in the Components folder of the TestStand public directory (C:\Users\Public\Documents\National Instruments\TestStand 20xx, shortcut %teststandpublic% in Windows Explorer)


Not Helpful