Exec node is not responding

General
22

yes, if the exec node executes for 1st time with out any redeployment it will generate the file

23

So is the problem that the file is not being created?

24

The problem is exec node on 1st deployment is not executed. But on redeploy without changes it is working great

25

I am now trying out with bigExec node.
as EXEC node is not working out for me.

Can you please help me in sending the file paths(containing ) as strings(the string that contains three strings separated by a space, each string containing a full path to a filename) like above to the Big Exec node?

I need to send below to bigEXEC node as a parameters
"""+msg.payload.inputFilePath+""" +" "+ """+ msg.payload.outputFilePath +""" +" "+ """+msg.payload.logicFilePath+""";

I mean to say i need to send 3 file paths in a string like below with real data
"C:\input_sample-xml1.xml" "C:\transformed_input_sample-xml1.xml" "C:\Users\DecryptedXML-text.imo"

26

with normal exec node, could you modify the function "sending parameters" to convert backslashes to forward slashes & add some node.warn so we can see what you are generating...

//check before
node.warn(["msg.payload.outputFoldePath", msg.payload.outputFoldePath])
node.warn(["msg.payload.outputFileName", msg.payload.outputFileName])
node.warn(["msg.payload.logicFilePath", msg.payload.logicFilePath])

//replace \ with /
const outputFilePath = msg.payload.outputFilePath.replace(/\\/g, "/");
const outputFoldePath = msg.payload.outputFoldePath.replace(/\\/g, "/")
const logicFilePath = msg.payload.logicFilePath.replace(/\\/g, "/")

//check after
node.warn(["outputFilePath", outputFilePath])
node.warn(["outputFoldePath", outputFoldePath])
node.warn(["logicFilePath", logicFilePath])


const filePath = `"${outputFoldePath}" "${outputFilePath}" "${logicFilePath}"`;
node.warn(["filePath", filePath])
msg.payload = filePath;

return msg;
27

Thank you everyone for the support.
The issue has been automatically solved when i updated the node-red version to ~1.3.5.

28

Please be more explicit for future readers.

What issue? The exec node issue? the bigExec issue?

What version of node-red were you using?

PS: V2.2.2 is the latest version of node-red!

29

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.