DMM Version mismatch error

[RichM]

I am running a TestStand sequence which makes a call to niDMM_init. Most times this works correctly, but intermittently I get error -1074117853 (every week or so, the function is may be called 50 times between failures)

"Error, Version mismatch error! Please verify the installation of all NI-DMM components. You may need a newer version of NI-DMM"

There are a large number of developers here who *may* be using different versions of NI-DMM on theor development machines to what is installed on the Test Rigs. This was my first thought - that perhaps there were some incompatibilities in DLL Ordinals between the various versions of NI-DMM. However, rebooting the rig and running the same sequence again allows it to work. Surely if this was the case - the problem would exist every time?

Sadly I cant attach the sequence here (since the niDMM_init function is buried inside a code module and a sub dll inside that - but I have traced it through and it is the niDMM_init function returing the error).

What I need to know is:

Is there a problem with developing on one driver version and then running with another?
If all the developers use the same versions of the drivers or at least compile the software with the same version - will this go away?
Why is the problem intermittent?

[RobSims]

Hi Rich,

Thanks for your post.

I can't think of a particular reason why such a situation may occur, aside from the fact the drivers will not be behaving in exactly the same fashion. I've also investigated some of our knowledge bases, but have, as yet, not found any prior knowledge of something like this.

However, to answer your questions, if you compiled the software using one version of the driver, it would normally be best to use the same driver on the deployed systems. Doing otherwise can leave you respective driverdriver versions.
The best bet is to try running the system using the same drivers as the compiler. This would, in theory, remove the oppurtunity for "Version Mismatch" errors. I presume the intermittent behaviour of the error arises from this same driver difference - quite why, again, depends on the details of the modifications.

Sorry I could not be of more help. Let me know what happens with normalised drivers.
If you have any more questions please do let me know. Thanks,