Ember s fail got EPERM: operation not permitted andist a image

I got this error and my app dont run :confused: the only way my app run is delete the dist folder

this is the log ember generates:

ENV Summary:

TIME: Thu Feb 08 2018 09:58:58 GMT-0500 (Hora est. Pacífico, Sudamérica) TITLE: ember ARGV:

  • C:\Program Files\nodejs\node.exe
  • C:\Users\luis.aragon.GRUPOSSI\AppData\Roaming\npm\node_modules\ember-cli\bin\ember
  • s EXEC_PATH: C:\Program Files\nodejs\node.exe TMPDIR: C:\Users\LUISAR~1.GRU\AppData\Local\Temp SHELL: null PATH:
  • C
  • \Program Files\Python36\Scripts;C
  • \Program Files\Python36;C
  • \ProgramData\Oracle\Java\javapath;C
  • \WINDOWS\system32;C
  • \WINDOWS\System32\Wbem;C
  • \WINDOWS\System32\WindowsPowerShell\v1.0;C
  • \Program Files (x86)\Windows Live\Shared;C
  • \php\ext;C
  • \Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit;C
  • \Program Files\nodejs;C
  • \Program Files\Git\cmd;C
  • \Program Files\MIT\Kerberos\bin;C
  • \Program Files (x86)\Yarn\bin;C
  • \Users\luis.aragon.GRUPOSSI\AppData\Roaming\npm;C
  • \Users\luis.aragon.GRUPOSSI\AppData\Local\Yarn\bin PLATFORM: win32 x64 FREEMEM: 1672990720 TOTALMEM: 6310412288 UPTIME: 527141.1274814 LOADAVG: 0,0,0 CPUS:
  • Intel® Core™ i3-3220 CPU @ 3.30GHz - 3294
  • Intel® Core™ i3-3220 CPU @ 3.30GHz - 3294
  • Intel® Core™ i3-3220 CPU @ 3.30GHz - 3294
  • Intel® Core™ i3-3220 CPU @ 3.30GHz - 3294 ENDIANNESS: LE VERSIONS:
  • ares: 1.13.0
  • cldr: 32.0
  • http_parser: 2.7.0
  • icu: 60.1
  • modules: 59
  • nghttp2: 1.25.0
  • node: 9.3.0
  • openssl: 1.0.2n
  • tz: 2017c
  • unicode: 10.0
  • uv: 1.18.0
  • v8: 6.2.414.46-node.15
  • zlib: 1.2.11

ERROR Summary:

  • broccoliBuilderErrorStack: [undefined]
  • codeFrame: [undefined]
  • errorMessage: EPERM: operation not permitted, open ‘F:\HigiaFront\dist\assets\img\bg_body.jpg’
  • errorType: [undefined]
  • location:
    • column: [undefined]
    • file: [undefined]
    • line: [undefined]
  • message: EPERM: operation not permitted, open ‘F:\HigiaFront\dist\assets\img\bg_body.jpg’
  • name: Error
  • nodeAnnotation: [undefined]
  • nodeName: [undefined]
  • originalErrorMessage: [undefined]
  • stack: Error: EPERM: operation not permitted, open 'F:\HigiaFront\dist\assets\img\bg_body.jpg’ at Object.fs.openSync (fs.js:663:18) at Object.fs.writeFileSync (fs.js:1314:33) at TreeSync. (F:\HigiaFront\node_modules\tree-sync\index.js:62:19) at Array.forEach () at TreeSync.sync (F:\HigiaFront\node_modules\tree-sync\index.js:50:14) at Builder.copyToOutputPath (F:\HigiaFront\node_modules\ember-cli\lib\models\builder.js:105:24) at Promise.resolve.then (F:\HigiaFront\node_modules\ember-cli\lib\models\builder.js:118:24) at tryCatcher (F:\HigiaFront\node_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:329:19) at invokeCallback (F:\HigiaFront\node_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:507:31) at F:\HigiaFront\node_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:571:14

I appreciate your collaboration

Do you run cmd as Administrator?

1 Like

yep i run all as administrator

Strange. We run many projets on windows. Where is bg_body.jpg coming from? Is it 0 bytes in the dist? Can you past a file with the same name by hand in the F:\HigiaFront\dist\assets\img\ folder? What if you try this on a git clone on C:\HigiaFront\ ?

Hi @broerse sorry for respond so late this account was on hold, :disappointed_relieved: yep we pass all img by hand, the folder with the problems are present in our .gitignore

No problem.

I don’t completely understand your answer. Is the image put by hand in: F:\HigiaFront\public\assets\img\bg_body.jpg or in F:\HigiaFront\dist\assets\img\bg_body.jpg ?

You must put it in F:\HigiaFront\public\assets\img\bg_body.jpg.

All the images are put by hand on F:\HigiaFront\public\assets\img but every time y stop ember serve and re estart again got this error and the only solution is delete the folder (F:\HigiaFront\dist\assets\img)

thanck you so much for your help

What happens when you do the same on the C:\HigiaFront\ clone ?

sorry but i don’t understand :confused:

It is just a test to see if you get the same errors.

ok, I’ll try that and I’ll tell you what’s happened :relaxed:

i clone mi repo on c:/ and i got the same issue :/, man i gave up i dont know what to do :disappointed_relieved::pensive:

Perhaps it is some npm version problem that creates this. What is your current npm version? Try this in your project:

delete package-lock.json
delete yarn.lock
npm cache clear --force
npm i -g npm
npm install --no-optional

Thank you again man :smile:

i try that, and i will talk you what happened. And sorry for my english is not my native language