Can someone tell me what the fix is to eliminate the CFile Exception 0 error message every time you save? I read somewhere it was because of Drop Box - I uninstalled it completely - also reran Run As administrator (but pretty sure that I did this when I loaded SU Pro 2018) - neither worked for me. Thank you in advance. Barb
Where are you saving your SketchUp files? The most frequent cure for this error is to save directly on your local hard disk, not to a network drive, USB stick, or cloud-shared destination such as DropBox.
Am saving to C drive in folder - even tried now saving to a documents folder and same thing. I deleted dropBox thinking that was causing the issue but didn’t resolve.
This seems like a known windows issue. I was able to apparently fix it for one user this morning by moving the Save File location to the D: drive… It didn’t have the same permissions lock that the C:/Users/Documents folder did. There was a lengthy discussion on this topic with a variety of outcomes here on this forum: https://www.cnet.com/forums/discussions/windows-10-read-only-problem-has-a-solution/
CFileException 2 when trying to save in sketchup
Problem with Saving File- It Shows Message: " CfileException 0 in C:\folder\file.skp " and does not save file
@TheGuz this error message has confused and frustrated me for a long time. Looking at the MS documentation, CFileException 0 is supposed to mean no error occurred. So how is it that SketchUp is detecting a failure when the exception code says there was no error? It seems to me that since SketchUp is obviously trapping some sort of issue, it ought to be possible to provide a more meaningful error message?
It’s true that CFileException 0 is supposed to mean “No error occurred”. It seems like a CFileException 5 or 12 would be more appropriate since we were seeing that SketchUp would not save the current file over the existing file called Test.skp. It instead created a new file called Test-0.skp and that saved without being corrupted. None of this occurred after we changed the path.
You may have missed my point.
SketchUp knows what operation it was trying to accomplish when it detected an issue. It ought to report something like “failed while attempting to create backup file”, or “creating alternate file Test-0.skp because original file is locked”, not just an overly technical CFileException value that is meaningless to most users. Code 5 or 12 might be more technically correct in a specific case, but is still unfriendly to non-nerd users. And code 0 is useless to everyone, including the SketchUp development team!
i.e. verbose error messages *
… shouldn’t be a big thing.
I have had the same errors in other applications, for instance Autocad. One cause has been that the Preview pane has been open in Windows Explorer. And yes, it happens more often with network drives.
If the actual error code is 5 or 12 I’m all for exposing it in the error dialog. Even if it doesn’t mean anything in itself it can be looked up on internet what those codes mean. However, phrasing a message in English is even better. Or why not both have an English phrase and show the underlying error code within parenthesis.