Help us fix bugs faster « Syncdocs Google Drive Forum

Syncdocs Google Drive Forum » Troubleshooting

[sticky]

Help us fix bugs faster

(33 posts) (15 voices)

Started 8 years ago by Phil
Latest reply from Phil
5 Members Subscribed To Topic

Tags:

« Previous 12

Phil
Syncdocs

From your logs it looks like the automatic updater program we use, wyUpdate is complaining about its settings file, client.wyc. Perhaps this file is corrupt. If you wish, please email us the client.wyc file and we'll look into it.

Version 0.55 is pretty old, but we haven't changed the format. You should be able to update to the latest version from it, but we haven't tested it. You can always install the latest version over the old version. Just download syncdocs.msi from download page and install it.

Regarding the 400 and 503 errors reported by Google in your log, these often occur when one of the two users don't have the permission to access the files.

Posted 8 years ago #

Magical rainbow ponies
bizwizkid
Member

Hey Phil, attached is the client.wyc file.

...
Thanks!

Posted 8 years ago #
Phil
Syncdocs

Unfortunately the forums don't allow attachments, you can email them to us at contact-syncdocs@syncdocs.com

The missing file is not critical - it is a cache. Syncdocs will just re-make it if it is not there.

Posted 8 years ago #
Pn Tb
Member

Hello, syncing is broken.

Log:
Google HTTP Upload Server Built on Nov 8 2011 08:38:15 (1320770295)
09.11.2011 15:47:19(ver. 1.25) Res up first chance retry 0 on D:\xxx\xxx.txt ex=error: (400).
09.11.2011 15:47:21(ver. 1.25) Possible direct upload to server failed, Google server error. Attempting fix.
System.Net.WebException : sd criticality=0
Inner:
Source: System : sd criticality=0
09.11.2011 15:47:54(ver. 1.25) Log: sovl0
09.11.2011 15:47:54(ver. 1.25) Error log dump info done.

Tried to upload new file from local machine.

Posted 8 years ago #
Andrew
Syncdocs

Yes, Google uploads are broken. They are fixing it, see:
http://code.google.com/googleapps/support/downtime/?place=topic%2Fgoogle-apps-apis-downtime-notify%2FIGEHK4WrkKk%2Fdiscussion

Posted 8 years ago #
Andrew
Syncdocs

It is now fixed. Uploads will work again.
----------------
From Google:
"Hi,

The issue has been resolved, and uploads are now working again.

The problem was caused by a data permissions error. One of our internal data storage systems stopped allowing the Documents List API access to newly uploaded resources. We have corrected the permissions issue, thus fixing uploads.

We are putting some changes in place to ensure that this cannot happen again. Thanks so much for your patience during this outage.
"

Posted 8 years ago #
bizwizkid
Member

Hi there,

I'm getting this issue again and am hoping to find an easy solution. I updated to the newest version, the interface goes through the long 'Doing initial sync' process and I end up with an error message regarding the 'client.wyc' document.

I emailed you my error log and referred to this post.

If it helps any I can get rid of the second account as I simply put everything in a single directory that will be backed up. I do have about 40g of data and would really not want to start all over here.

Thanks again.

Posted 7 years ago #
Mike51
Member

That log file is helpful for pinpointing errors. Sometimes they flash by too fast!

Posted 3 years ago #
Benny_k
Member

Hi

Syncdocs cant seem to sync name changes correctly that I make to files/folders on my server.

For example, if I rename a few folders or files on my server, Syncdocs insists on downloading them again from Google Drive with the old names and then it uploads the ones with the new naming to Google Drive. It never deletes the old naming on Google Drive so I always end up with the old and the new versions of the files/folders on both my server and on Google Drive.
But if i make the changes at Google Drive it works as it should. I have checked the "full sync" box in the settings.

Please have a look at this issue because i drives me crazy.

Posted 3 years ago #
Phil
Syncdocs

The most likely cause of this is that Syncdocs does not have permission to see the local renames.

You can fix this by quitting Syncdocs and then right clicking on the Syncdocs icon and selecting "Run as Administrator". This should give it permission to see your folder changes.

Posted 3 years ago #
Benny_k
Member

Thank you. I will give that a try. But how will that work for the option "start at windows startup"? If this problem is solved by running as admin, will i need to manually start this program at every reboot? It sounds like this problem needs a fix for the next update?

Posted 3 years ago #
Benny_k
Member

Will this issue be addressed or do i need to find a better software?

Posted 3 years ago #
Phil
Syncdocs

Here's how to do it:
http://www.syncdocs.com/forums/topic/how-to-run-syncdocs-as-administrator-at-startup

Posted 3 years ago #

RSS feed for this topic

« Previous 12

Reply

You must log in to post.