-
Notifications
You must be signed in to change notification settings - Fork 128
Uncaught Error: EPERM: operation not permitted, lstat '/\cco-fil-02\userdata\' #289
Comments
Thanks for the report! Can you confirm a few things for us?
|
|
Hmm, if you adjust (if possible) the permission of the higher level directory, does that clear things up? And just to confirm, are you able to work with the files in |
Oh and also, I'm assuming this is a remote file on a network drive? |
Hi Robert,
Unfortunately I don't have the ability to adjust permissions on the higher
level directory, so can't confirm that. But yes, this is a network drive
and I am able to read/write files in my assigned subdirectory.
Thanks!
Phillip
…On Thu, Apr 20, 2017 at 9:58 PM Robert Sese ***@***.***> wrote:
Oh and also, I'm assuming this is a remote file on a network drive?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#289 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ASsNLLF4sHuH8EqNOeDA2ibgcCiEwPK2ks5ryDdkgaJpZM4M_Mm6>
.
|
Glad to hear the error isn't stopping you from working with the files in the directory you do have permissions on, thanks for confirming that 👍 |
@pcmccollum When you open Atom, what is your root project folder set to? |
Hi folks. The way this exception happened in my case was that my windows box had it's home directory and common directories mapped to the wrong server (not my C;\ drive but what Documents and other common directories were mapped to). Yesterday morning the server that my Documents et al were mapped to was unavailable and I was unable to access any of my files. One of the sys admins realized that my home directory and common directories were incorrectly mapped and they re-mapped it to the correct drive. This was after atom had accessed all these files where they had originally been, with the incorrect drive mappings. When my home and common directories were re-mapped to the correct drive this error started happening. It appears that atom was maybe holding on to the original mapping? I'm not sure, but hope that helps. Thanks for the awesome editor! |
[Enter steps to reproduce:]
Atom: 1.16.0 ia32
Electron: 1.3.13
OS: Microsoft Windows 7 Enterprise
Thrown From: fuzzy-finder package 1.5.0
Stack Trace
Uncaught Error: EPERM: operation not permitted, lstat '\cco-fil-02\userdata'
Commands
Non-Core Packages
The text was updated successfully, but these errors were encountered: