Copy link to clipboard
Copied
One of my editors is not able to sync fonts or library files with the rest of the team. The app is showing an uknown sync error and no folder location path. "Pause syncing" button is unresponsive and trying to select the folder location to User>Creative Cloud Files just leaves the app stuck in "moving folder".
In addition to the sync error, all of the mogrt files she was attempting to sync to the CC library have vanished from the my work section of the app. My guess is they never made it to the cloud, is there a local temp folder where those still might exist?
Adobe logs are uploaded.
@SuJoshi Thank you for the link. I did ommit in my orginal post that using the "learn more" resulted in no particular error but we did go through the process outlined in both of these links without any change. As an update, our onsite ACSP went through a number of troubleshooting steps with Adobe support yesterday. The only way they were able to get syncing back was to create a new user profile on the workstation. Technically this issue is solved, just not an ideal way.
Copy link to clipboard
Copied
<moved from cc services>
Copy link to clipboard
Copied
@kglad - Sorry I do not seem to be able to edit my previous post. Inserting the images here instead.
Copy link to clipboard
Copied
Hello,
I hope the below help document might help you in troubleshooting the issue:
> https://helpx.adobe.com/in/creative-cloud/kb/creative-cloud-desktop-app-spinning.html
> https://helpx.adobe.com/in/creative-cloud/kb/arent-my-files-syncing.html
You have to click on "Learn more" to get the actual error.
Copy link to clipboard
Copied
@SuJoshi Thank you for the link. I did ommit in my orginal post that using the "learn more" resulted in no particular error but we did go through the process outlined in both of these links without any change. As an update, our onsite ACSP went through a number of troubleshooting steps with Adobe support yesterday. The only way they were able to get syncing back was to create a new user profile on the workstation. Technically this issue is solved, just not an ideal way.