System Command not executing command

Help Please

I have a windows command that when used in cmd.exe on the server, runs just fine. Yet, when I run that same command in the syscmd node, it does not work the same. Should it not?

To get specific, I am calling on a 3rd party process to run - which it does just fine when I run it from the command prompt on the server - but when I run it from syscmd node, it is saying that process is not recognized. Why is it found when I run the command directly but not when I run it from syscmd node?

Successful command on served in the command prompt: cd /d D:mypathta_folder_folder & newman run mycollection.json

From log file in flow:
Full system command: cmd.exe /C cd /d D:mypathta_folder_folder & newman run mycollection.json
Command output (combined): 'newman' is not recognized as an internal or external command,
operable program or batch file.

Any help is appreciated!

Thank you!

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

All comments

unknown

You might need to escape the & ?

robert-canham

it sounds like newman isn't part of the path when the syscmd node starts. If you specify the full path to newman it might work.

unknown

that was my other thought, maybe you are not looking for the file where you think you are. I know that there are times when I can just say "D:" and times when I have to use the fully qualified path and file name. - email attachments is an example of that, I think.

plancor

Maybe grasping at straws, but did you verify the Command Execution Parameters "run as user" authorities?

chris-mccullough

WOW! Such quick replies! Love this place. These are great suggestions. I am going to look into all 3 now..
'newman' is a module in Node.js which works with Postman..

It is basically my API workaorund to send an XML file to a vendor since the WebNode cannot handle the xml/file content type. So, I have Postman doing the API send of the file and this syscmd is supposed to trigger it. It works when I run it directly in cmd prompt so that is why I thought it would work in syscmd...

Let me take a look at these...brb

chris-mccullough

Oh and btw, I have added this as an enhancement request...so if you see it, thumbs up because we are getting bombarded with vendors wanting APIs and not flat file sends. I think IONI can do a lot of this, but we are not using ION yet...

Ray Juodis

command line concatenation on system command node may not be supported - try creating a bat file with commands in it instead.

unknown

To run a System Command in SYSCMD, you will need to add an extra backflash '' to the path.

Something like this (copy "D:\CopyFrom\Filename.txt" "D:\CopyTo\FileName.txt" ) without parenthesis

or if you are using the variable then copy <!DirCopyTo> <!DirCopyTo> under the Command box. If the directory is a network server then you need to double those two backflashes like: "\\servername\FileDir\FileName.txt" without quotes. Hope that helps.

jose-sahagun

I used Postman to create my API call and utilizing WebRun node to perform the API call.

chris-mccullough

ok, I played with the sys command connection a bit, that could not get it to run - dang like the idea though

chris-mccullough

I tried finding the newman path but I can not

chris-mccullough

good idea - let me try bat file approach

andy

Run echo %PATH% from the command line. If you can run newman from the command line without the absolute path, the executable is likely in one of those directories.

andy

Command concatenation is supported in Sys Commands. I usually use && which will only continue if first execution is successful.

kyle-tucker

From what I remember you can concatenate commands in the SYSCMD node. However, I frequently had to set the drive (popd and pushd) That gives it the specific server location rather than "D:". Even though it's running from the same server I sometimes had issues with this.

chris-mccullough

Thanks Jose - I tried this but the issue is that the WebRun node itself can not handle xml/file sends.....it can do xml posts, but to send an actual file is not supported. Others have created PS and Perl to do the API send, which I may end up doing if I can't do this...

Ray Juodis

I don't recall the exact syntax but with system commands you can redirect the console errors to a file which you can then examine. Also, if you are able to log onto the server itself the OS sometimes captures certain errors as well. Good luck.

Ray Juodis

If newman is not recognized it is not located in an available path for the IPA service to run it (logging in as Lawson admin may not have the same path variables as the IPA service). If newman was installed and located in an OS directory tree above where the IPA service account runs even giving it absolute path in the syscmd node will probably not work. The IPA service account has to have access to that path as well. I assume you are uploading your flow onto the server and running it. Try running the flow in debug mode and query some of the variable or consider assign the echo path and compare that string of directories to when you log in interactively and echo path to the command line. You may need a configuration added as JReese says or you may need to have a path defined at the OS level on the server itself. You are on the right path, (bad joke sorry).

unknown

I've been following for my own curiosity - thank you all for your input, it's great to learn from others!

Question about neuman... Would you need an extension on this in your code like .exe? You have an extension on my_collection.json. Could this be why SysCmd node "cannot" find neuman?

chris-mccullough

Great idea Tammy...worth trying.. I will let you know!

chris-mccullough

So, I tried running :C:folderfolderfolder
ewman.cmd -v

Which, btw, worked just fine manually in cmd prompt.

But with IPA, it now gives me '"node"' is not recognized as an internal or external command

So, bad, but different. I am googling this now

unknown

2 quick things I just thought of, but don't see here (sorry if I missed them)

Have you tried selecting a different Execution Mode in the syscmd's properties?

You might want to open up your lpd as a text file, find that syscmd node, and look at what IPD has done to your command string.

unknown

Wow... open as a text file? I've never heard of that. I'll have to try it. Glad I was following along.

unknown

We are upgrading IPA to v11 (LSF is still v10) and changing the Execution Mode in the syscmd's properties is what I had to do to get the basic 'bcp' Bulk Copy Program to work again. I don't think it applies to your situation, since you have a 'SysCmd' working elsewhere, but for those following along.

Copyright © 2025 Infor. All rights reserved.