SERVER.DomainAccess error

This space is made available to users of Open Patent Services (OPS) web-service and now also to users of EPO’s bulk data subscription products such as 14. EPO worldwide bibliographic database (DOCDB), 14.11 EPO worldwide legal status database (INPADOC), 14.12 EP full text data, 14.1 EP bibliographic data (EBD)and more.

Users can ask each other questions, exchange experiences and solutions, post ideas. The moderator will use this space to announce changes or other relevant information.
Post Reply

AntonFrolov
Posts: 12
Joined: Sat May 12, 2012 11:29 am

SERVER.DomainAccess error

Post by AntonFrolov » Tue Apr 15, 2014 1:42 pm

Hi,

On request

http://ops.epo.org/3.1/rest-services/pu ... escription

we get following error:

<fault xmlns="http://ops.epo.org">
<code>SERVER.DomainAccess</code>
<message>
The request could not be processed. Please try again later
</message>
</fault>

Regards,

Anton.


EPO / OPS Support
Posts: 1027
Joined: Thu Feb 22, 2007 5:32 pm

Re: SERVER.DomainAccess error

Post by EPO / OPS Support » Tue Apr 15, 2014 9:40 pm

Dear user,

You get error because there is no full text available for this CH A publication as you can see in Espacenet:

http://worldwide.espacenet.com/publicat ... cale=en_EP

But error message is not what one would expect. I will check that with our technical team and get back to you on that,

Kind regards,

OPS support


AntonFrolov
Posts: 12
Joined: Sat May 12, 2012 11:29 am

Re: SERVER.DomainAccess error

Post by AntonFrolov » Mon Apr 21, 2014 11:22 am

You get error because there is no full text available for this CH A publication
But why there is information about full text for description in fulltext method (http://ops.epo.org/3.1/rest-services/pu ... A/fulltext) response:

<ops:fulltext-instance system="ops.epo.org" lang="FR" desc="description">
<ops:fulltext-format-options>
<ops:fulltext-format>text-only</ops:fulltext-format>
</ops:fulltext-format-options>
</ops:fulltext-instance>

We have found one more document with same error:

http://ops.epo.org/3.1/rest-services/pu ... escription

Should we always consider error message "SERVER.DomainAccess" as full text absence reponse?

Regards,

Anton.


EPO / OPS Support
Posts: 1027
Joined: Thu Feb 22, 2007 5:32 pm

Re: SERVER.DomainAccess error

Post by EPO / OPS Support » Tue Apr 22, 2014 9:15 am

Dear user,

This CH A is also not available in our databases, either OPS or Espacenet because A code of CH in that case is not a laid open document. In both cases you have first publications available but as A4 and not as A.

So again, there is no CH A description/claims in Espacenet:
http://worldwide.espacenet.com/publicat ... cale=en_EP

But there is a CH 165460.A4 (Document laid open ( First level, searched and preliminary examination)
)available:
http://ops.epo.org/3.1/rest-services/pu ... escription
http://ops.epo.org/3.1/rest-services/pu ... .A4/claims

It is always best to consult Espacenet when you get no results and to check concordance tables on our website to see which codes are to be used when searching for biblio only or when you need full text.

Message you are getting does not seem appropriate to me so I did send request for check and change to our IT already last time but for such changes we need to wait for next release and I also did not get any reply yet. I will get back to you on that error message once I know more.

Kind regards,
OPS support


AntonFrolov
Posts: 12
Joined: Sat May 12, 2012 11:29 am

Re: SERVER.DomainAccess error

Post by AntonFrolov » Tue Apr 22, 2014 1:03 pm

This CH A is also not available in our databases, either OPS or Espacenet because A code of CH in that case is not a laid open document.
If this document (CH.366243.A) is not available in your database, then why I get correct result on request for it's bibliography (http://ops.epo.org/3.1/rest-services/pu ... 3.A/biblio) and fulltext (http://ops.epo.org/3.1/rest-services/pu ... A/fulltext)?

Regards,

Anton.


EPO / OPS Support
Posts: 1027
Joined: Thu Feb 22, 2007 5:32 pm

Re: SERVER.DomainAccess error

Post by EPO / OPS Support » Tue Apr 22, 2014 6:25 pm

There seem to be a problem with loaded CH documents alltogether. Our IT is looking at it now. Some applications are wrongly linked together so hopefully they can fix it soon. I will get back to you on that once we know more.

Kind regards,
OPS support


Post Reply