TestStand causing error 403683 - Module was unable to synchronize events

[MarLentz]

We have a specific test system where our DQMH-based HAL is unable to run under TestStand. When starting up a sequence which initialises an instrument module we get a timeout on the sync events VI (even if we let the timeout value increase to 2 minutes). The startup module seems to run correctly an returns a module ID.

The same code runs fine on our other "identical" systems - in quotation marks, as they clearly are not identical when it works on one station, but not the other.

The module runs fine when using the module tester in a pure LabVIEW environment.

The environment on the station is DQMH 6.1, TestStand 2017 and LabVIEW 2018. Both 32-bit and 64-bit versions are installed on the system, which is a difference from our other stations, but in my mind shouldn't cause such an issue. TestStand is set up to use the 32-bit version.

Any ideas on what can cause this before we go and reinstall TS and LV?

Thanks

Martin

[FabiolaDelaCueva]

I would go piece by piece, checking all the settings and configurations on a system that works and the one that doesn't. 
Run the API Testers as sniffers in both systems, and add "Status Updated" in several areas, so you can see on the API Testers where the difference may be.

If it were a timeout, you could increase it to an insane amount... if it eventually advances, how long is that time? There may be a clue as to what is going on there. 

Sorry that I don't have any more tips, but this is the case when the "but it works on my machine!" answer pops up. 

If you can have a clean system, where you start adding all the pieces, you would know what works by default. Then it is up to you if replacing or doing a factory reset to the system that is not working is the way to go.