SequenceContext error

[Hubinho]

Hello
I haven't been using TestStand for a few weeks now, so I can't remind what is the reason for my problem.

Everytime I try to run a sequence I get this error:

Even in the simpliest sequence containing one statement I must click "OK" several times. It is impossible to debug sequence as I can't check variables because this error appears.

I repaired TestStand with NI Package Manager but it didn't help.

I tried to reinstall TestStand, but I can't. When uninstalling TestStand with Package Manager, I get this error:

Does anyone have any idea how to fix Test Stand on my PC?

[Scott_Richardson]

The expression runtime error suggests that something is wrong with the TestStand files installed or how they are registered. I have been away from TestStand for too long to direct you to what files might be messed up.

If you have started to uninstall TestStand partially before you hit the error, you might need to continue down that path to resolve that first before debugging the expression error.

If you want to debug the uninstall error, you can obtain more details for others to help debug this issue, specifically log files that Windows can generate. Please follow the instructions in Generating and Locating NI Package Manager Error Logs for obtaining Package Manager and MSI log files. Specifically, enable MSI logging, attempt to uninstall again to reproduce the error, and then review the new log files that were updated and created. You can post the log files on this forum thread for others to review as well.

The files of interest include any updated and any new files in these directories:

• %localappdata%\National Instruments\NI Package Manager\Logs\
• %localappdata%\National Instruments\NI Package Manager\Logs\NIPkgLogs\
• %localappdata%\National Instruments\NI Package Manager\Logs\WinInstMSI\

[Hubinho]

Hello Scott,

Thank you for suggestion. I have enabled MSI logging and I attach both MSI and NI error logs. I cannot find any leads in them 😞

In the meantime I have found TestStand setup. I have uninstalled Teststand with it, restarted PC, installed Testand, restarted PC and I got the same Sequence Context error as in the beginning.

[Scott_Richardson]

Hubert, all NI MSIs in our installer packages use pre-install custom executes to setup some shared environment variables and something that we call NIPaths which resolve to what directories that NI is using for its software. For some reason the OS MSI Engine is failing to properly invoke those custom commands in child processes and results in these variables not getting setup properly.

Questions:

1. What OS and version of the OS are you seeing this issue on?
2. Are there any changes in security management features that are running that could be affecting installation operations?

[Hubinho]

I'm using Win 10 Enterprise 21H2.

Yes, it may be a reason. My company is using few cyber security softwares on computers.

However Teststand was working normally 1 month ago. Since that time I was using sequence editor without running them. I have no idea what could I change.

[Scott_Richardson]

Hubert -

If the security software has been updated to be more aggressive with monitoring privileged processes like installation, and it might be limiting what unsigned MSIs are allowed to do.

Can you share with me here or in a private message the details of what cyber security software is being used on your system?