11-20-2017 11:46 PM
Hello,
I am using labview 2014 sp1 32bit.
My operating system is Window10 64 bit.
I recently installed opencv toolkit using VIPM (Run as administrator).
After installing and restarting PC, I tried to open opencv example vi and i am getting following error.
How can I rectify this error.
Thanks & Regards,
Nisarg Shah
11-21-2017 06:02 AM
Sounds like a Microsoft Visual C Runtime version error. You will have to find out which Microsoft Visual C runtime redistributable you need to install. Sorry to not be able to give you more specific information but I haven't used that library yet so not sure what is the Visual C version used for those DLLs.
11-21-2017 06:28 AM
There is a suspicious problem in your message. You use LabVIEW 32 bit on Windows 64 Bit. As such I would expect the system DLLs to be loaded from inside C:\Windows\SysWOW64 and not C:\Windows\System32!
Also did you happen to restart the computer after you installed this package?
11-21-2017 11:26 PM
Yes I restarted pc.
Previously i was working with window 8 64 bit system and labview 32 bit was installed with opencv toolkit. it was working fine.Now shifted to new system with window 10.
I tried with latest version of opencv tool kit and previous version also.
In vimp it is showing compatible os for toolkit is window8,7 and vista.
Is it because of window 10 not supported?
Regards,
Nisarg Shah
11-21-2017 11:34 PM
You are right that system dll should be loaded from C:\Windows\SysWOW64.
I have checked all required dll are there in C:\Windows\SysWOW64. and not in C:\Windows\System32
In window 8 64 bit system with labview sp1 32 bit it was working.
This problem is facing with window 10.
I even tried to cut paste dll from SysWOW64 to system32 folder still didn't worked.
Regards,
Nisarg Shah
11-22-2017 04:06 AM - edited 11-22-2017 04:18 AM
Don't start copying and pasting DLLs from one system location to another. That only can make things worse if you don't know exactly what you are doing, and not even I would know how that could help in this instance.
I did briefly check and the installation procedure is adding these directories in System32 as soft links to the real installation (hence the administrator requirements for VIPM since you are not allowed to create symlinks in the system directory without. Also directory redirection in Windows should redirect to C:\Windows\SysWOW64 anyways when a 32 bit application requires a DLL in C:\Windows\System32 on a 64 Bit Windows system. So the location "should" be not the culprit.
Most likely your Windows system doesn't have the right Microsoft Visual C 12.0 C runtime libraries installed. Try to download this installer (for other people coming across this page look on this site for links for other VC versions) and install it on your system and keep your fingers crossed.
This has most likely nothing to do with Windows 10 directly other than that every Windows version comes with a number of preinstalled Visual C runtime libraries for various build in components that were created using various versions of Visual C. If your library happens to use the same version of Visual C as one of those built in tools was created with it will work, otherwise Windows will not be able to locate the prefered version for your DLL and will try to load with another similar one, which often ends up not having the required exports.
11-22-2017 05:20 AM
12-04-2017 05:30 AM
I installed labview 14 Sp1 32 bit on another fresh new system with window 10.
Downloaded opencv toolkit from VIPM Run as Administrator. Toolkit installed successfully without any error. Restarted the System. But for example vis, Run button still showing Broken.
We are developing application where some algorithm already developed in opencv need to import as some function are not available in vision library. we are stuckup with DLL wrapper calling part.
Thanks & Regards,
Nisarg Shah
10-19-2018 12:47 PM
Hi,
Did you get this issue cleared after some time? Because I too try to do the same thing but ended up with the DLL file missing error. Do you find anyways to solve this sir?
01-16-2019 07:06 AM
i also faced the same error? when running it on windows 10 with labview 64bit .if u will get any solution then kindly help it out
should be thankfull .