Service Issues

Report any Haven OnDemand API service issues to the development team here. Before submitting your issue and for issue status definitions, be sure to read this page.
Search the Dev Community
Showing results for 
Search instead for 
Do you mean 
Post a Message
0 Likes
Status:
Completed
Hi,

I am currently running into issues when tring to use the news_eng index from the querytextindex api. Is this simply an temporary outage? It was working fine yesterday and the service status is not showing any disruptions.

Thanks

{ "error": 5000, "reason": "Job actions failed", "actions": [ { "status": "failed", "action": "querytextindex", "version": "v1", "errors": [ { "error": 5000, "reason": "Backend request failed", "detail": "ERROR" } ] } ], "jobID": "usw3p_48d7f265-b0ff-4dcd-8543-099ee4bf0811", "status": "failed" }
Status:
Completed
0 Likes
Status:
Not an Issue

Speech recognition error 5000

Status:
Not an Issue
by krishnaguy New Member on ‎03-12-2016 04:17

I am trying to call the speech to text services via Python, but get a "Backend request failed" error. However I do get results when I upload the file via the "Try it" interface.

 

My code snippet below:

 

import requests

r = requests.post('https://api.havenondemand.com/1/api/async/recognizespeech/v1', data = {'apikey':'KEY', 'language':'en-US-tel', 'file':'file_name_with_full_path'})

 

and the error:

 

{u'actions': [{u'action': u'recognizespeech',
   u'errors': [{u'error': 5000, u'reason': u'Backend request failed'}],
   u'status': u'failed',
   u'version': u'v1'}],
 u'jobID': u'JOB-ID',
 u'status': u'failed'}

 

I have attached the sample wav file that I was using as well. 

Status:
Not an Issue

Hi Krishnaguy,


Thanks for getting back to us with the update.


Do let us know if you need anything further.

 

Chris
Haven OnDemand team

0 Likes
Status:
Completed

Broken Parametric Refinement

Status:
Completed
by Gordo Level 4 on ‎02-18-2015 05:34

https://api.idolondemand.com/1/api/sync/querytextindex/v1?text=pensions&start_tag=<span class=result...

 

This gives the error 

 

{
  "error": 4024,
  "reason": "Job actions failed",
  "actions": [
    {
      "errors": [
        {
          "error": 4024,
          "reason": "Field_text contains operations on unoptimized fields",
          "detail": "'The fieldtext contained an operation against a non-optimized field.'"
        }
      ],
      "status": "failed",
      "action": "querytextindex",
      "version": "v1"
    }
  ],
  "status": "failed"
}

 

According to the documentation :

 

https://www.idolondemand.com/developer/docs/PublicDatasets.html

 

rss_sourceStringParametric

 

This worked last week.

Status:
Completed
0 Likes
Status:
Completed

Tokenize text transaction failing

Status:
Completed
by Ward Level 3 on ‎06-10-2014 01:37

The following curl seem to be failing when I try to token a pdf file:

 

curl "https://api.idolondemand.com/1/api/sync/tokenizetext/v1?reference=417f7ea5-8acd-425d-91c2-1901170b82...

Status:
Completed
Ward, We traced this to an issue in our system that has now been resolved. Apologies for any inconvenience. Chris
0 Likes
Status:
In Progress

Hello, I have several API keys that were compromised, and I would like to delete them as soon as possible, but there seems to be no option to delete the API keys in the account settings. Thank you.

Status:
In Progress

Thanks Johnsonshi,

 

The feature you mention is on our roadmap for later in the year.  In the meantime if you would like us to delete any API Keys for you - please provide details via the contact us form. (https://www.havenondemand.com/contactus.html)


Regards

 

Chris

Haven OnDemand team

0 Likes
Status:
Not an Issue

I'm using the entity extraction API and finding that 'Michael Roe' is extracted from my uploaded document. But in the uploaded document two people names is there Ulrich Bernier and Michael Roe. So How can i get the both names Ulrich Bernier and Michael Roe.

Status:
Not an Issue
0 Likes
Status:
Completed

I'm not sure if this is the same issue as  IODI-166 but there is a disparity between counts made in the calls to getparametricvalues and querytextindex

 

URL:

 

https //api.idolondemand.com/1/api/sync/getparametricvalues/v1?text=mars&indexes=news_eng&&field_text=( MATCH{the%20telegraph}:*/RSS_SOURCE )&sort=document_count&document_count=true&field_name=RSS_SOURCE,RSS_CATEGORY,WIKIPEDIA_TYPE,PERSON_PROFESSION,PLACE_COUNTRY_CODE,COMPANY_EXCHANGE&max_values=20&apikey=<APIKEY>

 Results

  

"RSS_SOURCE":
{
"THE TELEGRAPH": 998
}

 

URL : 

 

https //api.idolondemand.com/1/api/sync/querytextindex/v1?text=mars&max_page_results=10&absolute_max_results=10&indexes=news_eng&&field_text=( MATCH{the%20telegraph}:*/RSS_SOURCE )&summary=concept&print_fields=autn:title,DREDBNAME,DATE,RSS_URL,RSS_RANK,RSS_COPYRIGHT,RSS_SOURCE,RSS_CATEGORY,MODIFIED_DATE,WIKIPEDIA_TYPE,WIKIPEDIA_ALIAS,WIKIPEDIA_CATEGORY,WIKIPEDIA_INFOBOX,WIKIPEDIA_ALTTITLE,WIKIPEDIA_TITLE_ENG,CONTENT_LENGTH,WIKIPEDIA_RANK,WIKIPEDIA_ID,WIKIDATA,PERSON_PROFESSION,PERSON_DATE_OF_BIRTH,PERSON_DATE_OF_DEATH,LON_NUMBER,LAT_NUMBER,PLACE_POPULATION,PLACE_COUNTRY_CODE,PLACE_REGION1,PLACE_REGION2,PLACE_ELEVATION,COMPANY_RIC,COMPANY_TICKER,COMPANY_EXCHANGE,COMPANY_WEBSITE&start=1&total_results=true&sort=relevance&highlight=terms&sentences=3&predict=false&start_tag=<span class=resulthighlight>&apikey=<APIKEY>

 Results:

 

"totalhits": 958

 Why is there a difference? Is it just down to predicting the values? If so, is there a way to disable predicts?

 

Thanks

 

Gordon

 

 

 

Status:
Completed
0 Likes
Status:
Completed

Error 7000 Sentiment Analysis

Status:
Completed
by j3pydev Level 1 on ‎10-05-2014 01:26

I'm a student using the sentiment analysis api to analyze tweets from Twitter, but despite my best efforts to space out my queries I keep running into this response from the sentiment api: {u'error': 7000, u'reason': u'Request took too long'}.  I am trying to analyze a significant number of tweets (around 1000), but it seems that even though I've spaced out my queries so that one tweet is sent with a pause of 10 ms up to 1 second I still get this error.  My last test was 1000 tweets with a one second pause between queries and at 16.2 minutes I received the 7000 error.  Any thoughts/suggestions/insights on this would be greatly appreciated.  It would be really cool if I could batch the tweets (send a whole list of them at once).

Status:
Completed

Hi @j3pydev,

 

We haven't heard back from you about your issue with the Sentiment Analysis Error 7000 so I'm going to close this thread.  Should you have any more issues please create a new thread or reach out to me through private message.  

 

Thanks,

 

Jenn

 

HPE Haven OnDemand Team

 

0 Likes
Status:
Completed

HTTPS issue

Status:
Completed
by Ward Level 3 on ‎02-24-2015 06:54

I'm seeing the following error when I try to connect to IDOL OnDemand since about 4 PM EST today:

 

Creating index merge_case_index1 failed with error java.lang.RuntimeException: Could not generate DH keypair
 
There another user who is trying to connect from Salesforce.com to IDOL who is experiencing the same issue.  Seems like maybe there has been a certificate expiration or something.  Is that possible?
Status:
Completed

Ward,

 

This issue has be traced to the continued usage of Java 6 which is unable to negotiate SSL to modern standards.  As an interim measure until Salesforce update to a later version , we are permitting lower grade ciphers for connections from the Salesforce IP range.

 

Regards


Chris

0 Likes
Status:
Open

Sentiment Analysis API V1: requests are not completing, and are returning Error 7000 - Request took too long.

 

We noticed API calls faling with the above error, as of 4/30/2017 around 5pm GMT—and it appears to still be failing as of this morning. The "Try It" feature on the product page for both V1 and V2 fails with the same error:

 

https://dev.havenondemand.com/apis/1/analyzesentiment#try

 

Prior to this, other than intermittent outages, we have had no issue working with this service. I'm not sure if there is any additional information I can provide, but if so, please let me know.

 

 

 

 

0 Likes
Status:
Not an Issue

Patents QueryTextIndex by reference

Status:
Not an Issue
by Gordo Level 4 on ‎03-23-2015 09:22

If I do the following query:

 

curl "https://api.idolondemand.com/1/api/sync/querytextindex/v1?text=DREALL&indexes=patents&summary=concept&apikey=<APIKEY>"

 I get back some results:

 

 "documents": [
    {
      "reference": "http://www.google.com/patents/USD07640597",
      "weight": 85.35,
      "links": [],
      "index": "patents",
      "title": "Image display device",
.....

 If i then try and query for this reference:

 

curl "https://api.idolondemand.com/1/api/sync/querytextindex/v1?reference=http%3A%2F%2Fwww.google.com%2Fpatents%2FUSD07640597&indexes=patents&apikey=<APIKEY>"

 I get the following:

 

{
  "error": 5013,
  "reason": "Job actions failed",
  "actions": [
    {
      "errors": [
        {
          "error": 5013,
          "reason": "Reference does not exist"
        }
      ],
      "status": "failed",
      "action": "querytextindex",
      "version": "v1"
    }
  ],
  "status": "failed"
}

 Is this a bug or am I misunderstanding something?

Status:
Not an Issue

Gordo,

 

Reference is his case is a reference to a file uploaded via the storeobject API rather than an index reference.

 

If you are trying to retrieve the given document you will need to use getcontent & the index_reference parameter, or if you would like to do findsimilar to find similar documents, you will again need to pass the reference as index_reference rather than reference.

 

Regards


Chris

IDOL OnDemand team

0 Likes
Status:
Completed

I created a text index by the name yashiaas using the CreateTextIndex api and it returned success.

 

Then i tried to create a connector with this index as destination but it failed indicating the index does not exist.

 

I then used the ListIndexes to see if it would show up the index i had created earlier, it showed up close to 12 indexes but not yashiaas - the one i had created.

 

Is there something wrong that i am doing here?

 

Thanks,

 

YD

Status:
Completed

Quota was increased when requested

0 Likes
Status:
Completed

Arxiv GetContent

Status:
Completed
by Gordo Level 4 on ‎03-20-2015 07:31

If we try and do a GetContent request for the Arxiv index we get an error :

 

 

curl "http://<REMOVEME>api.idolondemand.com/1/api/sync/getcontent/v1?indexes=arxiv&index_reference=http%3A%2F%2Farxiv.org%2...

 

{
  "error": 8002,
  "reason": "Job actions failed",
  "actions": [
    {
      "errors": [
        {
          "error": 8002,
          "reason": "Index name invalid"
        }
      ],
      "status": "failed",
      "action": "getcontent",
      "version": "v1"
    }
  ],
  "status": "failed"
}
Status:
Completed

Thanks Gordo for taking time to raise this issue.

 

Our Engineers have now enabled the Arxiv index for getcontent.  Please do let us know if you have any further issues.

 

Regards

 

Chris

IDOL OnDemand Team

0 Likes
Status:
Completed

This is most likely not a service issue, though probably it is.

When I visit the Showcase Gallery and click the Expire Social example, it brings me to the application website.
http://www.expiresocial.com/

There I click the "Login with Facebook" button and the browser redirects me to a page which says that it is an infinite cycle redirect.

https://www.facebook.com/dialog/oauth?client_id=331301670345945&redirect_uri=http%3A%2F%2Fwww.expire...

 

It happens no matter which permissions the Facebook authorized user grants to the application.

Status:
Completed

Ilia,

 

Thanks for taking the time to report this issue.  This issue has now been resolved.

 

Regards


Chris

IDOL OnDemand team

0 Likes
Status:
Completed

Having posted a largish (200Mb file) to the recogniser service using the following:

 

curl "https://api.idolondemand.com/1/api/async/recognizespeech/v1" -X POST -H Content-Type:multipart/form-data; --insecure -o response.json -F apikey=<APIKEY> -F language=enuk -F file=@trimmed.mp4

 

I check the status

 

curl "https://api.idolondemand.com/1/job/status/usw3p_4b284786-2b80-475c-8674-6f9c29422cb7" -X POST --insecure -F apikey=<APIKEY>
{
"actions": [
{
"errors": [
{
"error": 5000,
"reason": "Backend request failed"
}
],
"status": "in progress",
"action": "recognizespeech",
"version": "v1"
}
],
"jobID": "usw3p_4b284786-2b80-475c-8674-6f9c29422cb7",
"status": "queued"
}

 

Why am I getting this:

 

"error": 5000,
"reason": "Backend request failed"

 

Is this indicative of a problem or should I disregard this and assume that my request is still queued?

 

Thanks

 

Gordon

 

Status:
Completed
0 Likes
Status:
Open

I'm getting an error 7000 when trying to call the AddToTextIndex API.The message is "Request took too long". This is only happening on a recently created index of the jumbo flavor.

 

Is anybody experiencing the same issue? 

 

Best regards,

Carlos Jourdan

0 Likes
Status:
Open

Speech Recognition API

Status:
Open
by DariaP Level 1 on ‎04-06-2016 05:21

I try to use Speech Recognition API with video hpnext.mp4. I get jobId and i check statuse during day, but every time i get statuse :  queued...

0 Likes
Status:
Completed

I am trying to send Email messages to the following HP IDOL contact addresses:

I have tried sending from my personal Gmail address and from our company second-level domain mailbox.

 

In any case the message delivery fails permanently with the following messages.

The original message was received at Mon, 20 Oct 2014 07:57:55 GMT
from [15.125.106.235]

   ----- The following addresses had permanent fatal errors -----
<idolondemand@hp.com>
    (reason: 450 4.7.1 Client host rejected: cannot find your hostname, [64.79.140.199])

   ----- Transcript of session follows -----
... while talking to smtp1.hp.com.:
>>> DATA
<<< 450 4.7.1 Client host rejected: cannot find your hostname, [64.79.140.199]
<idolondemand@hp.com>... Deferred: 450 4.7.1 Client host rejected: cannot find your hostname, [64.79.140.199]
<<< 554 5.5.1 Error: no valid recipients
Message could not be delivered for 5 days
Message will be deleted from queue

Original-Recipient: rfc822;idolondemand@hp.com
Final-Recipient: RFC822; idolondemand@hp.com
Action: failed
Status: 4.4.7
Remote-MTA: DNS; smtp1.hp.com
Diagnostic-Code: SMTP; 450 4.7.1 Client host rejected: cannot find your hostname, [64.79.140.199]
Last-Attempt-Date: Sat, 25 Oct 2014 07:58:18 GMT

 The SMTP headers have these records:

Received: by 10.140.83.136 with SMTP id j8csp3326qgd;
        Sat, 25 Oct 2014 00:58:22 -0700 (PDT)
X-Received: by 10.194.91.176 with SMTP id cf16mr9952863wjb.60.1414223901302;
        Sat, 25 Oct 2014 00:58:21 -0700 (PDT)
Return-Path: <>
Received: from mailserver-las-01.optimost.com ([64.79.140.199])
        by mx.google.com with ESMTPS id s6si7717454wjx.58.2014.10.25.00.58.20
        for <koichisenada@gmail.com>
        (version=TLSv1 cipher=RC4-SHA bits=128/128);
        Sat, 25 Oct 2014 00:58:21 -0700 (PDT)
Received-SPF: none (google.com: mailserver-las-01.optimost.com does not designate permitted sender hosts) client-ip=64.79.140.199;
Authentication-Results: mx.google.com;
       spf=neutral (google.com: mailserver-las-01.optimost.com does not designate permitted sender hosts) smtp.mail=
Received: from localhost (localhost)
	by mailserver-las-01.optimost.com (8.13.8/8.13.8) id s9P7rpZl025902;
	Sat, 25 Oct 2014 07:58:18 GMT
Date: Sat, 25 Oct 2014 07:58:18 GMT
From: Mail Delivery Subsystem <MAILER-DAEMON@autonomy.com>
Message-Id: <201410250758.s9P7rpZl025902@mailserver-las-01.optimost.com>
To: <koichisenada@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
	boundary="s9P7rpZl025902.1414223898/mailserver-las-01.optimost.com"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--s9P7rpZl025902.1414223898/mailserver-las-01.optimost.com

The original message was received at Mon, 20 Oct 2014 07:57:55 GMT
from [15.125.106.235]

   ----- The following addresses had permanent fatal errors -----
<idolondemand@hp.com>
    (reason: 450 4.7.1 Client host rejected: cannot find your hostname, [64.79.140.199])

   ----- Transcript of session follows -----
... while talking to smtp1.hp.com.:
>>> DATA
<<< 450 4.7.1 Client host rejected: cannot find your hostname, [64.79.140.199]
<idolondemand@hp.com>... Deferred: 450 4.7.1 Client host rejected: cannot find your hostname, [64.79.140.199]
<<< 554 5.5.1 Error: no valid recipients
Message could not be delivered for 5 days
Message will be deleted from queue

--s9P7rpZl025902.1414223898/mailserver-las-01.optimost.com
Content-Type: message/delivery-status

Reporting-MTA: dns; mailserver-las-01.optimost.com
Arrival-Date: Mon, 20 Oct 2014 07:57:55 GMT

Original-Recipient: rfc822;idolondemand@hp.com
Final-Recipient: RFC822; idolondemand@hp.com
Action: failed
Status: 4.4.7
Remote-MTA: DNS; smtp1.hp.com
Diagnostic-Code: SMTP; 450 4.7.1 Client host rejected: cannot find your hostname, [64.79.140.199]
Last-Attempt-Date: Sat, 25 Oct 2014 07:58:18 GMT

--s9P7rpZl025902.1414223898/mailserver-las-01.optimost.com
Content-Type: message/rfc822

 

Status:
Completed

Illa,

 

Thank you again for raising this issue.

 

We have made changes to prevent these bounces in future.  Please do let us know if you have any further issues.

 

 

Regards


Chris

IDOL OnDemand team

0 Likes
Status:
Open

Hi,

 

I have tried to use your "Contact Us" form, from both Chrome (v53) and Edge on a Windows 10 machine, but the submit button does nothing. I've tried it both logged in and logged out of your site.

 

 

0 Likes
Status:
Completed

api key required

Status:
Completed
by jul New Member on ‎07-20-2015 08:14

Hello

 

I am using a Python script to do requests to the sentiment analysis API.

The request is the following

 

textAPI = text_from_tweet['text'].replace(" ","+")

r=requests.get("https://api.idolondemand.com/1/api/sync/analyzesentiment/v1?text="+textAPI+"&language=eng&apikey=xxx...

 

Sometimes it works, sometimes it gives this error instead :

 

{
"message": "API key required",
"detail": {
                    "error": 2000
              }
}

 

I tried to add a time.sleep(1) to test if the requests were too close one to the other, but it stayed the same.

 

Is it an issue ?

 

Julien

Status:
Completed

Hi @jul,

 

We haven't heard back from you about your issue with the API key so I'm going to close this thread.  Should you have any more issues please create a new thread or reach out to me through private message.  

 

Thanks,

 

Jenn

 

HPE Haven OnDemand Team

Social Media
† The opinions expressed above are the personal opinions of the authors, not of HPE. By using this site, you accept the Terms of Use and Rules of Participation