Build error after upgrading from 8.2.1 to 8.5 "Error 1055 occurred at Invoke Node..."

After upgrading to 8.5, I'm getting the following error when trying to build an EXE:

Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1055 occurred at Invoke Node in AB_Source_Library.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW:  Object reference is invalid.
I have been building this application for both Windows and Mac OS, and I even get the same error when building the .app on an Intel Mac.
Things that I've already tried:
* Mass-compiling all my code
* Created the project from scratch
* Enabled each panel of the "diagram disable structure" one at a time and compiled again
Any ideas?
x9561 (148440)
10/26/2007 8:10:07 AM
comp.lang.labview 35213 articles. 1 followers. vasusachin24 (1) is leader. Post Follow

4 Replies

Similar Articles

[PageSpeed] 36

I think I saw that in LV 8.2.1 after upgrading from LV 8.2
I did a repair on the nistall and that cleared up the problem.
You may want to try that.
x9561 (148440)
10/26/2007 10:10:05 PM
You mean a repair of the NI installation of LV8.5?  But I had the same trouble on a Mac OS machine too.  Seems unlikely that an installation glitch could explain the problem on such different platforms.  (For the record, I tried on both a Win2K machine and an XP machine--a total of 3 different LV installs with the same error 1055.)
x9561 (148440)
10/26/2007 10:40:09 PM
Hi Travis,

Ben?s advice if definitely the best place to start. Error 1055 is a very general LabVIEW error for ?Object reference is invalid.? The cause is usually a bad install where important LabVIEW function aren?t placed in the right directory or aren?t installed at all. 

x9561 (148440)
10/29/2007 10:10:06 PM
The installer for Mac OS is so different than for Windows.  I can't imagine there being much code reuse.  How could the same installer bug occur on both platforms?  And whatever this installer bug is, is the fix going to make it into 8.5.1?
And is there even a way to repair a MacOS install?  (Don't have the computer in front of me to try at the moment.)
x9561 (148440)
10/30/2007 2:40:09 PM

Similar Artilces:

How can I modify the "Type definitions" of "Function Prototype" if I want build a DLL in Labview 8.5.1.?
Hello,We have a library with several VIs (API - Interfaces to our Real Time Target). This VIs we provide to our customer to generate own VIs to control the Real Time Target.Now we want to provide the functionality of this VI-library as DLL to our customer. The problem is, that labview use self definite name of type definitions. Also if I use "strict Type definition".Example:void GetOutputValues(VARIANT *Scale_In, int32_t ModelNr, uint16_t SignalID[], TD1:smileymad: *errorIn, VARIANT *Scale_Out, TD2 *Data, TD1 *errorOut, int32_t len)It is possible to modify "TD1" and "TD2"? I want to give useful names.GreetingsSteffen Hi Steffen,       Try editing the .h file as follows: CHANGE FROM: typedef struct { LVBoolean status; long code; LStrHandle source; } TD1; CHANGE TO: typedef struct { LVBoolean status; long code; LStrHandle source; } TD1; typedef struct { LVBoolean status; long code; LStrHandle source; } LVErrorCluster; then your GetOutputValues prototype becomes: void GetOutputValues(VARIANT *Scale_In, int32_t ModelNr, uint16_t SignalID[], LVErrorCluster *errorIn, VARIANT *Scale_Out, TD2 *Data, LVErrorCluster *errorOut, int32_t len) If your source-code doesn't refer to "TD1", then you probably won't need to keep the TD1 prototype! Cheers. ...

Labview 8.5.1's MathScript window failed running imread with an error "A problem occurred in a subVI call."
Hi, I am trying to port a Matlab program into a MathScript script.&nbsp; Following is the first few lines of the script:clear;image1=imread('C:\LV_VertAlign\DSC_0104.jpg','jpg');image_double1=im2double(image1);image_gray11=rgb2gray(image_double1);In the first line, imread is supposed to read in a photo taken from a DSLR camera, so I think it's a 32-bit image.&nbsp; And this is the error I got when trying to run this script in the Labview 8.5.1's Mathscript windows:"Error in function imread at line 2.&nbsp; A problem occurred in a subVI call."What is the problem here?&nbsp; and why does it complain about a subVI call?Thanks for any help to point me in the right direction.-Anh Hi Anh, &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; We have documentation on many of the MathScript functions available in LabVIEW.&nbsp; You can look at a document <a href="http://zone.ni.com/reference/en-XX/help/371361D-01/lvtextmath/msfunc_imread/" target="_blank">here</a> that describes how to use the imread function.&nbsp; This is searchable from ni.com by entering the function name.&nbsp; If you read this document you will see the second parameter of the function only accepts the following arguments : 'BMP', 'JPEG', 'PNG'.&nbsp; If you change your line 2 to : image1=imread('C:\LV_VertAlig...

error 7 in &quot;application builder&quot; for LabVIEW 8.5.1
Hello, &nbsp; I am getting an error while building a project for making EXE file. &nbsp; below is the displayed message. &nbsp; Error 7 occurred at Copy in New VILibrary.vi-&gt;AB_Dest_LLB.lvclass:Create_Destination.vi-&gt;AB_Build.lvclassLCreate_Destinations.vi -&gt;AB_Build.lvclasss:Build.vi-&gt;AB_EXE.lvclass:Build.vi-&gt;AB_Engine_BUild.vi-&gt;AB_Build_Invoke.vi-&gt;A B_Build_Invoke.vi.ProxyCaller &nbsp; ============================NI-488: Non-existent GPIB interface. C:\ProgramFile\NationalInstruments \LabVIEW8.5\vi.lib\Utility\libraryn.bin &nbsp; thanks, &nbsp; You can force LabVIEW to recompile the entire VI hierarchy in your project with CTRL+SHIFT+Run Button. Have you imported some old VI's into the project?&nbsp; From a previous version? Did you add files since creating the build parameters?&nbsp; You may want to delete the build parameters and create a new one. RayRMessage Edited by JoeLabView on 07-02-2008 08:35 AM Also, check the path of the reported missing file and make sure it really isn't missing. Thanks George...&nbsp; :) Especially if code moved around (Copy / Paste to another folder / backup, etc..) Thanks Ray and George, I was using VIs of 7.1 version for 8.5 builder. I deleted the previous build parameters and created a new one, it was sucessful. - sriveni &nbsp; Glad it worked.. :) ...

LabVIEW RT 8.5.1 &quot;reboot due to system error&quot;
I'm running my app on a quad core RT desktop target.&nbsp; The executable runs anywhere from a few minutes to a few hours before the machine reboots.&nbsp; About half the time I get the "reboot due to system error" and the "software state: safe mode" messages.&nbsp; rtlog.txt has no record of the reboot. &nbsp; Is there any way to get LabVIEW to log any useful data when this happens? &nbsp; What actions can I take to track this down (other than disabling portions of my code to see what part might be causing it)? Connect up a display to&nbsp; the RT chassi to see if you get any message there. In addition, watch your memory useage. If you run out of memory,&nbsp;RT will just STB. :smileysurprised: Ben Hey Ben, Thanks for responding. I do have a display hooked up to my RT desktop, but when it reboots, it reboots.&nbsp; Screen goes blank.&nbsp; No messages. How do you watch the memory usage on the RT target? What does STB mean? Thanks, In LV 8 and up I believe there is a property under the RT target inside the project. STB = "Sh#$ The Bed" Ben You can go to Tools --&gt; Real-Time Module --&gt; System Manager ...

LabVIEW 8.5.1 &quot;The build was unsuccessful&quot;
When attempting to build my executable in LabVIEW 8.5.1 I get the following dialog: &nbsp; <img src="http://forums.ni.com/attachments/ni/170/338657/1/Build%20Errors.PNG"> &nbsp; I've tried recreating my build specification, reinstalling LabVIEW, commenting out sections of my code and nothing seems to help.&nbsp; Has anyone encountered this before?&nbsp; Any ideas NI?Message Edited by FlamingYawn on 07-08-2008 11:24 AM Build Errors.PNG: http://forums.ni.com/attachments/ni/170/338657/1/Build Errors.PNG Hi, &nbsp; Are you building a .exe application? In that case, please verify that all your startup and always included VIs exist in the same path and have been properly compiled. You can try Tolls&lt;VI Analyzer&lt; Mass Compile. Also are you using DSC or shared variables in your code? &nbsp; Ipshita C. Hi Ipshita, &nbsp; Thanks for responding.&nbsp; &nbsp; Yes, this is "a .exe application."&nbsp; &nbsp; My startup path is correct, and I tried building with all my "always included" VIs removed.&nbsp; Same error. &nbsp; I've mass compiled several times. &nbsp; I'm not using DSC or shared variables. &nbsp; I'm able to build the executable on another computer with the exact same project and code (we use source code control), so something must be different about my environment or setup. &nbsp; Thanks, &nbsp; Robert I have seen this error before, but ...

Error 1047 in LabVIEW 8.2: LabVIEW failed to send variable to the script server. Server:&quot;&quot;
I am working with the evaluation version of labVIEW as well and I have run into another error.&nbsp; I am using a MATLAB script node within a for loop and attempting to pass the for loop counter variable into the script.&nbsp; When I run the code it brings up a 1047 error and says "LabVIEW failed to send variable to the script server. Server:"" ".&nbsp; I looked up the error online which seems to have roots in a failed auto initialization of MATLAB.&nbsp; Is there something that I can do in labVIEW to fix the problem or is it strictly a MATLAB error? &nbsp; I really appreciate your help. Hi Patsenat, &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; We have a knowledgebase document on our system referring to this issue.&nbsp; Try reading through <a href="http://digital.ni.com/public.nsf/allkb/2B3FF46C8512C4F786256CF30071BE53?OpenDocument" target="_blank">this</a> and attempting what it says.&nbsp; If you still have problems, please post again. ...

Labview 8.5 error on save: &quot;Cannot load help information of [filename].&quot;
Hi all, &nbsp; &nbsp;I was working on a VI in Labview 8.5 when the program (Labview) crashed. When I relaunched Labview it asked me if I wanted to recover the VI&nbsp;I was working on,&nbsp;I said yes and the recovered VI runs fine, but I cannot save it. When&nbsp;I try to Save or Save As I receive the following error message: "Cannot load help information of [Filename]" and my only option is "Cancel Save". If I click "Cancel Save" Labview returns a "File not Found error". Until the recovery, I could and did save the file with no problems. It now seems that I am locked out of the file. &nbsp; &nbsp; I have a backup, but it is does not contain the 2-3 hours of work I put in before the crash. Does anyone have a work-around, or know the source of this error? This is the second time I have seen it on a recovered file (the first time I had a fresh backup, so it wasn't a big issue). &nbsp; Here is a dump of the "Referencing files in the project or its dependencies" from the Save As dialog: &nbsp; [Project Name].lvprojreplay2-offsets.vi:Instance:6replay2-offsets.vi:Instance:5replay2-offsets.vi:Instance:3replay2-offsets.vi:Instance:2replay2-offsets.vi:Instance:4replay2-offsets.vi:Instance:1replay2-offsets.vi:Instance:0 &nbsp; Thank you, Tim I'm having the same problem. I came here to see if there was any information about this problem, and found the previous message. Lucky for me, I&#...

why it keeps on asking &quot;NI LabVIEW 8.5.1&quot; distribution when building installer?
Hi, I am building an installer for one image processing application. For addtional installers, NI Labview runtime engine 8.5.1NI vision runtime engine 8.5NI IMAQdx 3.1.2NI VISA runtime 4.3When building, it keeps on asking "NI LabVIEW 8.5.1" distribution even though I put the CD into CD room, saying it needs to copy a component installed or updated by the distribution to continue building the installer.If&nbsp; NI-IMAQ dx 3.1.2 not checked, it is OK. BUT, I need it.Thanks a lot for any help.Anne Zuo What is a "CD room"? or CD driver. sorry for my language.&nbsp; Take a look at this <a href="http://forums.ni.com/ni/board/message?board.id=170&amp;view=by_date_ascending&amp;message.id=210032#M210032" target="_blank">link</a> and see if it helps. &nbsp; Also, if it doesn't like disk 1, put in disk 2 instead, if not disk 2, then try disk 3.&nbsp; Perhaps it is looking for the driver it needs, but the actual files it is looking for is on the 2nd or 3rd CD. &nbsp; Ultimately, it may be best to copy all of the CD's to your hard drive and have it point to them there. ...

&quot;investigate previous internal error&quot; every time I start LV 8.2.1
Hi, &nbsp; Every time I start LV 8.2.1 I get a message "The last time you ran LabVIEW, an internal error or crash occurred at fpsane.cpp, line 401" and it asks if I want to investigate now. I don't have any problems while running the application, compiling it or building an installer. Does anyone have any idea what this is and if it's important? &nbsp; Thanks, Danielle "The last time you ran LabVIEW, an internal error or crash occurred at fpsane.cpp, line 401" This occurs mostly&nbsp;by your front panel controls. &nbsp; Try a search in this forum with the keyword - "fpsane.cpp" You can get a couple of solutions. Post if further help required. &nbsp; Thanks, Mathan Although the VI runs, it may have a strange entry somewhere.&nbsp; &nbsp; I did get that message a couple of times.&nbsp; From what I can recall it was when running omething &amp; I had to kill the execution, or shut down LV completely.&nbsp; Upon re-start of LV a similar message popped up.&nbsp;&nbsp; The message did not re-appear at the next start.&nbsp; Maybe I inadvertently fixed it without knowing.. &nbsp; Try loading your VI, running it once.&nbsp; Saving it.&nbsp; Shut down LV.&nbsp; Restart LV.&nbsp; And check to see if the message continuous to appear. (you may have to repeat the steps once). &nbsp; Oh... Do you have any Disable Structure which has some unfinished code iside it?&nbsp; ...

&quot;IMAQ image to string&quot; difference in 8.2 and 8.5
My basic aim is to capture image from one computer and then send to another in LAN using TCP/IP. I have LabVIEW 8.5&nbsp;and LabVIEW vision 8.5 in one and LabVIEW 8.2 and LabVIEW vision 8.2 in another. I&nbsp;capture an image in the computer whear&nbsp;I have installed 8.2 version&nbsp;of&nbsp;both&nbsp;and then flattened using " IMAQ image to string"&nbsp;and then sent it to computer using TCP/IP to computer with 8.5 version but the image is not displayed whearas when i do&nbsp;send&nbsp;that from 8.5 to 8.2 ( Capture the image in the computer with 8.2 and then flatten it to string and send it to the computer with 8.5 and display) , it works. Is it beacuse of different version of LabVIEW vision? &nbsp; Hi aman_bajra,You should be able to pass the image from one computer to another using TCP/IP, even if the computers have different versions of the Vision Development Module installed.&nbsp; I tested this here and I had no difficulty sending the image from a computer running Vision 8.5 in LabVIEW 8.5 to a computer running Vision 8.2 in LabVIEW 8.2, or vice versa.&nbsp; FYI, I used the normal Flatten to String node, not the IMAQ Image to String VI.&nbsp; I have included the VIs I used to do this below.&nbsp; Please give these a try and reply back if you are still unable to send your image properly.&nbsp; Thanks.Rishee B.Applications EngineerNational InstrumentsMessage Edited by risheeb on 03-12-2008 12:24 PM...

Installer &quot;Source file settings&quot;, &quot;VI Settings&quot; problem in 8.2
I have just upgraded from LabVIEW 8.0 to 8.2 and it seems the Installer "Source file settings", "VI Settings" check boxes no longer have any affect on the built application. &nbsp; For example, if I un-check the "Show Menu Bar" boxes for my Main.vi and build, when I run the built application the Main.vi Menu Bar is visible. &nbsp; It seemed to work as expected with 8.0 though. &nbsp; Any help and suggestions are much appreciated. &nbsp; Aaron Hi Seamus, Thanks for that and I look forward to hearing from you again Aaron ...

&quot;IDDCO ERROR&quot; for Labview 8.0 and Keithley 6487 picoameter
Hi all, I have a 6487 keithley picoameter and I would like to take current mesurements using labview 8.0. What I tried to do is to built a very simple vi with two instrument I/O assistants (one for configuring the picoammeter and another to take measurments as it changes voltage). I have accompliced the same thing in Visual Studio with C#. The problem is that although some times I do get correct measurements there is always one, two or three IDDCO ERROR idications which I do not know what they mean.&nbsp; I can only tell that this does not happen at the same voltage value but it seems rather random. What is wrong? I have attached the vi if anyone is interested. Thanks in advance for any helpAndreas V_bias_test.vi: http://forums.ni.com/attachments/ni/170/324015/1/V_bias_test.vi According to <a href="http://www.keithley.com/search?searchType=general&SearchableText=IDDCO" target="_blank">Keithley</a> , "This error means the instrument received an Illegal Device-dependent Command Option.". I have not used this model Keithley or DDC. One thing you should do is wire the error out of the initialize Instrument Assistant to the for loop to assure that is actually runs before the for loop. ...

&quot;Error 7 occurred at Invoke Node...&quot; when attempting to open .vi for editing
I am attempting to open a vi for editing, and instead the vi is attempting to execute.&nbsp; I&nbsp;get the error: &nbsp; &nbsp;"Error 7 occurred at Invoke Node in BuildTargetBuildSpecification.vi-&gt;BuildXFS.vi"&nbsp;&nbsp;&nbsp;&nbsp; Possible reason(s):&nbsp; &nbsp;LabVIEW:&nbsp; File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer. Method Name: Project: Open &nbsp; When I close the Error Message dialog, Labview terminates. &nbsp; ...

What is "error 8"
I set up an external serial modem using the Red Hat GUI networking tool as a generic modem device. However, when I hit the "Activate" button, I get the message, "Failed to activate device with error 8." Where can I find what "error 8" means? Thanks. No one responded, but for the benefit of any other newbies who encounter this problem, here is the solution: I looked in the System Log and saw that the modem did not find a dial tone. I plugged in a phone line, and the "Activate" command worked fine. (I had not realized that "Activate" meant "Connect.") Crooked River wrote: > I set up an external serial modem using the Red Hat GUI networking tool > as a generic modem device. However, when I hit the "Activate" button, > I get the message, "Failed to activate device with error 8." Where can > I find what "error 8" means? > System error numbers can be found in /usr/include/asm/errno.h The only problem is that there is no assurance that that is what the program is displaying. #define ENOEXEC 8 /* Exec format error */ does not sound like what you are really getting. The best bet would be to look at the source of the program that is producing that error message. Unfortunately, the scattered shell scripts, programs, and whatnot concerned with networking, especially dial-up networking is a spaghetti mess, and if your ...

How to remove the &quot;int len&quot; of my return string on the DLLS header when building a DLL on LabVIEW 8.5
Hi all. I'm building a DLL on LabVIEW and I choose a string as an output on the terminals connectors. But LabVIEW creates another output, the lenght of the return string. This is a problem because I have other DLLs and&nbsp;I need them to be compatible. How do I remove this length from the header? What is the difference between Pascal String and C string and String Handle Pointer? String Handle Pointer removes the length from the header but I don't know the difference between this data types. Thanks in advance for the help. &nbsp; Daniel Coelho Portugal &nbsp; Daniel Coelho wrote:Hi all. I'm building a DLL on LabVIEW and I choose a string as an output on the terminals connectors. But LabVIEW creates another output, the lenght of the return string. This is a problem because I have other DLLs and&nbsp;I need them to be compatible. How do I remove this length from the header? What is the difference between Pascal String and C string and String Handle Pointer? String Handle Pointer removes the length from the header but I don't know the difference between this data types. Thanks in advance for the help. &nbsp; Daniel Coelho Portugal &nbsp;C string pointer is a pointer to a memory location whose string information is terminated by a 0 byte. Pascal String Pointer is a pointer to a memory location where the first byte specifies the number of bytes to follow. This obviously allows only for strings up to 255 character length.LabVIEW String Hand...

Labview &quot;Fatal Internal Error &quot;memory.cpp&quot; line 1038
Hi, &nbsp; This is an example file provided by NI and can be found in Labview 8.2\examples\instr\niHSDIO: Dynamic Generation.lib. Inside this library, there is a file called "Dynamic Generation.vi". If I copied "Dynamic Generation.vi" to other place, the labview will crash. Error message: &nbsp; "Fatal Internal Error. "memory.cpp". Line 1038. Labview version 7.1.1. You will lose any unused work, please contact NI, etc, etc" &nbsp; In the mean time, the Windows freeze. Mouse right click no response. No status bar at the bottom of the screen. The whole desktop is blank. All icons on the desktop disappeared. I have to log-off and re-login to re-active everything. &nbsp; I also tried to copy&nbsp;other VI's in other library files. Same thing happened. &nbsp; Thanks, Jing I&nbsp;was using Labview 8.2.1 when I had this crash, though I have Labview 7 installed in the same computer. When I "copy the file to some other place", I mean: Click the *.vi file, ctrl-c and ctrl-v to some other directory. Thanks, Jing ...

&quot;no disk&quot; error
I came accross an interesting problem with LV today (LV 8.20, Professional Development system, Win XP Pro) &nbsp; I opened a .vi directly from CD by double clicking the file in Windows explorer while LV 8.20 was showing its start screen. [I don't think it's relevant but the file was "Clear Specific Error.vi" from the LV Intermediate I course CD.] &nbsp; I Quit LV and removed the CD &nbsp; Attempts to restart LabVIEW gave an error box titled "LabVIEW.exe", and containing the text "There is no disk in the drive. Please insert a disk into drive E", with buttons "Cancel", "Try Again" and "Continue". Pressing any of the buttons&nbsp;simply caused the error box to re-appear. [My CD maps to drive E:] The only way to get LV running was to put a CD (any CD) into the drive and "Try again". This allowed LV to start. &nbsp; On the start screen I selected the E:\.....vi from the recent files list. As the CD I had inserted was not the CD I had read the .vi from, I got the expected file does not exist message with an OK button. After pressing OK, the E:\...vi was removed from the recent files list, and a subsequent start of LV without the CD in the drive worked. &nbsp; Has anyone else experienced the same or similar problem? &nbsp; Whilst I can now fix/avoid this problem again for CD's, there remains the possibility of having loaded a&nbsp;.vi over a network share, and having th...

An exception occured within the external code called by a Call Library Node.... was stopped at node &quot;&quot; at a call to &quot;IMAQ RejectBorder&quot;
Hi, I get occasionnaly this message when running an executable which has been installed from the same machine: &nbsp; LabVIEW: An exception occurred within the external code called by a Call Library Node. This might have corrupted LabVIEW's memory. Save any work to a new location and restart LabVIEW. VI "1629-00_200-Main.vi" was stopped at node&nbsp;"" of subVI "IMAQ RejectBorder" &nbsp; It is really anoying because the executable can run without any poblems for many hours and then the message comes and can crash the application &nbsp; Any advice? &nbsp; Version: LV 8.2 IMAQ Vision 8.2 &nbsp; Rodolphe Naoux ...

plug-in &quot;not installed&quot; in my LabVIEW project's &quot;Build Specifications&quot;
I moved my LabVIEW project from one computer to another, now when I click on any item under the project's "Build Specifications", I get an error reading "The plug-in for the selected item is not installed on your system." Does anybody know how to fix this? I have no idea what this "plug-in" is.Attached is a screenshot. plug-in error.PNG: http://forums.ni.com/attachments/ni/170/222664/1/plug-in error.PNG ...

LV8,5 Dev Suite install, error &quot;Measurement Studio for VS2003 not installed&quot;&quot;
Hi guys, &nbsp; Installing LabVIEW 8.5 Developers suite, installed LV8,5 OK, but all otehr products (CVI, Studio, etc) come up with error messages as per attached photo, "measurement Studio for VSXXXX not installed" &nbsp; When should I have installed this ? which DVD has this ? &nbsp; Any help apreciated &nbsp; Cheers &nbsp; Mathew LV8.5Install.GIF: http://forums.ni.com/attachments/ni/170/272665/1/LV8.5Install.GIF Thanks for the replys. The thing is,I have brought the Developers Suite www.ni.com/suite/ ($7070 NZD),which includes the CVI toolkit&nbsp; and a whole lot of other stuff, surely the required 3rd party software required should be included in the package ? Will give the install anther go, using default settings and see what happens Message Edited by Matwelli on 09-18-2007 11:58 PM ...

Memory is full during &quot;Save As&quot; of LabVIEW 8.5 project
Good Morning All, &nbsp;&nbsp;&nbsp;&nbsp; Have run into a weird issue while trying to rename a LabVIEW 8.5 project. I've got two projects that ended up having the same names (one by me, one by another engineer). I want to open both at the same time, so I figured I'd open the one and do a "save as", or a "rename". The first time it started processing, doing file loads, and then hung looking for a sub-vi, with the search address pointing to the .llb in the LV 8.5 directory where I manually located it. Once that was resolved, and the original project saved I tried again. This time it did a bunch of loading and then gave me an error box with the message:&nbsp; "LabVIEW:&nbsp; Memory is full.&nbsp; Cannot save project 'original project name.lvproj'" This isn't a big project, the machine is a new HP Compaq dual core 2.8GHz with 1.5Gb of ram, so I don't really think that it should be generating anything that big. This happens with either a "save as" or "rename". I ended up just changing the names of the .lvproj .aliases files to the one I needed and it seems to load ok, but it would be nice to understand what is happening here. &nbsp; &nbsp; This is interesting behavior, since NI actually ensured that you would now have the ability to Save As and Rename a project with the <a href="http://www.ni.com/pdf/manuals/371780c.pdf" target="_blank">release ...

Why do I receive a &quot;Fatal internal error: &quot;fpsane.cpp&quot; line 399&quot; when saving?
Why do I receive a&nbsp; "Fatal internal error: "fpsane.cpp" line 399" when saving my VI? &nbsp; Thank you. Gustavo Hi Chris, But I could not solve the error that way. Actually, Labview is crashing with this error at any time when I am writing my VI. It simply crashes even if the VI is not running. I think the problem is not in my VI, because&nbsp;it runs normally in another machine, but must be with the Labview installation. I have reinstalled Labview three time already and the error continues. Any other ideas? Thanks, Gustavo hum... not yet. &nbsp; I reinstalled LAbview 8.2 for the 3rd time... nothing happened. The VI I am trying to run is the example 4128.vi we can find in the forum. It is still crashing with the same error when I try to save or save as... or sometimes before the VI starts to run when I do any alteration. I think the error might be related to saving the VI. The problem happens to other VIs as well, but only those that are using IMAQ. &nbsp; Hope you can help me... Tks, Gustavo I am agree with <a href="http://forums.ni.com/ni/view_profile?user.id=91046" target="top"> gutoassi</a> , even though labview 8.2.1 releases are very useful, it still have something to be depurated, my VI is ok and I have the same error fpsane.cpp line 399. In order to give a clue with this issue, I am working with CINs and visual C++, some times it just work fine but in a very inconsistent way it crashes som...

Using &quot;To-upper-case&quot; on cluster with Enum (LabVIEW 8.2)
Hi folks, &nbsp;&nbsp;&nbsp;&nbsp; The following example won't compile on my installation of 8.2 ! &nbsp; &nbsp; <img src="http://forums.ni.com/attachments/ni/170/225670/1/ClusterErr.jpg"> &nbsp; Cheers.Message Edited by tbd on 01-23-2007 09:21 PM ClusterErr.jpg: http://forums.ni.com/attachments/ni/170/225670/1/ClusterErr.jpg ClusterErr.vi: http://forums.ni.com/attachments/ni/170/225670/2/ClusterErr.vi It fails the same way under LabVIEW 8.0. Clearly something is not handled properly. (Of course I don't quite see the general&nbsp;usefulness to use "to uppercase" on a simple&nbsp;enum. ;)) altenbach wrote: (Of course I don't quite see the general&nbsp;usefulness to use "to uppercase" on a simple&nbsp;enum. ;)) (tbd momentarily ponders: "Why does it seem there's always something Altenbach doesn't quite see?") &nbsp; Oh, gee,&nbsp;do it (enum to upper-case) all the time&nbsp;when I forget and type enumerated-case-values in all upper-case. :smileywink: &nbsp; &nbsp; <img src="http://forums.ni.com/attachments/ni/170/225670/1/ClusterErr.jpg"> &nbsp; Indeed it doesn't compile.&nbsp; But the To Upper Case VI handles numbers as ASCII codes.&nbsp; How would converting an enum value of 97 to 65 be useful to you?&nbsp; Are you trying to capitalize the strings in the enum's typedef?&nbsp; A case structur...

VI &quot;FindInstrumentDrivers.vi&quot; was stopped at node &quot;&quot; at a call to &quot;IDF_WsIdOpen.vi&quot;
This what I get trying to download Instrument Drivers in LabVIEW 8.2. LabVIEW 8.6 doesn't succeed either. any ideas? Could just be an intermittent server problem. Does this happen all the time? At what point does it fail? When you first launch it, after you login? The network traffic indicates that it uses port 3339. Is this being blocked by your firewall? ...

Web resources about - Build error after upgrading from 8.2.1 to 8.5 &quot;Error 1055 occurred at Invoke Node...&quot; - comp.lang.labview

Resources last updated: 3/19/2016 1:11:48 PM