Fenton
September 23, 2021, 5:20am
1
When I type n8n it returns with:
» Error: There was an error: EPERM: operation not permitted, scandir ‘C:\Users\Administrator\Application Data’
I am running the npm version. (node version: 14.7.6, npm version: 6.14.15)
jan
September 23, 2021, 5:52am
2
Welcome to the community @Fenton !
That issue is not related to n8n. So can sadly not really help you hehe. Is best to Google the error message and then check out the differents posts like this:
opened 07:04PM - 12 Jul 17 UTC
closed 05:31AM - 27 Oct 17 UTC
windows
support
bot-closed
#### I'm opening this issue because:
- [x] npm is crashing.
- [x] npm is… producing an incorrect install.
- [ ] npm is doing something I don't understand.
- [ ] Other (_see below for feature requests_):
#### What's going wrong?
```
D:\MyDev\ljs_app\trunk\periscope\build>npm i
npm ERR! path D:\MyDev\ljs_app\trunk\periscope\build\node_modules\fsevents\node_modules
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall scandir
npm ERR! Error: EPERM: operation not permitted, scandir 'D:\MyDev\ljs_app\trunk\periscope\build\node_modules\fsevents\node_modules'
npm ERR! { Error: EPERM: operation not permitted, scandir 'D:\MyDev\ljs_app\trunk\periscope\build\node_modules\fsevents\node_modules'
npm ERR! stack: 'Error: EPERM: operation not permitted, scandir \'D:\\MyDev\\ljs_app\\trunk\\periscope\\build\\node_modules\\fsevents\\node_modules\'',
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'scandir',
npm ERR! path: 'D:\\MyDev\\ljs_app\\trunk\\periscope\\build\\node_modules\\fsevents\\node_modules' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\doberkofler.LBITS\AppData\Roaming\npm-cache\_logs\2017-07-12T18_53_54_304Z-debug.log
```
#### How can the CLI team reproduce the problem?
https://gist.github.com/doberkofler/f24eea4a2d57cefde864ed64556b7bc1.js
### supporting information:
- `npm -v` prints: 5.2.0
- `node -v` prints: 8.1.4
- `npm config get registry` prints: http://registry.npmjs.org/
- Windows, OS X/macOS, or Linux?: Windows
- Network issues:
- Geographic location where npm was run:
- [ ] I use a proxy to connect to the npm registry.
- [ ] I use a proxy to connect to the web.
- [ ] I use a proxy when downloading Git repos.
- [ ] I access the npm registry via a VPN
- [ ] I don't use a proxy, but have limited or unreliable internet access.
- Container:
- [ ] I develop using Vagrant on Windows.
- [ ] I develop using Vagrant on OS X or Linux.
- [ ] I develop / deploy using Docker.
- [ ] I deploy to a PaaS (Triton, Heroku).
Hey @Fenton , welcome to the n8n community!
Was showing a friend n8n and ran into the same thing.~/.n8n) and then do n8n start!
Fenton
September 25, 2021, 9:56pm
4
Thanks so much. It’s always the cd lol