Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot Start Bot

See original GitHub issue

Describe the bug

Cannot start bot. It fails with the following message:

{"stack":"Error: spawn C:\\Windows\\system32\\cmd.exe ENOENT\n at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)\n at onErrorNT (internal/child_process.js:456:16)\n at processTicksAndRejections (internal/process/task_queues.js:80:21)","message":"spawn C:\\Windows\\system32\\cmd.exe ENOENT","errno":"ENOENT","code":"ENOENT","syscall":"spawn C:\\Windows\\system32\\cmd.exe","path":"C:\\Windows\\system32\\cmd.exe","spawnargs":["/d","/s","/c","\"dotnet user-secrets init --project azurewebapp\""],"cmd":"dotnet user-secrets init --project azurewebapp","stdout":"","stderr":""}

Version

Browser

Electron distribution
Chrome
Safari
Firefox
Edge

OS

macOS
Windows
Ubuntu

To Reproduce

Steps to reproduce the behavior:

1.Click on Start Bot Button 2. Wait for it to fail

Expected behavior

The bot starts

Screenshots

Issue Analytics

State:
Created 3 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

Rekeyeacommented, Mar 7, 2021

I used the “Get a new copy of the runtime code” functionality. Had to rerun the schemas, but it apparently is working again. What I saw is that before the update, my Runtime code location was runtime but when I got the new copy it was automatically set for …/runtime. So I guess that was the issue.

I think this can be closed. Thanks for all your help.

0reactions

Rekeyeacommented, Mar 7, 2021

Adding more details, it happens when using a custom runtime. When going back to the default runtime this does not happen.