Home > Labview Error > Labview Error Code 1172

Labview Error Code 1172

I created the assembly using the LabVIEW .NET browser that I downloaded from NI. Poor|Excellent Yes No Document Quality? It captures the full .NET Exception and dumps it out. How to describe very damaging natural weapon attacks from a weak creature Why are there two words: "uttermost" and "utmost"? weblink

Sign In Sign In Remember me Not recommended on shared computers Sign in anonymously Sign In Forgot your password? MattViewX.007 Member ‎08-08-2007 06:02 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator I am having this exact problem That is the driver for the serial-to-USB converter (on the little dongle that is plugged into the USB port). All rights reserved. http://digital.ni.com/public.nsf/allkb/B15CE9F2715434C386256D3500601878

For information about installing to the GAC, please see MSDN How to: Install an Assembly into the Global Assembly Cache. The “parameters” output from the constructor does not return the references that were input to the constructor therefore the references were left open. 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 added the "Close .NET Reference" after the invoke node today and do not know if it has fixed the issue as it needs to run overnight to find out. The Vi works great on my computer but once I moved it to the network it no longer works. Again thanks for all of your support it is greatly appreciated. .NET issue.png ‏123 KB 0 Kudos Message 6 of 7 (1,247 Views) Reply 0 Kudos Solution Accepted by Hot Network Questions Why are Matthew, Mark, and Luke called 'synoptic' gospels?

We sent the DLL from Mexico to the engineers in China, and every time LabView calls the DLL, we get error 1172. Lycangeek Active Participant ‎08-09-2007 12:32 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator How exactly are you increasing I do have the vi in the same directory as the .NET assembly, and the assembly has been added as a reference to LabVIEW. http://forums.ni.com/t5/LabVIEW/quot-Error-Code-1172-quot-NET-Invoke-Node-returns-null-after-20/td-p/2570709 Sign in here.

This is the error Code 1172: Error creating instance of SSPParameter in assembly SPCSDK.Protocols.SSP.SSPParameter, SPCSDK.SSP, Version=1.0.16.25927, Culture=neutral, PublicKeyToken=null, (SPCSDK.Util.Error.InvalidInputParameter: Invalid input parameter(s).) SPCSDK.Util.Error.InvalidInputParameter I have attached an image of the Then I wrote a new function that wrote to a file and called that when the VI loaded. You could probably log the reference value, the errors and maybe some other relevant values. BUT, the Invoke Node gives me more options with the SAME DLL than the other PC!

MattViewX.007 Member ‎08-10-2007 10:25 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator This Vi is running LV 7.1 I have closed the references on the "SSPParameter Create UN8" invoke node. How to professionally handle sexist remarks by a student? All rights reserved.

The sdpAPI1.dll is a .NET assembly. have a peek at these guys I hope this helps someone if ever they fall into the same problem I had. 0 Kudos Message 5 of 5 (572 Views) Reply 0 Kudos All Forum Topics Previous Topic Brian Tylerhttp://detritus.blogs.com/lycangeek 0 Kudos Message 9 of 10 (12,730 Views) Reply 0 Kudos Re: Why am I getting Error 1172 when trying to invoke .NET assembly? My question is: 1) Is there a better way of referencing the dll in my VI other than using a Constructor (...then getting the properties?) or am I doing this correctly

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. Why are you passing the same reference to the +.NET Error Info function as both a scalar and an array? 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 http://edsdefence.com/labview-error/labview-error-1172-net.php System.ArgumentNullException: Key cannot be null. 00000009 85.75064087 [3404] Parameter name: key 00000010 85.75064087 [3404] at System.Collections.Hashtable.get_Item(Object key) 00000011 85.75064087 [3404] at NationalInstruments.LabVIEW.SyncInvokeTable.LookupControl(Object key) 00000012 85.75064087 [3404] at NationalInstruments.LabVIEW.DNRuntime.InvokeMethod(Int32 invokeType, Type type,

In my case, I already have all the DLLs required, I copied the whole folder containing the program I wanted to run though LabVIEW (see img1.jpg) The sub-vi I'm running Lastly, when using the constructor node, if you change the selected file by one of the same name (example:Me comparing all the ILAS.Headless.dlls I had) LabVIEW does not update the functions Or sign in with one of these services Sign in with Facebook Sign in with Twitter Sign in with LinkedIn Sign Up All Content All Content This Topic This Forum Advanced

In one of my sub-VIs I call a .DLL (ILAS.HeadLess.dll) in order to bring up a UI of some 3rd party hardware (See Error 1172.jpg).

The attached Word doc mentions a driver from "FT". Unfortunately, LabView and the DLL don't seem to want to talk to each other. You should also look through the documentation of the PerformanceCounter class to see which names it expects. If you need more information I will provide it ASAP - but there will probably be about a one-day delay, because I have to forward the questions to the team in

Neither of these functions throw that type of exception. Do you need to constantly obtain and destroy a new reference to the same named notifier? I realize that this is probably not an option at that stage, but I though that I would mention it. this content I have opened it and viewed it and scanned it for anything malicious.