Cannot execute a library created with Labview 2011 in visual C++

I created a very simple DLL in Labview 2011, then, I try to call this DLL from a Visual C++ 2005 application.
I have tried to load the DLL at compilation time with the .LIB and .H files, and also dynamically with AfxLoadLibrary.
When I try to call the library function, it works fine, but the second time i call the library freezes the app.
all the library does is to show a simple dialog box and that's it, no params, no returns, no nothing,
but it freezes the app, why the VI works in Labview, but in DLL doesn't?

Hi Alveru,
What might be happening is that the process never ends and when you try to re call it, it fails and that it is why your app freezes, what you can do to probe is that is what is happening is to test your DLL directlly in LabVIEW with the Call Library Function Node so you can import the DLL and test it. If it also freezes or not work as expected the problem is with the DLL.
The proceses are automatically closed by LabVIEW at the moment the VI stops running; however, when you deploy the vi, you need to close them manually.
Try this out!!
Regards,
Luis Fernando
National Instruments Cono Sur
Ingeniería de Campo y Consultoría
http://chile.ni.com/

Similar Messages

Vision builder AI 2011 incompatible with Vis created by Labview 2011 ?

Hi,
I have some issues to drive some motor by a Vi created under Labview 2011 using an inspection built under vision builder AI 2011
The step for running a Labview Vi said me that it only support 2010 VIs or earlier ? How two NI softwares 2011 can be incompatible ?
So I try to save under a old version but this vi is part of a huge LLB...Is it possible to save this LLB as a 2010 version without saving all subvis .ctl etc.. ? I am a little confused...
Thank you for your help

You should be able to save the top level VI for previous to LV 2010, and all VIs from that LLB will also be saved to a LV 2010 version LLB that can be used by VBAI. There is a restriction that any VIs from a toolkit that you have to pay for (i.e. Vision), even if they are in your LLB will not be saved for previous, but driver VIs (i.e. Motion, DAQ, NI-IMAQ) if they are in your LLB will be saved in the resulting LV 2010 LLB.
I realize this isn't ideal and VBAI will be supporting LV 2011 or a future version later. Another option will be to use the VBAI API in LV 2011 to have VBAI do just the image processing portion of your control system and do Motion, or other functionality in LV environment and control VBAI from LV using the VBAI API (this allows you to load inspections, run them, get images, and results, etc.), which does support LV 2011.
Hope this helps,
Brad

Warning: Library created with compilation errors.

I am trying to run the following in SQLPlus logged in as
Portal30_SSO on the portal database server:
create or replace library auth_ext as 'C:\oracle\ora81
\bin\ssoxldap.dll';
commit;
When I run this it gives me the error:
Warning: Library created with compilation errors.
I am following the instructions from "Configuring Oracle9iAS
Portal for LDAP Authentication". I am running Oracle 8.1.7 and
OID on one W2K server and 9iAS on another W2K server. Any
suggestions on how to resolve this problem?

Is there any solution about how to compile XDB.DBMS_XDBUTIL_INT package?
My XDB.DBMS_XDBUTIL_INT package gives the following error when compiled:
How can I recreate "XDB.DBMS_XDBUTIL_INT". Currently it does not compile, giving error :
LINE/COL ERROR
33/7 PL/SQL: SQL Statement ignored
34/14 PL/SQL: ORA-00942: table or view does not exist

Install labview 6.1 (or compatible) run-time engine with labview 2011

I have installed a trial period version of Labveiw 2011 in order to check for possible upgrade issues I may have if I decide to upgrade from labveiw 6.1. Well, needless to say there have been alot. That is as expected since I have not updated labview in many years. I am still not under any pressure to update; however, I would like to in order to get support and make sure I do not have any compatibility issues with new equipment purchases. I have been able to resolve most of my compatibility issues with simple code fixes and such. However, twice now I have run into an error when launching labview executeables compiled by two different equipment manufacturers. The equipment I am using is not even old...maybe a year or so. When I launch the labview executables to control this equipment on a PC that has the trial period labview 2011 installed, I get an error message stating something like " This requires a Labview 6.1 (or compatible) run time engine." I have tried to download and install the 6.1 labivew engine but I can't install this engine on a PC which has labview 2011 installed. Can someone explain how I am to run these executables under labview 2011. I can't imagine these executables were developed using 6.1 since this equipment is not even a year old now.
Solved!
Go to Solution.

Im not for sure I am on the same page with you here. Im not trying to develop any code myself. I have some labview executables that came with hardware we purchased in order to control it. We used to have labview 6.1 installed; so everything was working ok. But now that I have installed 2011, I get an error message when trying to run these executables. The error message states that this executable requires a labview 6.1 or compatible run-time engine. I have seen this error on both XP and Windows 7 machines. I did not develop the executable, it was developed by the hardware manufacturer. But since this hardware is only about 1 year old, I an assuming they used a newer version of Labview to develop this code. Certianly newer than 6.1.
So I guess my question is..is there a way for me to get this executable to work on a PC that has labview 2011 installed. I have tried to install a labview 6.1 run time engine but it will not install. Any other options?

Cannot open imovie libraries created "with a newer version" (false!)

First of all, excuse me for my bad english!
I've an iMac 21.5'', fall '09 series. I'm not an expert user (I use Windows at work) and I use the Mac just for fun, when I have time.
A couple of months ago, I've updated to Maveriks. Then I try to update my iLife '11, too, but the Apple Store didn't show me the "update" option. Following some italian blogs tips, I change the language preferences and that let me able to update iLife. iMovie updated my video libraries and everythings works fine.
Yesterday, after a long period, I switched my iMac on, and check for software updates. Then I updated iPhoto and iMovie. Again, iMovie updated my libraries, and everythings works fine.
Then I choose "update all", the system prompted me asking my AppleID and pwd, the default language switched to italian, and all updates takes places.
On restart, "software updates" re-show me again iPhoto and iMovie, and other updates. I choose "update all", and the system reinstall iMovie among the others.
When I open iMovie, it prompted me with a "choose a library" messages, but whatever library I choose, it alert me with a messages that claim something like "cannot open this library, because it was created with a newer version of iMovie".
The problem is that "the newer version" is the "same" version (10.0.2) - exept for the different languages preference settings, and I dont' wanna wait until the next iMovie version to update my libraries
Can anyone help me to resolve this issue?

...It was so bad my English?

Application crashes when calling DLL built with LabVIEW 2011

Hello everybody,
Our application calls DLLs built with LabVIEW 2010 SP1. We installed LabVIEW 2011 and built some DLLs. So far so good. If we start our application and run 2010 DLLs it still works fine. If we run a 2011 DLL just once no error happens, but if we try to run the same 2011 DLL our application crashes reporting the error below. I saved the code for 2010 version and built a DLL and it works fine. Does anyone know why?
Thank you in advance.
#Date: Fr, 16. Sep 2011 16:25:25
#OSName: Microsoft Windows XP Service Pack 3
#OSVers: 5.1
#OSBuild: 2600
#AppName: PasTA
#Version: 11.0f2 32-bit
#AppKind: AppLib
#LabVIEW Base Address: 0x30000000
16.09.2011 16:25:26.181
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: 8a779b3f-51d7-4864-8e4d-6ab0195cd158
ExceptionCode: 0xC0000005
N
0x3072C804 - lvrt <unknown> + 0
0x3072CBB8 - lvrt <unknown> + 0
0x7C864191 - KERNEL32 <unknown> + 0
0x7C83AB50 - KERNEL32 <unknown> + 0
0x00000000 - PasTA <unknown> + 0
Attachments:
error.PNG ‏11 KB

On that note, you should be able to create DLLs in 2010 and run them with 2011, correct?? In my case, I have a 2010 built DLL (talking to sbRIO), most of the functions work when run in 2011, but a couple of them lock up LabVIEW on the desktop (but not the sbRIO), no lock ups happen with 2010 on the desktop.

Execute a VBAI code with Labview

Hello
I work with a CVS, and for that I create a VBAI code that I need to use with Labview, I already use the tool "migrate inspection to labview" and tryed this VI. I added the "inspect main" VI on my cvs target, but I did'nt do what I put on the VBAI code.
How can I do to execute exactly the VBAI steps in Labview.
Thank you for your help
Attachments:
Inspect Main.vi ‏103 KB

Here's a sample LV 2013 project with a CVS target and the build specs to get a startup app.
1. Right clikc on the CVS and select Properties. Change the IP Address to match your target's.
2. Right click on the "My Real-Time Application" under Build Specification for your target and select Build
3. Once the Build is done, right click again and select Deploy. This should automatically create a Configuration Files folder on the target with the correct files.
4. Right click again and select "Run as Startup" and this will ask you to reboot. Now the VI will start running when the target reboots.
If you need to debug, you can stop the startup app on the CVS by right clicking on the target and connecting. Then just open the Inspect Main.vi from the project when it's under your CVS target) and run it. The Configuration Files should already be downloaded to the target after following the above steps.
Hope this helps,
Brad
Attachments:
Sample Project.lvproj ‏36 KB

IPhoto will not open - says: Library created with unreleased version

I can't even open the app. due to a message that reads "The photo library was created with an unreleased version of iPhoto. Please quit and update this photo library by opening it in iPhoto 2 or iPhoto 4." I haven't done anything to the library recently. I did install Photoshop Elements and upgrade to OS 10.5 within the last few days. I got the same message in iPhoto before the upgrade to OS 10.5 however. Can anyone help me get my iPhoto open?

Olla:
Give Terence's suggestion a try. You'll end up with a new library and your old one for further attempts at fixing.
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Iphoto message: library created with unreleased version of iphoto

Hi I'm brand new to the forum--know others have had a similar issue--
I get the message that says library was created with an unreleased version of iphoto, and I should quit and open with version 2 or 4. when this message appears the only choice is to quit--iphoto menu bar is not available.
I'm also new to Mac. I bought my powerbook August 2005, but I can't even open iphoto to tell exactly which version I have. I imagine its 5.something.
I have about 3500 photos on here, but can only see them through preview, not my iphoto library. Wondering if this is related to the fact that my 512 usb memory stick seems to have been making my entire computer freeze (there are photos stored on it). Is it possible I picked up a virus from a PC via my memory stick and it's messing with iphoto? please help. I am completely dependent on this machine--I use it for 8-10 hours every day.
thanks,
RF

Hi RF,
Just highlight the iPhoto.app in your applications folder and in the next column it should tell you the version (viewing in column view)
I don't know the reason you go this message, though you are not the first one.
So far I have not seen any solution for that error message in these discussions. If you have a recent backup of your iPhoto Library folder then take the old library out of the Pictures folder and put your backup library in there (I suggest you backup the backup before you do this) Launch iPhoto and hopefully everything will be back to normal. If you don't have a backup then...
The only thing I can tell you to do right now is to create a new library and import/add to the library to reimport your images.
these are the steps:
Close iPhoto
Drag the iPhoto Library folder to the desktop
Launch iPhoto
In the next window that opens choose to create a new library.
When the new empty library opens go to File/add to library
In the next window navigate to the library on your desktop and choose it.
Your images will be imported in nice dated rolls. (make sure your view is set to sort by rolls to see it) There are a couple of caveats to this. You will get rolls named "Originals" These rolls will contain your video clips and your original images that you had edited. If you had RAW files they would be in those rolls too (I don't do RAW, so I don't know for sure) Delete what you don't want from those rolls. You will also get the jpeg pointer files to your video clips imported. They will just be jpegs and will not point to the video clips anymore as iPhoto made new ones when the clips were imported again. You can delete those. they should be in a roll right next to the newly imported video clips so they are not hard to find. The thumbnail files don't get imported as iPhoto makes new ones when the images are imported.
You will have to redo your albums, keywords, etc.
Good luck!
Lori

Cannot open Office 2004 documents with Office 2011 on Lion Server

I am in the process of moving our documents from a Tiger server to Lion server. My users who are using Office 2004 are having no issues, but the users with Office 2011 cannot open any documents with the .doc extension. I have tried logging on using afp and smb and I get different error messages but no access. When logging on as smb if I try to double-click I get the file type blocked message. If I go to File/Open I get the message Word cannot open this document. The file be in use, etc. There are no special characters in the file name. If I try to open a docx document then no problem. The same problem occurs with xls versus xlsx documents. Does anyone know if there is something different I should be doing. Permissions are set for full access. We have a mix of users with both versions of Office and over 90% of the file server are .doc or .xls documents. I cannot fully implement until I get this resolved.

I am having the same problem with UCM 10gr3. Our desktop engineers are doing an enterprise upgrade of MS Office to 2010 and this issue just surfaced. Trish, how do your users authenticate to Beehive? We are using a cusom connector using our AD.

Library Created with Newer Version?

I keep getting this dialog box when I try to open iTunes on my Mac ... says my library was created with a newer version of iTunes ... never had this problem in the six months or so I've had this Mac ... lotso music on there too, so I'm worried. Any ideas?

Did you ever get an answer from Apple Tech Support? I am having the SAME issue only I am on Windows Vista. iTunes said I had to download the 64 bit application, which I did. But when I try to launch the application, it won't let me because of the library error.

Internal warning 0xAFBF5C57 on startup with LabVIEW 2011 Student edition

Upon opening LabVIEW 2011 student edition, I get the following error everytime I open it.
I am using the it on a Mac computer, with Mac OSX 10.7.1, the Lion edition operating system.
Attachments:
StartUpError.jpg ‏52 KB

Hi Joe,
Have you ever successfully opened LabVIEW 2011 on your Mac?
Also, can you tell me what processor does your Mac has? I want to make sure that there is not a compatibility issue here. Please reference to LabVIEW Version Compatibility with Mac OS PPC and x86 Processors for the compatibility list between LabVIEW and Mac.
Regards,
Daniel
Regards,
Daniel REDS
RF Systems Engineer
Help us grow.
If a post solves your question, mark it as The Solution.
If a post helps, give Kudos to it.

Editing a software created with labview

Hi
I have a software which was created using labview. it is basically a sofware to control a laser machine used for material deposition. i also i have the source code for the software. I want to make some modifications to the program. When i make some changes in the source code. i see that there is no change in the actual software which is an exe file. so how can i overcome this problem? I guess once i make the changes to the source code I need to create a new excecutable file from all the VI's. So I want to know how can i make a new exe file from the changed VIs.
I want to know what is the difference between the following
.vi file
.llb file
.lvllb file
Thanks in advance
Vikas
Solved!
Go to Solution.

Vikas,
when working in LV, you have an edit time compiler, compiling you source code (the block diagram) into executable code. Still, you need the developement system to start the execution of this code.
Therefore, you will create a *.exe file out of your application when finishing all changes in order to execute the application without the need of the developement system (still you need the LV Runtime Engine).
VIs are the modules in LV and they consist of three parts stored on disk:
a) Frontpanel, the interface (IO or user interface)
b) Block Diagram, uncompiled sourcecode
c) compiled sourcecode
LLBs are the old version of LV libraries:
+ free naming (obsolete since break up of 8.3 naming convention)
+- VIs contained in the LLB are slightly packed
+-single file (good for deployment, bad for SCC)
lvlibs are new LV libraries:
+ lvlib-file is XML based "filehandler"
+ namespacing allows same VI names in memory (still bad idea for disk!)
+ VIs know about "their" lvlib
- Under certain circumstances maybe a little confusing for deployment
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Building an executable with .vits with Labview 2011

Howdy Forum,
I've recently adopted some code that dynamically calls two different .vits, one that parses (and displays data), and another that is used for logging this data.
While developing, it runs fine and dandy.
If compiled and not moved from the build directory, it runs fine.
If compiled, and moved to some arbitrary directory, it throws Error 7, and croaks.
If compiled, moved to some arbitrary directory and the .vits are also copied to that directory, it opens the .vits and tries to run them, but croaks as the .vits are broken due to all of the broken references to sub-vis.
I read this page regarding Error 7, and both .vits and the global that shares the info between them and the main .vi are included in the Always Included build information.
The fact that my executable tries to open local .vits tells me that those .vits are not being included in the executable for some reason. Any way to get around this, i.e. can I somehow "compile" each of the .vits so that I don't have to worry about associating all the sub-vis used by each .vit?
I am learning the painful lesson of build early and often, but would appreciate any insight you guys might have. It would be much appreciated!
Thanks!
.jim
Jim S
GRA/Colorado School of Mines

I actually have a simple example project that demonstrates some of the newer features that make VITs obsolete for dynamic launch. (They still have great value for development!)
Go ahead and play with this project I built for internal benefit.
Edit: Attached backsaved for 2011 too
Jeff
Attachments:
Launch N(Core) (2).zip ‏51 KB
Launch N Folder 2011.zip ‏45 KB

Cannot open any library documents with MS Office

I recently starting using Beehive. I am a user, not an administrator. I uploaded a bunch of documents to a new workspace I just created. Now I want to open them for viewing and editing. When I try to open any MS Office document (Word, Powerpoint, Excel), I get a message "Access to this web server is disabled by default because it is controlled by basic authentication and does not use Secure Sockets Layer (SSL). Do you want to search the Microsoft Online Support Center to view possible solutions?". I click on "No", and then nothing happens. The applicaiton is open, but no file is never displayed.
I have had this message before when opening documents from MS Project Server 2010 library, and always click "No" and then the document opens regardless. It also prompts me for the username and password for the Windows Server where MS Project Server 2010 is installed. I am not being prompted for that when I launch the document from Beehive. However, the MS Project Server 2010 server is located on our side of the firewall. This Beehive server is a shared government server located outside our dept firewall. BTW, I have no issues opening PDF files.
A workaround is to drag and drop the document onto my desktop and then open it. Not very efficient, but it works. I have tried adding the website as a "trusted locations" but can't add the URL. Is this a function of MS Office, a function of our Webwasher, or is it something that must be done on Beehive?
Thought this might be a useful way to do team collaboration across several government depts, but won't do me any good if I can't open and edit the documents I store on there.
Trish :)
Edited by: 941034 on Jun 15, 2012 12:14 PM

I am having the same problem with UCM 10gr3. Our desktop engineers are doing an enterprise upgrade of MS Office to 2010 and this issue just surfaced. Trish, how do your users authenticate to Beehive? We are using a cusom connector using our AD.

Cannot execute a library created with Labview 2011 in visual C++

Similar Messages

Maybe you are looking for