02-21-2024 03:12 AM
I am getting error code: 205103168 (0x0C39A040) source: "System Exec.vi. Command was "ping -n 1 -w 100""
Yes, I am aware that the command is ill formed and doesn't ping anything. When executed, the standard output says that I should specify an address, but without error.
I was unable to replicate this error myself, it is from error log from a client. So I suppose this error occurs rarely. I found that the System Exec can throw Windows errors too, but for this error I found no record with Google. So I doubt it is a Windows error. Any clues?
Solved! Go to Solution.
02-21-2024 08:50 AM
@VitSlay wrote:
I am getting error code: 205103168 (0x0C39A040) source: "System Exec.vi. Command was "ping -n 1 -w 100""
Yes, I am aware that the command is ill formed and doesn't ping anything. When executed, the standard output says that I should specify an address, but without error.
I was unable to replicate this error myself, it is from error log from a client. So I suppose this error occurs rarely. I found that the System Exec can throw Windows errors too, but for this error I found no record with Google. So I doubt it is a Windows error. Any clues?
Typically an undefined error is a custom error that didn't get added into the error.txt (or the file was left out of the deployment). If you are the developer, buried within your code, someone said, "throw this error when something happens".
02-21-2024 03:22 PM
While System Exec looks like it is the Command Line window, it is not! It directly Creates the process from the command line and that also means that whatever the process returns as return value will be interpreted as error code.
If you want the command line handling you have to add the according command to the System Exec command line:
cmd ping ………..
This will launch cmd.exe and pass it the rest of the command line to execute. That will give you a similar behavior than what you get in the Command Line window.
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YGivCAG&l=nl-NL