Home > Labview Error > Labview Error 1379

Labview Error 1379

Please re-enable javascript to access full functionality. I'm glad you're up and running. 0 Back to top Back to VI Package Manager (VIPM) Reply to quoted postsClear JKI Discussion Forums → JKI Products → VI Package Manager Thanks for any help anyone can offer in solving this. LabView shutdown and restarted. Source

So, I don't pick which card to send stuff on and I'm not sure how LabVIEW decides (or maybe the decision is passed down to Windows?), but it works for us. Now, our two cards have IP addresses that don't "overlap". Please tell us why. After he disabled the firewalls, the installation proceeded normally.Thanks for the help!Eldon Zacek 0 Back to top #9 Jim Kring Jim Kring JKI Team 1,267 posts Posted 27 September 2010 - http://digital.ni.com/public.nsf/allkb/310773417BAD0E9C86257341005466E5

I have also tried to use the Logos.ini trick in the c:\windows directory and used both mac addresses of my wireless adapter and the VPN as suggested by an NI AE Bout ready to build a seperate data transfer file rather than trying to use the buggy built ins. 0 Kudos Message 8 of 13 (1,355 Views) Reply 0 Kudos Re: Error All rights reserved. Share this post Link to post Share on other sites Ton Plomp 164 How many lines per hour?

Related Links: KnowledgeBase 268B8SXQ: Error 1003 When Using VI Server in a LabVIEW ApplicationKnowledgeBase 5I8AK4RQ: Enabling VI Server Support for an ExecutableWhite Paper: VI-Based Server - Developing a ServerDrivers and Updates: We contact NI to have some inputs and the answer was: ...Another thing we can try is to put the device driver you are using on the server computer. Everything appears to be setup correctly, Port #, etc.. Why is this occurring?

And the error doesn't appear when running the app from the run-time version 6. Pat This is really all about TCP IP routing tables and how they are setup. An attempt was made to read from an empty buffer. −1967362021 File already exists. −1967362020 The provided refnum is invalid. −1967362019 A null refnum was provided as input. −1967362014 Class not VI Server will not work with two network cards Sign in to follow this Followers 0 HELP!

I thought my PC had died when I got this error but now it's as good as new. But we need to install the minimum drivers on the PC that will run the app Vi Server. And, what is the compoment installedon the server by NI-DAQmx 8.1 that solve the problem? Add Comments 1 2 3 4 5 My Profile|Privacy|Legal|Contact NI© National Instruments Corporation.

It is a client's PC that is having problems and they have been busy for the last few weeks. http://www.devsuperpage.com/search/Articles.aspx?G=6&ArtID=782958 These can block VIPM's ability to communicate with LabVIEW.Please let me know if that works.Thanks,-JimFinally caught back up with the client. I want to install the minimum on my server PC, not all the NI-DAQmx 8.1 drivers. I owe you a drink!” Stephen: - 7 Months Ago “I was getting loads of errors until I tried this.

No Dice ~,~ Norm 0 Kudos Message 6 of 13 (1,385 Views) Reply 0 Kudos Re: Error 1379 occurred at Open Application Reference JMota Active Participant ‎04-19-2007 03:07 PM Options Mark http://robertwindows.com/labview-error/labview-error-1050.html You're a lot more likely to get an NI AE to help there than here. My problem was resolve by the onlyfact to install NI-DAQmx 8.1 on the PC that's run the VIServer. This list can be found by looking at the options in LabVIEW under Tools»Options»VI Server: Machine Access.

Jump to content Remote Control, Monitoring and the Internet Existing user? Repair Labview Error 1379 Posted: This is a suprisingly common error, and I have a Repair! Maybe the problem is with VI server specifically. have a peek here Thanks, Eldon Zacek Attached Files June_02_2010.txt 9.45KB 202 downloads 0 Back to top #4 Michael Aivaliotis Michael Aivaliotis JKI Team 501 posts Gender:Male Posted 03 June 2010 - 07:51 PM Micheal,Here

So if I try to connect to 192.168.1.44, there is only one card this will work on. Now, our two cards have IP addresses that don't "overlap". Refer to the KnowledgeBase for more information about correcting errors in LabVIEW.

That's the next thing we are going to try to see if that fixes the problem.JMota 0 Kudos Message 7 of 13 (1,378 Views) Reply 0 Kudos Re: Error 1379 occurred

In our case we are not going through any VPNs or anything like that.Have you tried downgrading the remote machine to use the LV 8.2 run-time engine? VI Server will not work with two network cards Started by John Lokanis, January 10, 2007 6 posts in this topic John Lokanis 76 The 500 club Members 76 786 SulzerApplications EngineerNational Instruments 0 Kudos Message 2 of 13 (1,732 Views) Reply 0 Kudos Re: Error 1379 occurred at Open Application Reference hamenarin Member ‎04-25-2006 02:38 PM Options Mark as New I have another machine on the corp net side that is running a LabVIEW app as a server.

If it can't resolve a specific name, it denies access.Therefore, if there are devices on the network without a resolvable network name, use *, IP addresses, and IP wildcards in the All rights reserved. | United States MY ACCOUNT   INNOVATIONS SHOP SUPPORT COMMUNITY Home Community Home : Discussion Forums : Most Active Software Boards : LabVIEW : Error 1379 with Vi Verne D. // Software R&D // National Instruments 0 Kudos Message 4 of 5 (709 Views) Reply 0 Kudos Re: Error 1379 with Vi Server lajf Member ‎09-03-2010 12:48 PM Options http://robertwindows.com/labview-error/labview-error-6.html Solution: A VI Server connection will be denied with Error 1379 if the client PC or device does not have a name on the network.

Poor|Excellent Yes No Document Quality? Cart|Help You are here:NI Home > Support > Manuals > LabVIEW 2012 Help Security Error Codes »Table of Contents LabVIEW 2012 Help Edition Date: June 2012 Part Number: 371361J-01 LabVIEW VI Server binds itself to the first network cardit sees and will not talk to your second card. Click 'Start Scan' to scan your PC for errors If errors are found, click 'Next' then 'Repair Now' to Repair the problem You may need to reboot your PC for the

The router can take care of the network address translation and allow only the connections between your client machine and the server machine. One is for connection to the corporate net and one is for connection to a local test net where my DUTs are attached. It solved the problem. The problem:the logos installer starts but I obtain an empty window when they ask to select features to install (see picture attached) ???

Visitor Comments 8 Comments for "Want to Repair Labview Error 1379?" Shirlee - Today “This Repaired the Labview Error 1379 message. I have until the end of the day to get this system working. Why not to set up router between the test network and the corporate network. All sorted now.

If you have any comments or questions, please feel free to submit a message using the form below. We aren't using VI server, just raw strings over TCP. Ensure that LabVIEW is installed properly. 1368 Unable to authenticate because LabVIEW failed to load an NI Security library that is required to authenticate access. 1379 The user failed a security Go to Solution Error 1379 with Vi Server lajf Member ‎08-30-2010 10:06 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to

Showing results for  Search instead for  Did you mean:  Reply Topic Options Start Document Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Try to connect to my VI Server and it works! The client can not put this laptop on the network due to company policies.I have attached the screen shots you requested and tried a few other things today.Under "Tools->Options", I had If I disable the network card in the client that is on the local test net (leaving the corp net connected) then everything works fine.

After that, I install only the logos.msi and press Next butten even if there is nothing to select in the features window and it starts the installation. Thanks, Scott 0 Kudos Message 5 of 13 (1,563 Views) Reply 0 Kudos Re: Error 1379 occurred at Open Application Reference NJKirchner Member ‎04-18-2007 08:48 PM Options Mark as New Bookmark