It seems that over the past 24 hours, the Files.Patch problem has returned to how it worked on August 22. We also encountered this problem when we tried to install the LastModified Timestamp file - see Extracting the log file below:
20130826 13:30:45 - GoogleApiRequestException: retry number 0 for file patch of File/Folder Id 0B9NKEGPbg7KfdXc1cVRBaUxqaVk 20130826 13:31:05 - ***** GoogleApiRequestException: Inner exception: 'System.Net.WebException: The remote server returned an error: (500) Internal Server Error. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at Google.Apis.Requests.Request.InternalEndExecuteRequest(IAsyncResult asyncResult) in c:\code.google.com\google-api-dotnet-client\default_release\Tools\BuildRelease\bin\Debug\output\default\Src\GoogleApis\Apis\Requests\Request.cs:line 311', Exception: 'Google.Apis.Requests.RequestError Precondition Failed [500] Errors [ Message[Precondition Failed] Location[If-Match - header] Reason[conditionNotMet] Domain[global] ] ' 20130826 13:31:07 - ***** Patch file request failed after 0 tries for File/Folder 0B9NKEGPbg7KfdXc1cVRBaUxqaVk
Today, the execution of the same process is performed every time it corrects the timestamp of files, as before August 22.
As a result of this 4/5 day crash, we now have hundreds (possibly thousands) of files with incorrect timestamps.
I know that the API is a beta version, but please, please Google Developers “inform us in advance about any“ trial fixes ”and at least post on this forum to confirm the problem, to save time trying find an error in our custom programs.
source share