wmic is not recognized as an internal or external command, operable program or batch file
:: Start :: Technology :: Computer & Internet
Page 1 of 1
wmic is not recognized as an internal or external command, operable program or batch file
https://knowledge.informatica.com/s/article/156865?language=en_US
ERROR: "wmic is not recognized as an internal or external command, operable program or batch file." when Nodeagent startup fails in Windows client machine
Description
While starting nodeagent from Windows OS, the startup fails with the following error message:
wmic is not recognized as an internal or external command, operable program or batch file.
wmic is the program, which will enable access to Windows Management Instrumentation console and nodeagent will require access to that program for getting CPU and Memory usage in the machine. Current issue will occur when wmic program is not present in the system PATH environment variable.
Solution
To resolve this issue, do the following:
Open Command Prompt in the machine, where nodeagent has to be started.
Run the following command for adding folder containing wmic to PATH environment variable:
SET PATH=C:\Windows\System32\wbem\;%PATH%;
After setting the path variable using the command above, run the following command to confirm whether wmic is picked properly:
where wmic
The command above should return the following as output:
"C:\Windows\System32\wbem\WMIC.exe"
After confirming, navigate to the nodeagent folder, without closing the Command Prompt session.
Start the Nodeagent by using nodeagent.bat start command.
ERROR: "wmic is not recognized as an internal or external command, operable program or batch file." when Nodeagent startup fails in Windows client machine
Description
While starting nodeagent from Windows OS, the startup fails with the following error message:
wmic is not recognized as an internal or external command, operable program or batch file.
wmic is the program, which will enable access to Windows Management Instrumentation console and nodeagent will require access to that program for getting CPU and Memory usage in the machine. Current issue will occur when wmic program is not present in the system PATH environment variable.
Solution
To resolve this issue, do the following:
Open Command Prompt in the machine, where nodeagent has to be started.
Run the following command for adding folder containing wmic to PATH environment variable:
SET PATH=C:\Windows\System32\wbem\;%PATH%;
After setting the path variable using the command above, run the following command to confirm whether wmic is picked properly:
where wmic
The command above should return the following as output:
"C:\Windows\System32\wbem\WMIC.exe"
After confirming, navigate to the nodeagent folder, without closing the Command Prompt session.
Start the Nodeagent by using nodeagent.bat start command.
sunt- Number of posts : 145
Registration date : 2008-11-14
Similar topics
» command prompt tricks
» How to Delete a file you can not delete
» How to install a .run file in Linux
» Program a 2004 Toyota Sequioa key
» Status file could not be parsed/ mergelist issues
» How to Delete a file you can not delete
» How to install a .run file in Linux
» Program a 2004 Toyota Sequioa key
» Status file could not be parsed/ mergelist issues
:: Start :: Technology :: Computer & Internet
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum