NI-DAQmx and Visual Studio 2019 stop working together

[kevin.shoop@ul.com]

I wrote a DAQ program in VS 2015/2019 about a year and a half ago that interfaces with an NI-9171/NI-9217 RTD module.  We haven't used for about a year and now it crashes when it tries to start the NI interface in the code.  Running it in debug results in the program crashing and exiting with code -532462766 (xe0434352).  I've reinstalled NI-DAQmx and tried the usual things (rebooting, recompiling . . .) with no success.  Even trying the example code from NI (ContAcqRTDSamples_intClk.2021) results in the same exit error.

KS

[hy_]

HI,

Are you compiling it on the same machine on which the project has been compiled successfully before ?

Does your Windows user have limited privileges? (restricted access to system directories, etc.)

[kevin.shoop@ul.com]

Hello hy_

The C# application was originally developed with DAQmx version 18.5.

I have reverted to version 19.0.45.2 on both my development systems and the lab computer and the development debug and the released code from 2019 runs as expected.

Given the application runs with version 18.5 and 19.0, If I have time I may start working up towards version 21 to see were things breakdown.

But given the amount of time Package Manager takes to do things, I’ll have to find a window in my schedule and I won’t get to it for a while

With VS 2022 coming out soon, there may be other issues popping up.

In answer to your questions.

My development system was swapped out in early 2020 and Windows has been continuously updated, per corporate IT policy.

I have full admin rights on the whole system, however the application is run by basic user accounts with limited rights.

The application is done as an all users installs, though requires admin rights to install.  All installs require admin rights on our systems, though basic users can run the applications.

Development is done in VS running under admin conditions.

[hy_]

Have you tried repeating the steps provided here?

They are slightly outdated, but might give an idea for what may be wrong.

[hy_]

HI

Installing an older DAQmx driver fixed the issue for me, try 20.1