We have a script updating Domain Shared Contacts for our tenant that runs every morning. Today, the insert requests started failing. Google is returning error code 500, which according to documentation is an 'unrecognized error'.
I'm not finding anything regarding an API outage currently going on, nor am I seeing anything relating to an API change taking effect today.
I recreated the request with curl hoping to get more info, but still just receive "500 Internal Server Error".
Anyone else seeing this? Anyone aware of an internal problem at Google, or an API change which just took effect?
Thanks for any help.
EDIT:
The issue seems to be resolved. Hopefully it has for others with this problem as well. Thanks to Google for addressing this.
Yes unfortunately this problem started yesterday see
Exception while adding contact in google.Internal server Error
I urge you to raise a Case with Google Support
Related
I'm getting this error in the Query monitor. Because of this error, the WordPress admin panel speed has been reduced. Please tell me how to fix this?
I'm using the Google Cloud and Litespeed server. The API is working correctly but maybe it's a hosting problem.
Just tried to check several settings with woo-commerce and Query monitor, this issue is possible due to the network latency. If your server is in the Asia region, the curl timeout happens easily. If we launch the server in the US region, no timeout issue.
Since 1000 milliseconds = 1 second is quite short, you might want to try the following method that I found from the Google search to avoid such issue, hope this helps.
https://kb.mailpoet.com/article/311-curl-issue-28-timeout
https://gist.github.com/sudar/4945588
I am using LinkedIn API to share my contents on the company page. Since last 3-4 days, I am getting an error.
"LinkedIn::Errors::InformLinkedInError: LinkedIn had an internal
error. Please let them know in the forum. (500): Internal Server
Error"
I have not done any code change that shall break my application.
How do I report this error to LinkedIn? What details are required to be shared?
If I were you I'd prepare the shortest code that triggers the problem: just the bare minimum that is needed to replicate it. Send it to them just as if it was a MCVE here on StackOverflow.
Imagine you are the LinkedIn developer solving this problem: how would you like to receive this error report? Ideally if it was some short piece of code that you could run locally and observe what exactly is being sent to the API. (Of course the code has to actually trigger the problem!)
I'm using Nginx and the extension tx_news. When I'm working in backend with news(cut,edit,close,...) I get sometimes a 502-Bad Gateway exception. This exception I get after a second. I don't understand what's going wrong here. Sometimes it works well and sometimes I get this exception more often. I only get this exception in combination with tx_news. The rest of backend is working fine. Maybe this is only a configuration problem of nginx connections or something like this. Is anybody here who has an idea?
Every hint can help me :-)!
Check the consistency of your database records on such a page.
I used to get 502 bad gateway errors on Nginx after copying a page with fluidcontent elements because somhow a FCE got itself as its parent, which caused an infinite loop upon rendering the page module. But all I saw was the bad gateway page. This only happened with a specific version of fluidcontent.
Maybe you have some relations in your news records that are circular after pasting? Worth checking for it.
I already put this into the old forum so I hope this will be fine.
Suddenly in one location users to the CMS side now are getting errors. If they work elsewhere there is no problems. I know the forum usage is low but if I shall slap the network people silly I need to have some pointers.
User gets several errors during the loading homepage process.
Err 1: A few times: JavaScript alert -
[synchronizer] unable to get client-side resource with ID xxxx
Err 2: Sometimes:
Unspecified error. on /library/javascript/mdvc.js
Err 3: several times:
A GUI system error occured. Details:[CmdsHTTPDone]
<tcmapi:Response xmlns:tcmapi="http://www.tridion.com/ContentManager/5.0/TCMAPI" success="false" actionWF="false" ID="WebGUIResponder.aspx"><tcmapi:Error><tcm:Line Cause="true" mlns:tcm="http://www.tridion.com/ContentManager/5.0"><![CDATA[Request message cannot be empty. ]]></tcm:Line></tcmapi:Error></tcmapi:Response>
Err 4: Sometimes we also get "permission denied" errors on TaskBarControl.js or other scripts.
In the end.. all views empty.
When trying to use a web proxy tool (Fiddler2) to see what is sent/received; user do NOT get any problems. Can log in and use the CMS without any problems. As long as the local web proxy tool is used, user have no problems with the CMS. As soon as tool is shut down, same problems come back.
So using this tool, we cannot even debug as we don't know what impact fiddler has on the connection making it work. Just in one location for Prod and Test (same issues) but DEV still is fine.. so my deduction is.. "some rule in the local network" is wrong - but how to proceed?
The CME GUI loaded in the browser reguarly checks back with the CME server. This looks like the browser cannot get a connection with the CME server.
For further troublehsooting you can try what happens if you do a full reload (CTRL-F5) of the web browser to see if it has a connection issue indeed.
If it is a connection issue it might not be Tridion related at all.
This is probably a proxy issue -- especially since you say that you cannot reproduce it using Fiddler. Fiddler works by acting as a proxy, so that would explain the lack of symptoms when using it.
You can try just using your browser's developer tools (press F12). Then watch for any requests that come back with a different status code than 200 or 304. You can then show this to your network team who can hopefully troubleshoot the issue from there.
In my Project (ASP.NET, VB.NET), sometimes a Server Error is showing.
When this error is shown, Users cannot submit their Applications, so that they have to re-type full details and submit again.
How can I escape from these Server Errors?
I think the reason may be Memory issues. Because if the user try to submit again (after Sign Out->Sign In ) then they can submit. Daily twice or thrice Error is happening.
The word "Server" in the phrase "Server Error" refers to your ASP.NET code. You are the server!
If you are running .NET 2.0 or later, you can look into the Application event log (use the Event Viewer applet) for warnings from "ASP.NET". They will include details of what went wrong.
You need to debug your code to find out what's causing this, but the event logs will give you a starting point.
"Server Error" is just a generic message that indicates the the server code (your code) threw an exception that wasn't handled. It shows the user "server error" instead of a specific message so that no implementation details are exposed to outside users.
In other words, without debugging or looking at a log file or something, all you can tell from "Server Error" is that an Exception of any type was thrown.
Sorry, but the information you provided is not helpful in determining the issue.
I think that you'll need to provide a bit more info to get meaningful solutions.
Do you have server logs?
Can you debug through the app as the error occurs?
Does the error occur at a certain time of day, or after a certain regular action?
Does your app attempt to write to a file that may not be accessible?
is it possible that you are experiencing memory issues?
the list could go on, best to do some more investigation and if a more specific issue comes to light edit your question with the extra detail.
AFTER EDIT:
From the extra detail you've provided I wouldn't jump to memory as an issue, in signing out and back in the user is refreshing their session so everything is reset. If you are not seeing anything in your logs you'll need to look at your exception/error handling.
You just haven't provided enough info yet for us to work out the root issue, let alone suggest a solution. That's what you're seeing from all the answers here thus far. Find the event log info and there should be something there to help you, or at least something more to post here.
Try debugging the error? Server Error can be caused by various reasons.
Check for potential infinite loops.
Check for code in the constructor that might fail (especially for web services).
I think I've had cases like this which led to 'Server Error'. I'm assuming you mean the big red 'Server Error' message?
Save all your files and close your Visual Studio and now right click on Visual studio and run as administrator. It worked for me.