spawn C:\Windows\system32\cmd.exe ENOENT error with childProcess.exec() on Debugger #28271

Comments

atif089 commented Jun 9, 2017 •

Steps to Reproduce:

1. Create a new file and run a command using childProcess.exec()
2. The script runs fine when I run the script through integrated terminal ( node myfile.js )
3. The script fails with an error Error: spawn C:\Windows\system32\cmd.exe ENOENT when running through the debugger.

The text was updated successfully, but these errors were encountered:

weinand commented Jun 14, 2017 •

@atif089 I cannot reproduce this (because I do not know the value of ‘execPath’).

Please provide a small code snippet that I can use to reproduce the problem (and please real code and not a screenshot since I do not want to enter it by typing).

atif089 commented Jun 14, 2017

Thanks for the follow-up @weinand. Here’s all the code from the actual screenshot.

This file works fine when I run it in the terminal (both cmd and the integrated one in VS Code) but then when I run it by pressing F5 I see the error mentioned. I tried running VS Code as Administrator assuming that might make difference but there was no change.

And this file was working fine in at least until version 1.10

atif089 commented Jun 15, 2017

I figured this has nothing to do with VS code. The exec command fails because the resolved cwd path was invalid and it didn’t exist.

When I was running it through the terminal, I was always in the appropriate directory and that is why the command was working fine.

weinand commented Jun 15, 2017

@atif089 thanks for investigating (and resolving) the issue.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

spawn cmd.exe ENOENT #76

Comments

harudagondi commented Jun 30, 2016

Having issues with sass-autocompile.

Added C:\Windows\System32 in %PATH%
Installed node-sass with -g
Path to ‘node-sass’ command:
«

node-sass —version >nul 2>&1 && (echo found) || (echo fail)
Output: found

#63
Replace compiler.coffee
Output:

The text was updated successfully, but these errors were encountered:

armin-pfaeffle commented Jun 30, 2016

Well, it seems your Atom cannot execute cmd.exe .

Which version of Atom do you use?
You use Windows, right? Which one?
Have you cleared Path to node-sass command completely? There are no characters at all, even no spaces?

harudagondi commented Jul 2, 2016

Which version of Atom do you use?

You use Windows, right? Which one?

Have you cleared Path to node-sass command completely? There are no characters at all, even no spaces?

Yup. No characters at all.

armin-pfaeffle commented Jul 4, 2016

Can you execute process.env.Path in Atom console and post the result? I’m pretty sure that C:\Windows\system32\ is missing in the path list.

What other plugins do you use? Perhaps python-tools?

Some other plugins modifies the internal variable process.env.Path so that my package cannot access executables from system32-folder.

armin-pfaeffle commented Aug 15, 2016 •

Any updates? Else I will close that issue.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Problem with npm start (error : spawn cmd ENOENT)

I have a problem with my application. Because before when I created an application it worked, but now, it shows me this error and I do not know why and the things I have to do to fix it.

Do you have any idea to help me ? (This is a reactJS app).

I checked some stackoverflow topics but everywhere I checked, it was not really an answer that worked.

5 Answers 5

Add C:\Windows\System32 to the global PATH environment variable.

Solution 1

Set your environment variable to C:\Windows\System32 . This works for me.

Solution 2

If the first one doesn’t work follow the 2nd steps. Navigate to your project folder and type this command >>>

Solution 3

Downgrade react-scripts in package.json file

I had the same problem after I tried to install Mongo DB. I found out that this problem only exists with react-scripts@3.0.0. Try to reinstall your npm with a different react script version. Simply go to your folder in command and reinstall like this:

After that the app worked for me again.

If someone hits this coming from Angular 2+, remove the —open from ng serve or run without this option.

For all those Who’ve come to this problem from react scripts not starting. The solution is

1. Go to search bar and write environment variables. You should see an option to called edit system environment variables or something similar.
2. Under the Advanced section there is a enivronment variable button. click it.
3. After that you will see an option named path click on it.
4. click add button and add following directory C:\Windows\System32 .
5. close down your editor and restart your command terminal. Problem should be resolved now 😁

Not the answer you’re looking for? Browse other questions tagged node.js reactjs git-bash or ask your own question.

Linked

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.4.16.39093

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

ReactNative — Error: spawn cmd.exe ENOENT

On executing react-native run-android, got an error message «Error: spawn cmd.exe ENOENT»

Environment:
react: 16.0.0-alpha.6,
react-native: 0.43.1
OS: Windows 10
node.js: 6.9.2
yarn: 0.22.0

Kindly assist to solve the issue.

3 Answers 3

check system environment variables and add C:\windows\system32 in system variables Paths !

packager port (8088) and tcp port (8081) are not same. Issue solved when both the ports are same.

Run command ‘adb reverse tcp:8081 tcp:8081’ in your android sdk platform tools folder.

I think you don’t have yarn installed try installing it with chocolatey or something. It should be installed before creating your project (react-native init command).

Edit: In the recent version of react-native they have fixed it. If you want complete freedom from this just uninstall node (For complete uninstallation Completely remove node refer this link) and reinstall node, react-native-cli then create your new project.

Not the answer you’re looking for? Browse other questions tagged react-native or ask your own question.

Linked

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.4.16.39093

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Ошибка NodeJs: spawn C:\Windows\system32\cmd.exe; ENOENT

Это мой сценарий :

А в консоли у меня есть :

Кто-нибудь может мне помочь ?

2 ответа

Я нахожусь на Windows и пытаюсь следовать инструкциям на http://yeoman.io/learning/index.html . До сих пор я успешно установил grunt-cli и bower, но когда я пытаюсь установить yo, используя следующую команду. npm install -g yo . командная строка возвращает это значение: > spawn-sync@1.0.11.

Когда я получаю следующую ошибку: events.js:72 throw er; // Unhandled ‘error’ event ^ Error: spawn ENOENT at errnoException (child_process.js:1000:11) at Process.ChildProcess._handle.onexit (child_process.js:791:34) Какую процедуру я могу выполнить, чтобы исправить это? Примечание автора .

Я должен решить эту проблему, проблема заключается в том, чтобы удалить точку с запятой(;) из конца строки. ComSpec путь C:\Windows\System32\cmd.exe

Компьютер>Свойства>Дополнительные параметры системы>Переменные среды>системные переменные

добавьте этот путь: ComSpec C:\Windows\System32\cmd.exe

Это также может быть вызвано тем, что вы вводите в ExecOptions параметр options, а именно ‘cwd’, и указанный вами путь является недопустимым

Если это неверно, то обратный вызов будет вызван с ошибкой, равной

Ошибка: spawn C:\Windows\system32\cmd.exe ENOENT

Похожие вопросы:

Я получаю ошибку, используя GM() на моем удаленном сервере, я думаю, что получаю проблему, когда пытаюсь написать файл. Он отлично работает на моем локальном сервере. Мой код : gm() .in(‘-page’.

Я использую модуль GM node на экземпляре AWS EC2 с Linux OS. Моя цель-обрезать изображение, предоставленное url из ведра S3. Я делаю запрос http к изображению url из корзины S3, чтобы получить буфер.

Я получаю следующую ошибку при установке парусов > sails@0.11.0 preinstall E:\jb\npmtest\node_modules\sails > node ./lib/preinstall_npmcheck.js npm ERR! Windows_NT 6.1.7601 npm ERR! argv.

Я нахожусь на Windows и пытаюсь следовать инструкциям на http://yeoman.io/learning/index.html . До сих пор я успешно установил grunt-cli и bower, но когда я пытаюсь установить yo, используя.

Когда я получаю следующую ошибку: events.js:72 throw er; // Unhandled ‘error’ event ^ Error: spawn ENOENT at errnoException (child_process.js:1000:11) at Process.ChildProcess._handle.onexit.

Случайно столкнулся со следующей ошибкой при установке node-sass с использованием npm на Windows 7 12689 verbose stack Error: windows-build-tools@0.5.0 postinstall: `node ./lib/index.js` 12689.

При выполнении react-native run-android появилось сообщение об ошибке Error: spawn cmd.exe ENOENT Окружающая среда: реагировать: 16.0.0-alpha.6, react-native: 0.43.1 OS: Windows 10 node.js: 6.9.2.

Я пытаюсь создать react-приложение, но у меня есть проблема ENOENT, это то, что показывает командная строка: Installing packages. This might take a couple of minutes. Installing react, react-dom.

Я сделал проект react native, используя react-native init HelloWorld . Когда я запускаю этот проект с помощью react-native run-android , я получаю эту ошибку. events.js:183 throw er; // Unhandled.

Я смог установить nodejs версии v10.7.0 и npm версии 6.1.0 без каких-либо проблем. Также установлены angular 1.7.2 и typescript 2.9.2.I я получаю эту ошибку ниже при попытке установить npm install-g.