Home > Labview Error > Labview Error 1172 .net

Labview Error 1172 .net

When distributing built applications, make sure the target computer has the .NET Framework installed that corresponds with the called .NET assembly. Showing results for  Search instead for  Did you mean:  Reply Topic Options Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark All rights reserved. I see that FTDI is now in VCP mode (virtual Com Port). http://jvmwriter.org/labview-error/labview-error.html

It might be easier to try to create a simple .EXE from C#/VB to load your assembly as a test case and get more detailed exception messages (7.1 doesn't support the Can't a user change his session information to impersonate others? When does bugfixing become overkill, if ever? AError 1172 is a generic LabVIEW error indicating there was an error thrown during a .NET assembly call.

I'm working in LV2010. Lycangeek Active Participant ‎08-09-2007 12:33 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator And also check outhttp://detritus.blogs.com/lycangeek/2005/05/network_paths_a.html Brian The class has two methods. Richard2950 Member ‎10-13-2004 01:47 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator If the vi and the .NET

It's easy! Brian Tylerhttp://detritus.blogs.com/lycangeek 0 Kudos Message 9 of 10 (12,558 Views) Reply 0 Kudos Re: Why am I getting Error 1172 when trying to invoke .NET assembly? LabVIEW Register for the community · Log in · Help ForumsCategoryBoardDocumentsUsers turn on suggestions Auto-suggest helps you quickly narrow down your search Hot Network Questions What are the legal and ethical implications of "padding" pay with extra hours to compensate for unpaid work?

DLL error picture.doc Share this post Link to post Share on other sites vugie 153 Extremely Active Members 153 388 posts Location:Warsaw, Poland Version:LabVIEW 2009 Since:2006 Posted May 27, 2011 I.e. The DLL communicates through a USB port on the PC. Sign In Now Sign in to follow this Followers 0 Go To Topic Listing LabVIEW General All Activity Home Software & Hardware Discussions LabVIEW General .NET Control Error 1172 - Only

Sign in here. Is a food chain without plants plausible? A software engineer in Mexico wrote a DLL in C# that LabView calls, then the DLL sends commands to perform some of the tests. Please turn JavaScript back on and reload this page.More documents in Precision DACs Where is this place located?EngineerZoneAll PlacesData ConvertersPrecision DACsLog in to create and rate content, and to follow, bookmark,

If the issue still remains, after updating LV-Link, then please reference the Knowledge Base article titled "Updating LV-Link Software". Data Translation is a leading designer, manufacturer, and provider of her latest blog Here is a good description of it : http://digital.ni.com/public.nsf/allkb/B15CE9F2715434C386256D3500601878and here is an example of what may cause the 1172 error: http://digital.ni.com/public.nsf/allkb/0C5833C1B73EE385862572CB0025EAC9 But, below is an example of the error Cart|Help KnowledgeBase Request Supportfrom an engineer NIHome > Support > KnowledgeBase EnglishKoreanChinese(Taiwan)JapaneseSpanish 21 ratings: 2.23 out of 5   LabVIEW and .NET Exceptions Primary Software: Presumably the author of the assembly has a test harness of some description.

Mark Share this post Link to post Share on other sites Create an account or sign in to comment You need to be a member in order to leave a comment his comment is here Only if you want to bypass your Mexican DLL. Sign In Sign In Remember me Not recommended on shared computers Sign in anonymously Sign In Forgot your password? Now this seems to work with no error.

More details are described in the diagram of the attached VI. Go to Solution .net error 1172 psuedo Member ‎06-27-2013 07:12 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator in Process Flow.vi Any ideas? http://jvmwriter.org/labview-error/labview-error-ni-488.html Then I add a second method (called lvobject), this one has an input which is a generic Labview object (I leave it unwired, i.e.

Share this post Link to post Share on other sites Clinto 0 LAVA groupie Members 0 5 posts Version:LabVIEW 2010 Since:2009 Posted May 27, 2011 Thanks for the reply Vugie. My first thoughts with Asian-only issues are the problems (and Labviews issues) with Unicode string handling. the method does nothing).

I'm forwarding all questions/comments to the development team.

A private assembly will allow access by a single application, where a shared can be used by multiple applications. I tried doing some web searching on the error message, and it's all about playing around with the various security settings and demands - running code on a network share is Jump to content Calling External Code Existing user? How to create a company culture that cares about information security?

I will forward your questions/comments to the engineers in China. Brian Tylerhttp://detritus.blogs.com/lycangeek 0 Kudos Message 6 of 10 (12,587 Views) Reply 0 Kudos Re: Why am I getting Error 1172 when trying to invoke .NET assembly? System.ArgumentNullException: Key cannot be null. 00000015 114.37963104 [3404] Parameter name: key 00000016 114.37963104 [3404] at System.Collections.Hashtable.get_Item(Object key) 00000017 114.37963104 [3404] at NationalInstruments.LabVIEW.SyncInvokeTable.LookupControl(Object key) 00000018 114.37963104 [3404] at NationalInstruments.LabVIEW.DNRuntime.InvokeMethod(Int32 invokeType, Type type, http://jvmwriter.org/labview-error/labview-error-7.html The C# programmer tested the DLL pretty thoroughly, including downloading LabView 2011 and making sure LabView could call the DLL.

PJM Share this post Link to post Share on other sites Clinto 0 LAVA groupie Members 0 5 posts Version:LabVIEW 2010 Since:2009 Posted May 28, 2011 Not exactly what you Sign In Now Sign in to follow this Followers 2 Go To Topic Listing Calling External Code All Activity Home Software & Hardware Discussions LabVIEW (By Category) Calling External Code Getting Both the development environment and the executable use the exact same DLL code. Just buy one of the various USB to RS232 converter (I personally use Keyspan) then use VISA from LabVIEW to communicate (over RS232) with the DUT.

Then I wrote a new function that wrote to a file and called that when the VI loaded. Labview needs to be run as administrator. 0 Kudos Message 4 of 12 (2,059 Views) Reply 0 Kudos Re: .net error 1172 søren_hallberg… Member ‎11-15-2013 04:08 PM Options Mark as New I realize that this is probably not an option at that stage, but I though that I would mention it. This is one way to make GMap return Lat and Lng coordinates from physical address info.

Richard2950 Member ‎10-14-2004 09:53 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Thank you, Philip. thanks J Share this post Link to post Share on other sites Mark Smith 32 Extremely Active Members 32 330 posts Location:Utah Version:LabVIEW 2011 Since:1995 Posted March 18, 2009 QUOTE Sign In Sign In Remember me Not recommended on shared computers Sign in anonymously Sign In Forgot your password? Philip_Courtois Active Participant ‎10-18-2004 11:23 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Hi Richard,Here�s a KnowledgeBase describing

Can you send that out to China and see what error log it produces (if any). Other considerations for calling a .NET Assembly from LabVIEW are: Private assemblies must be placed in the same directory as the calling application. I attached an error indicator to the invoke node, which is showing me this error:   Error calling method InstrumentDataGridView.InstrumentDataGridView.LabVIEW_FillTableFromXML, (System.ArgumentNullException: Key cannot be null.Parameter name: key) System.ArgumentNullException in Experiment UI.lvlib:Experiment If you have LV 8+, then you can get more detailed information on the error (maybe not in this case...but worth a shot) by getting debugview (http://www.microsoft.com/technet/sysinternals/Miscellaneous/DebugView.mspx) and running that when