500 - Internal Server Error
Lee Daffern
from the Google web service?
I'm using a custom generic web service client to submit the requests
and interpret the results, and every now and then it responds with an
HTML document giving the above error instead of the expected XML
document. On resubmission (ie the exact same request), it usually
works fine, although occasionally I have to resubmit a couple of
times.
Any ideas?
Mark Doyle
I think the server is dead or dying. The sample programs in the SDK no longer work.
Shawn Hogan
It happens once in awhile... you just need to have code that takes it
into account (and possibly resubmit it automatically).
The last 48 hours has been much more than normal though... and as of
right now, the entire API system is down completely (for 2 hours so
far).
- Shawn
-----------------------------------------------------------
Free Keyword Placement and Back Links Tracker (Google API):
http://www.digitalpoint.com/tools/keywords/
Vu Nguyen
I am getting the same error as you. I get this message Client:Loading
the request into SoapReader failed. HRESULT=0x80070057. the wsdl is
not loading. Did google switch the wsdl location?
Antonio Gulli
slow time to answer. What it the everage time to get an answer for
you?
POST http://api.google.com/search/beta2
Accept: text/xml
Accept: multipart/*
Content-Length: 880
Content-Type: text/xml; charset=utf-8
SOAPAction: "urn:GoogleSearchAction"
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><namesp4:doGoogleSearch
xmlns:namesp4="urn:GoogleSearch"><key xsi:type="xsd:string"> !!!
REMOVED BY ME !!! </key><q xsi:type="xsd:string">data mining</q><start
xsi:type="xsd:int">0</start><maxResults
xsi:type="xsd:int">10</maxResults><filter
xsi:type="xsd:boolean">1</filter><restrict
xsi:type="xsd:string"/><safeSearch
xsi:type="xsd:boolean">1</safeSearch><lr xsi:type="xsd:string"/><ie
xsi:type="xsd:string">utf8</ie><oe
xsi:type="xsd:string">utf8</oe></namesp4:doGoogleSearch></SOAP-ENV:Body></SOAP-ENV:Envelope>
HTTP/1.1 500 Internal Server Error
Date: Wed, 21 Jan 2004 05:44:46 GMT
Server: e h c a p a
Content-Type: text/html; charset=iso-8859-1
Client-Date: Wed, 21 Jan 2004 11:47:39 GMT
Client-Peer: 216.239.51.82:80
Client-Response-Num: 1
Client-Transfer-Encoding: chunked
NnCoection: close
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>500 Internal Server Error</TITLE>
</HEAD><BODY>
<H1>Internal Server Error</H1>
The server encountered an internal error or
misconfiguration and was unable to complete
your request.<P>
Please contact the server administrator,
api-s...@google.com and inform them of the time the error
occurred,
and anything you might have done that may have
caused the error.<P>
More information about this error may be available
in the server error log.<P>
</BODY></HTML>
500 Internal Server Error at
/usr/lib/perl5/site_perl/5.8.0/SOAP/Lite.pm line 2834
l...@thedigitalscream.co.uk (Lee Daffern) wrote in message news:<c0148f54.04012...@posting.google.com>...
bobs
working fine ...
l...@thedigitalscream.co.uk (Lee Daffern) wrote in message news:<c0148f54.04012...@posting.google.com>...
Joe Pietroni
Thank you for bringing this to our attention. Occasionally, the Web API
servers are taken down temporarily for maintenance purposes. You should be
able to your submit your queries without a problem in the near future. We
apologize for any inconvenience. Please keep in mind that the Google API
program is in beta, and this service may experience fluctuations in its
availability.
Regards,
The Google Team
mark....@alum.mit.edu (Mark Doyle) wrote in message news:<63342d4f.04012...@posting.google.com>...
Nikhil
I have been getting the Internal Server Errors regarding "Unsupported
Response Content: text/html" must be "text/xml" for the last couple of
hours now.
Seems to be an internal problem with how the API works with the actual
search engine
If anyone has any idea about it , let me know.
Thanks
Nikhil
l...@thedigitalscream.co.uk (Lee Daffern) wrote in message news:<c0148f54.04012...@posting.google.com>...
Seamus Dromey
APi and I am having exactly the same problem. What is going on ????
Seamus Dromey
I cannot seem to access the Google API from my .NET Application either
and it was working fine until yesterday. What is going on???
David
Everything was fine until Jan 20 approx 8pm est
Now i am getting:
com.google.soap.search.GoogleSearchFault: [SOAPException:
faultCode=SOAP-ENV:Protocol; msg=Unsupported response content type
"text/html; charset=iso-8859-1", must be: "text/xml". Response was:
Any ideas anyone?
sh...@digitalpoint.com (Shawn Hogan) wrote in message news:<8b27cb28.04012...@posting.google.com>...
Google Web APIs Team
accept our apologies for the recent server instability around January
20 and January 21. Around 10AM California time we completed some
maintenance that should make the service more reliable. The server
should be working again.
The Web APIs are a beta service and may not always be available, but
we do try our best to make it work for you! We're sorry for the
inconvenience.
Shawn Hogan
Whatever you guys did, it's noticeably faster now too. :)
Google Web APIs Team
That's good to hear! We'd be interested to know more: do you have any
particular measurements of performance or reliability improvements?
Shawn Hogan
Well, I didn't do any official benchmarking on the old system, but the
new API servers (I'm assuming they are new servers) are most
definitely faster (I would conservatively guess they are 5 times
faster).
We have some free tools that use the Google API, and I've even had
users email asking how we made it so much faster (we didn't change
anything). So for them to go out of their way and ask, they had to
have noticed it too...