![]() ![]() Oh, so what you are saying is that this is actually external to LabVIEW (so it doesn't really matter about the bitness). That the according installer doesn't install the Visual C Runtime library (properly) is a bug but a weird one, because it obviously doesn't happen for most users, otherwise this forum would be full of such reports. That the according installer doesn't install the Visual C Runtime library (properly) is a bug but a weird one, because it obviously doesn't happen for most users, otherwise this forum would be full of such bitness of the dll needs to be the same as the bitness of the LabVIEW install, not the version. It doesn't really matter for the bitness of LabVIEW, since a LabVIEW process is communicating with this engine only through interprocess communication, so both 32-bit and 64-bit LabVIEW can use the same Error Reporting engine (and LabWindows/CVI and whatever other NI software may want to make use of that feature). NET Compact Framework provide a way to access unmanaged code in native Win32 DLLs: Platform Invoke, or P/Invoke. Not exactly sure but this is probably the NI Error Reporting engine that starts up automatically when you login and such background tasks are often running in the same bitness than the OS on which they are getting installed. I was getting the message upon startup and now I am not.Īs the program name in your error box said, it is nierserver.exe. This can reduce the startup time of anything using these assemblies, as they won't have to be compiled by the JIT at runtime. NET framework generate native images of their assemblies when they are installed. I then installed vc_redist.圆4.exe, rebooted and that seems to have fixed the problem. NET framework includes a tool called ngen that can compile. Hmm, that's what I would have suspected but I thought I'd ask because I read somewhere that different parts of LV are written in different bitness? I have LV2017 32bit so I installed vc_ , rebooted and that did not solve the problem. ![]() Bitness of the dll needs to be the same as the bitness of the LabVIEW install, not the version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |