Skip to main content

Hello,

When running a system command like ipconfig there is no problem. But when trying to execute a custom command (CLI) the system throws error -150, as if this command was not recognized.

The command is question is registered in the path variable of the system so that when called from a normal command console it responds without problems.

The question arises whether this is due to UNIFACE permission, since if the command line is called from UNIFACE through an intermediary, it responds that the command does not exist, as if it were inheriting permission from the UNIFACE executable.

Could the Uniface need to be configured to accept custom commands? or when executing a program generates a system user to whom we must fix the permission appropriately?

Thanks.

Hello,

When running a system command like ipconfig there is no problem. But when trying to execute a custom command (CLI) the system throws error -150, as if this command was not recognized.

The command is question is registered in the path variable of the system so that when called from a normal command console it responds without problems.

The question arises whether this is due to UNIFACE permission, since if the command line is called from UNIFACE through an intermediary, it responds that the command does not exist, as if it were inheriting permission from the UNIFACE executable.

Could the Uniface need to be configured to accept custom commands? or when executing a program generates a system user to whom we must fix the permission appropriately?

Thanks.

Hi Alejandro,

Have you tried calling the following from Uniface:

    cmd/c  your_custom_command

instead of:

    your_custom_command

Regards,

Jason.

Hello,

When running a system command like ipconfig there is no problem. But when trying to execute a custom command (CLI) the system throws error -150, as if this command was not recognized.

The command is question is registered in the path variable of the system so that when called from a normal command console it responds without problems.

The question arises whether this is due to UNIFACE permission, since if the command line is called from UNIFACE through an intermediary, it responds that the command does not exist, as if it were inheriting permission from the UNIFACE executable.

Could the Uniface need to be configured to accept custom commands? or when executing a program generates a system user to whom we must fix the permission appropriately?

Thanks.

Hi Jason,

Now instead of the error -150 it returns this "'sdcli' is not recognized as an internal or external command,
operable program or batch file".

Here is a test from the cmd where I get the proper response from the command:

Hello,

When running a system command like ipconfig there is no problem. But when trying to execute a custom command (CLI) the system throws error -150, as if this command was not recognized.

The command is question is registered in the path variable of the system so that when called from a normal command console it responds without problems.

The question arises whether this is due to UNIFACE permission, since if the command line is called from UNIFACE through an intermediary, it responds that the command does not exist, as if it were inheriting permission from the UNIFACE executable.

Could the Uniface need to be configured to accept custom commands? or when executing a program generates a system user to whom we must fix the permission appropriately?

Thanks.

Are you using "spawn" or an OSCALL signature with the operations  COMMAND & COMMANDOUT?

Are you using "spawn" or an OSCALL signature with the operations  COMMAND & COMMANDOUT?

An OSCALL signature because I need to be able to catch the response 

Are you using "spawn" or an OSCALL signature with the operations  COMMAND & COMMANDOUT?

Hi Alejandro,

my guess is the default directory of cmd .exe and the default directory of your Uniface app are different and your sdcli.bat or sdcli.cmd CLI file is located in the cmd default directory.

Try to (temporary) address sdcli CLI with its full path name and extensions to confirm my guess.

Gianni

Are you using "spawn" or an OSCALL signature with the operations  COMMAND & COMMANDOUT?

Hi Gianni,

I get this error when I tried the full path with the sdcli.cmd: 

"'"node"' is not recognized as an internal or external command, operable program or batch file. "

Are you using "spawn" or an OSCALL signature with the operations  COMMAND & COMMANDOUT?

Hi Alejandro,

It is executed! That's a good point...it is NOT a Uniface problem.

Probably your sdcli CLI file is correct but not robust enough to be executed when positioned in a directory different from the one where it was developed; you should improve it to have it more robust and indipendent.

Gianni

Hello,

When running a system command like ipconfig there is no problem. But when trying to execute a custom command (CLI) the system throws error -150, as if this command was not recognized.

The command is question is registered in the path variable of the system so that when called from a normal command console it responds without problems.

The question arises whether this is due to UNIFACE permission, since if the command line is called from UNIFACE through an intermediary, it responds that the command does not exist, as if it were inheriting permission from the UNIFACE executable.

Could the Uniface need to be configured to accept custom commands? or when executing a program generates a system user to whom we must fix the permission appropriately?

Thanks.

Hello everyone,

I did some more testing and what I can conclude is that Uniface doesn't recognize the npm console, I wonder if there is a way to integrate it?

Thanks.

Are you using "spawn" or an OSCALL signature with the operations  COMMAND & COMMANDOUT?

Hi Gianni,

What I detected from testing is that the npm console is activated but is failing when is done from Uniface, maybe what I need is a way to integrate the node.js (CLI) and the npm console with Uniface???

Terms & ConditionsAccessibility statement