11-29-2021 09:12 AM
This first screen shot has the error message in it I'm currently trying to resolve.
This second screen shot is entire view of the vi on two monitors I apologize for the appearance of it but I had to stretch the application over to different monitor screens.
I keep getting a 1172 Property Node (Arg:1) and I don't know why. Any help with this issue would be great.
11-29-2021 11:27 AM
Put a probe on the reference wire leading in to the property node that generates the error. See if you get a null reference (0x00000000) or a real one (basically anything else).
I'm betting you'll see that it's a null reference. If so, there's probably some sort of action you need to call on the wire there to actually start the connection before it will output a working one...
If it's not a null reference, do you maybe have some sort of example code in C# or whatever that you're working off of to create this? Maybe you could get some? Whatever the "ctl_LoginProcess" is probably has some documentation to it that maybe would give a hint as to something you skipped by accident.
12-01-2021 10:20 AM - edited 12-01-2021 10:25 AM
I tried putting a probe in there. It is coming up null, but I still can't figure out why.
01-19-2022 09:22 AM
Does anyone know if my issue with the 1172 property node error is being cause because of the Microsoft.VisualBasic version and CLR don't match. I have the same mismatch condition for the ctl_LoginProcess as well. The version and target CLR are different on both. If so I can I solve this issue?