Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google.Apis.Requests.RequestError Not Found 404 #318

Closed
sclewis23 opened this issue Aug 31, 2017 · 6 comments
Closed

Google.Apis.Requests.RequestError Not Found 404 #318

sclewis23 opened this issue Aug 31, 2017 · 6 comments

Comments

@sclewis23
Copy link

sclewis23 commented Aug 31, 2017

I'm not sure if it is my firewall but i just started getting:

Google.Apis.Requests.RequestError
Not Found [404]
Errors [
	Message[Not Found] Location[ - ] Reason[notFound] Domain[global]
]

Then I get API rate limit reached. Backing off 2sec before retry.
This was the first sync of the day.....Haven't tried in a couple days so I would have thought i'm not near my api limit.

@phw198
Copy link
Owner

phw198 commented Aug 31, 2017

🗒️ I'd need your logfile to see in more detail what's happening [see instructions]...but the API rate limit means that too many changes are happening in too short a period of time. OGCS should automatically back off and retry, so if that isn't happening, sounds like a bug...

@sclewis23
Copy link
Author

sclewis23 commented Sep 2, 2017 via email

@phw198
Copy link
Owner

phw198 commented Sep 3, 2017

Thanks @sclewis23

So looks like we've got multiple things going on here! Some questions:

  1. Are you a long time user of OGCS? Did these problems start with v2.6.1?
  2. Did you at some point have two-way sync going, or synced from Google to Outlook?
  3. Have you always synced Descriptions
  4. Have you always used the proxy currently configured?

I think the HTTP404 errors when retrieving Google event sio6eh8n8gfaui6gmj0c0st95o can be ignored - this likely comes from a 2-way sync, but has since been deleted in Google after reverting to O->G. It will likely fix itself once we can fix the next issue.

More concerning, is

WARNING: Event creation failed.
Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
     at Microsoft.Office.Interop.Outlook._AppointmentItem.get_Body()

It seems you no longer have rights to see the Outlook appointment body/description. This policy might have been changed by your IT. Could you try unchecking the Description option in OGCS, at least temporarily to stop this error?

Last, it seems communication to update Google events is then failing:

Doing a dummy update in order to update the last modified date of single instance
WARNING: Updated event failed to save.
Error while copying content to a stream.

These feels like a proxy/firewall issue maybe - have you always used the current one configured? Are you able to try OGCS with a direct internet connection?

@sclewis23
Copy link
Author

I have been using it for a while, but our firewall/proxy was recently updated.
I went ahead and removed my google calendar and let it sync again with description off.
I did create all entries, but it seems to have to created 4 calendar entries for each.
I also get a pop window indicating a popup error saving, I just click OK to continue.

@sclewis23
Copy link
Author

sclewis23 commented Sep 4, 2017 via email

@phw198
Copy link
Owner

phw198 commented Sep 4, 2017

Unfortunately for you, it seems your firewall is wreaking havoc - when OGCS tries to talk to Google to create the events, you're getting back from ForcePoint Access to this site is blocked.

Your log file's full of this error...I'm kinda surprised it managed to create any events at all in Google, let alone 4 duplicates. But if the firewall is randomly blocking certain activities (the delete worked and the retrieval of events works...mostly), then I think you're dead in the water. 💀

I'm guessing ForcePoint is also blocking your ability to retrieve the description of the Outlook items too. Seems either like a horrific product, or not properly configured.

@phw198 phw198 closed this as completed Nov 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants