LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Command Prompt argument cause error 17201

Solved!
Go to solution

I have a quick question in regards to command line arguments.

Right now, if I execute my .exe file through cmd and add an argument like 1234, the program will throw an error as seen in the attached image. However, if I were to put a character such that the argument is -1234, then the error is not going to be visible.

 

I have tried to search for documentation and such but found nothing. 

Ideas?

 

 

I also assumed that maybe because it is a number that it's causing the error to pop up. For example, if I put .../testexec.exe 1234, the error would show up. It would also show up if I use "1234" but not for '1234'.

 

Any help would be apperciated. thanks!

0 Kudos
Message 1 of 3
(2,613 Views)

I see that you are using TestStand and the error you are getting seems specific to that product, so I suggest you repost this question to TestStand board or ask a moderator to move it there.

In the meanwhile, I was able to find this help page that speaks about command line parameters passed to executables: maybe it can help you.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 2 of 3
(2,555 Views)
Solution
Accepted by topic author pinguu

This error is fixed.

 

It was the cause of TestStand taking the argument and trying to process the command line.

After disabling the setting through API, there was no more issues.

 

TSUI_ApplicationMgrSetProcessCommandLine()

0 Kudos
Message 3 of 3
(2,446 Views)