Page 1 of 2

'Internal Server Error'

Posted: Mon Nov 06, 2017 9:22 pm
by martien
In the afternoon I got '_msg' => 'Internal Server Error' on
https://ops.epo.org/3.2/rest-services/p ... full-cycle ( q=applicant%3DIBM )

This however worked:
https://ops.epo.org/rest-services/publi ... full-cycle

and also this:
https://ops.epo.org/3.2/rest-services/c ... ?q=plastic
and this:
https://ops.epo.org//rest-services/clas ... ?q=plastic

Can I rely on forgetting the api-version part?

Regards,

Martien

Re: 'Internal Server Error'

Posted: Tue Nov 07, 2017 10:07 am
by EPO / OPS Support
Hi,

When you get the error, was it in time of the above announced maintenance release? Because its working when I try today.

Also, please formulated URL’s as they are in API Console: https://developers.epo.org/ It must ways contain a version – otherwise you are not reaching production version of OPS but old, outdated version.

We will soon announce a time line when URL will be amended to link to production version by default, witout versioning, but that is not the case yet. Please always follow our announcements in this forum to find out info about service being unavailable or timelines of OPS.

Regards,
OPS support

Re: 'Internal Server Error'

Posted: Tue Nov 07, 2017 3:43 pm
by martien
Hi,

please have a look on my log today:

1 Di 7. Nov 15:05:27 CET 2017 UA: https://ops.epo.org/3.2/rest-services/p ... full-cycle applicant=IBM
1 Di 7. Nov 15:05:27 CET 2017 UA-method post
1 Di 7. Nov 15:05:27 CET 2017 UA-status: 500 Internal Server Error
0 Di 7. Nov 15:05:27 CET 2017 srch: An unknown error occurred. Please contact Open Patent Services Team (http://forums.epo.org/open-patent-servi ... eb-service):

and not using the version:
1 Di 7. Nov 15:05:07 CET 2017 UA: https://ops.epo.org/rest-services/publi ... full-cycle applicant=IBM
1 Di 7. Nov 15:05:07 CET 2017 UA-method post
1 Di 7. Nov 15:05:07 CET 2017 UA-status: 200 OK

The same problem exists with looking for images.
Query for availability is ok with https://ops.epo.org//rest-services/publ ... .A1/images
Using the api results in "Not found":

1 Di 7. Nov 15:40:27 CET 2017 UA: https://ops.epo.org/3.2/rest-services/p ... .A1/images
1 Di 7. Nov 15:40:27 CET 2017 UA-method get
1 Di 7. Nov 15:40:27 CET 2017 UA-status: 404 Not Found

Loading a single image needs the version.


Regards,
Martien

Re: 'Internal Server Error'

Posted: Wed Nov 08, 2017 8:39 am
by EPO / OPS Support
Everything needs the version, not only images, otherwise it's not a production version of 3.2 but old outdated version that potentially gives you incomplete records.

As far as your POST requests, we are having a look at this again. You can also use GET in the meantime.

Regards,
OPS support

Re: 'Internal Server Error'

Posted: Wed Nov 08, 2017 12:26 pm
by martien
Hi,

thanks for your advice.
The get-method was ok for search.
For images however I get e.g.:

1 Mi 8. Nov 11:30:00 CET 2017 UA: https://ops.epo.org/3.2/rest-services/p ... .A1/images
1 Mi 8. Nov 11:30:00 CET 2017 UA-method get
0 Mi 8. Nov 11:30:00 CET 2017 error 404 Not Found:

1 Mi 8. Nov 11:31:24 CET 2017 UA: https://ops.epo.org/3.2/rest-services/p ... ff?Range=2
1 Mi 8. Nov 11:31:24 CET 2017 UA-method get
1 Mi 8. Nov 11:31:24 CET 2017 UA-args: $VAR1 = {};

1 Mi 8. Nov 11:31:24 CET 2017 UA-status: 404 Not Found

OK:
1 Mi 8. Nov 11:33:46 CET 2017 UA: https://ops.epo.org//rest-services/publ ... .A1/images
1 Mi 8. Nov 11:33:46 CET 2017 UA-method get
1 Mi 8. Nov 11:33:46 CET 2017 UA-args: $VAR1 = {};

1 Mi 8. Nov 11:33:46 CET 2017 UA-status: 200 OK

and
Mi 8. Nov 11:40:33 CET 2017 UA: https://ops.epo.org//rest-services/publ ... ff?Range=2
1 Mi 8. Nov 11:40:33 CET 2017 UA-method get
1 Mi 8. Nov 11:40:33 CET 2017 UA-args: $VAR1 = {};

1 Mi 8. Nov 11:40:33 CET 2017 UA-status: 200 OK

Re: 'Internal Server Error'

Posted: Wed Nov 08, 2017 12:50 pm
by martien

Re: 'Internal Server Error'

Posted: Wed Nov 08, 2017 1:14 pm
by EPO / OPS Support
I know that, I am just trying to explain since my first post on that you should not be using OPS without version before we don't fix it in 3.2. Just because its works for you it does not mean that the data that you are getting is either complete, correct or we can take any guarantee for it

Just wait for us to sort the 3.2 production version

Regards,
OPS support

Re: 'Internal Server Error'

Posted: Wed Nov 08, 2017 2:35 pm
by radium
Dear all,

I am experiencing the same problem as discussed above with my code since Tuesday morning. I think it's caused by the latest maintanance update.

Could you please specify the changes you have made to the POST interface?

Here's what I am trying to do:

I am trying to send an HTTP POST request to "https://ops.epo.org/3.2/rest-services/p ... full-cycle" using headers "Authorization=Bearer ((my token))" and "Accept=application/xml". The request's body is for instance "text/xml=EP1467955.B1".

Here's the server's response I am receiving since Tuesday morning:

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<fault xmlns="http://ops.epo.org">
    <code>SERVER.NotSupported</code>
    <message>An unknown error occurred. Please contact Open Patent Services Team (http://forums.epo.org/open-patent-services-and-publication-server-web-service)</message>
</fault>
Strangely, once I change the rest service's API version in my requested URI from 3.2 to 3.1 (i.e. sending my requests to "https://ops.epo.org/3.1/rest-services/p ... full-cycle"), everything works nicely.

Do you have any recommendations for me?

Thank you very much in advance!

Best regards
Stefan

Re: 'Internal Server Error'

Posted: Thu Nov 09, 2017 10:31 am
by EPO / OPS Support
Hi,

Please look at the "Content-Type" header and read a post on the same topic: https://forums.epo.org/400-bad-request- ... -post-7285

We will get back to everyone soon explaining a change in "Content-Type"

Regards,
OPS support

Re: 'Internal Server Error'

Posted: Thu Nov 09, 2017 11:29 am
by radium
Dear OPS Support,

Thank you very much for your quick and helpful response. Changing the Content-Type of my request did the trick.

When using RestSharp in combination with C#, here's how you change the Content-Type of your request:

Code: Select all

RestRequest req = new RestRequest("https://ops.epo.org/3.2/rest-services/published-data/publication/epodoc/full-cycle", Method.POST);
req.AddParameter("text/plain", "Body of your request, i.e. patent number", ParameterType.RequestBody); // replace your old Content-Type with "text/plain"
Thanks again!

Best regards,
Stefan