A small number of files I have sent to CC syncing service fail to sync. I have checked all the troubleshooting tips (no special characters in file name, etc.) and none of them apply. The files are .ai files and are big but not super huge: ~ 380 MB ea.
The file names of the ones that won't sync are 006.ai, 007.ai, and 009.ai. However, other files in the series (made the same way, at the same time, and are about the same size) called 001.ai, 002, 003, 004, etc. all sync fine.
I have tried renaming the failing files before resaving (e.g. 009x.ai ) and they still fail. I have tried opening the original file on my desktop and doing 'save a copy' directly to CC. Still fails.
The consistent error message is "Some files failed to sync". The tantalizing "learn more" link just leads to the disappointingly uninformative message,"unable to sync 007.ai".
I have been trying for days - at first thinking maybe a spotty internet connection was the problem. But it fails whether syncing from home or work, or any day of the week.
I have also noted a message on the Adobe troubleshooting page that for large files, the actual sync doesn't happen until the whole file is copied, and until then the file is flagged as a 'fail'. Well, I've waited hours, and the flag never goes away. (And BTW, if it's true that a still-syncing file might be flagged as a fail and giving a message in past tense ("some files failED to sync") is dumb UX design and should be fixed.)
Running Mac OSX 10.8.5
Am getting really frustrated here. Whatver value CC syncing offers my life and workflow has been erased by the time I have wasted troubleshooting this problem.
Did you figure this out? I'm having the same issues and the "Learn More" isn't at all helpful - only says that, "Creative Cloud is operating normally"...very frustrating!
Could you send us some log files so that we can investigate this issue?
Please zip up the entire 'CoreSync' folder at the location below and send to me at email@example.com.
'Library' on Mac and 'AppData' on Windows are both hidden folders. Please read this page for help on showing these folders:
Hi Ben, I did what you suggested to juliax99 (turned on hidden folders) but still cannot find the path for the log files. I'm on a PC at work (Windows XP) and Windows 8 at home and syncing is an issue on both computers.
I did a search for the path and nothing turned up for what you show but I did find two folders in the Adobe\Adobe Creative Cloud\CoreSync\sibres path named CloudSync & CloudSyncExt. I know this thread is for juliax99 but can I send you the log files from CloudSync on my work computer and you see if you can figure out what the problem is? Let me know, thanks!
Very sorry to anyone reading this; I made a typo in my post above. The correct paths are:
I am facing the same error - I think!
It says "Synch von * aufgrund eines Serverfehlers nicht möglich"
"syny not possible due to server error"
Could you also follow the steps above (post 4) to package up and send me your log files?
Thanks for the logs. The files that are not syncing properly are Lightroom catalog files. The Lightroom/Creative Cloud FAQ does not recommend syncing Lightroom data files to Creative Cloud:
So we're expected to go through ALL our files and take out our catalog files - this makes no sense. I have far too many folders to go through not to mention Lightroom is an Adobe product and should work with Adobe Cloud Storage - it's storing the file so I'm having a hard time understanding the issue. Every designer/photographer I know stores the CAT files in a folder withing the folder/original images and now I'm to understand that due to some internal conflict I cannot sync my files...? Please clarify if possible.
I have the same problem:
It says "Synch. von <Dateiname> aufgrund eines Serverfehlers nicht möglich"
"sync of <filename> not possible due to server error"
But I did not store a Lightroom catalog file (what is this?). Just a JPG. This JPG was stored from another user and it was in my creative cloud files but the system said that it could not snyc this file. Now the file is deleted from another user but the error-message above still occurs!