CFileException 0 in C:\Users....WTH??
-
I get this error when saving..the only thing that cures it is to save the skp file under a new name..that works for a while then eventually the save error returns on that new file as well..
So I can't save a file anymore without getting this damn error and it's driving me to drink...anyone know how to solve this?..I've searched this forum and Google and nothing...I've seen CFileException 3 errors discussed but not this variation of it...
-
the frequency of this error is increasing and it's killing me.
-
The only time I see this error message is when saving after sending a file to Kerkythea for rendering. The SketchUp team knows about it and are working on a fix. I just save the SKP file prior to exporting to Kerkythea. When I save after that, I get the error message and another copy of the SKP file.
-
also if you are working on a network or USB drive this can happen.
-
no network or usb involved.......just dropbox sync between 3 pc's / laptops
-
Um., isn't dropbox sync via the network? The latency in that operation may be what is triggering the error message.
-
explain ''latency'' please
-
@pipingguy said:
explain ''latency'' please
lame.. jamming.. limping... i.e. doesn't respond fast enough to the SU file saving routine, to fix save local and drop it to the cloud folder then.
-
but i thought the files get refreshed instantaneously in the c drive, and then the syncing takes place between this and other machines and the cloud as an automatic secondary operation, behind the scenes? anyway, i dumped old versions of skp and am using only 2017. i think that cures the problem. i just do not get a thrill from the trays.
-
If Auto-Backup is set then Dropbox probably isn't playing nice with the .skb file related to the .skp
-
good point
-
I HAVE HAD THIS ERROR FOR A LONG TIME AND ITS DRIVING ME CRAZY: I end up having to save the file manually and keep changing the name. Autosave does it and "Save" does it. I am not on a network, running as admin, saving to "documents/xxx.
It started when I upgraded to Make 2017.
Advertisement