02-08-2012 10:24 AM
I built a simple VI with a single input and saved it.
I then tried to turn it into a Veristand Model and recieved the following feedback:
------------------------------------------------------------------------
Setting Template Project properties... ERROR:
Code: 1327
Source: mxLvErrorHandler.vi:1
Error occurred. No DLL produced.
------------------------------------------------------------------------
I put the same vi on a different machine and I compiled no problem.
What gives?
Has anyone else experienced/solved this?
Thanks!
02-09-2012 02:30 AM
Hi MPCC,
i found a CAR to this problem. Are you using a LabVIEW 2011 beta version, for example LV2011Beta2 (b79). With this version the error occured, with b133 the problem does not exist anymore.
Regards,
Michael
NIG
02-09-2012 06:58 AM
I am not on a beta.
I am on LabView 2011 version 11.0 (32-bit)
02-10-2012 02:20 PM
Hi MPCC,
I was able to find the same CAR that MHoffmann had referenced (CAR 296994). Since you're not using a beta version, let's get some more information to see why this may be failing.
1) What version of VeriStand are you using?
2) Has building an lvmodel ever worked for you? If so, what's changed recently?
3) Does running a repair on VeriStand resolve this issue?
Regards,
02-12-2012 07:59 AM
Hi MPCC,
Did you call the VI you want to generate a model from model.vi?
just asking cause this result in an error (I dont have NI VeriStand install at home so I cannot be sure this is the same error... but that remind me something fore sure 😉 )
Have a great sunday,
Flo
02-13-2012 12:43 PM
Hey Che!
It's Mike from Wineman. I believe that I worked with you extensively a couple of months ago on a thermocouple card in veristand issue.
Here's my deal:
I'm onVeristand 2011.0.0.201
I'm using LabVIEW VS 11.0 (32-bit)
I have no problem importing a model into Veristand. (I'm actively compiling models on a different laptop and adding them to Veristand on the problem machine without issues.)
The error occurs when I try to compile a model on the 'Problem Machine'.
The LabVIEW is throwing the error. Not that I don't believe Veristand 'Could' be the issue. I just want to make sure we are on the same page.
As far as previous models; I have never compiled a model sucessfully on this machine.
Also: I did not name the VI model.vi. However, that would have sucked! I think that I named it something close to that!
I've since then attempted with unique names to no avail.
02-13-2012 02:55 PM
Hi MPCC,
some time ago I was able to fix such error by running the LVDB.exe
file found at C:\Program Files\National Instruments\Shared\LVDB\lvdb.exe
. This will update the registry to the correct value, and should resolve the error.
Regards,
Jiri Keprt
Systems Engineer (RTT & HIL)
CLA, CTA
02-14-2012 05:42 PM
Hey Mike! Small world, huh!? I hope your project is going well.
It seems like the current behavior you're seeing is causing unnecessary inconvenience, so let's get you up and running. I think that Jiri's suggestion will get you to that state. Please let us know the results!
Regards,
02-14-2012 07:23 PM
I did try running the exe.
It did not work.
I don't know if it had anything to do with it being in ProgramFiles(x86) or not though. (Being a reg editor... I'm not sure..)
That brings to point that I am operating in a 64bit OS with the 32bit version of LV and Veristand.
I don't really have other ideas as to why it wouldn't work though.
02-15-2012 06:41 PM
Hi Mike,
I'll look into the issue and get back to you as soon as possible. In the meantime, can you clarify whether or not the working computer has the same setup (Windows 7 64-bit, VS 2011, LV 2011, installed from same source media). Speaking of source media, are you using DVDs or downloading it from the website, or getting it from a server that your company is hosting?
Regards,