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

Create Index Problem

Status:
Completed
by Gordo Level 4 on ‎05-06-2015 01:46

I'm trying to create two new custom-field indexes on IoD.

 

Apparently I have 0/50 units used (though I have 1 index with custom fields)

A new custom index costs 12 units

When I try and add a new index the message says 

 

"Unable to create text index: Reached index quota - need 12 units, have 8 units left"

 

Can you explain why this is?

 

Thanks

 

Gordon

 

Status:
Completed

Hi Gordo,

 

The incorrect display of text index quotas you identified as been removed.

 

You can view you quotas at any time via: https://www.havenondemand.com/account/quotas.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

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

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:
Not an Issue

Why does it say Index Name invalid for some of the Requests - AddtoTextIndex

Status:
Not an Issue
by logontokartik Level 1 on ‎07-07-2014 02:21 - last edited on ‎07-07-2014 08:04 by Level 7

Hi,

For some requests its successful, but for some of the addtotextindex requests it says Index name invalid and returns 8002. Why does it do that? Below is one of the requests that failed.

 

https://api.idolondemand.com/1/api/sync/addtotextindex/v1?index=sfdc_idol_index&json=%7B%22documents... Method=GET]

 

 

{
  "error": 8002,
  "reason": "Job actions failed",
  "actions": [
    {
      "status": "failed",
      "action": "addtotextindex",
      "version": "v1",
      "errors": [
        {
          "error": 8002,
          "reason": "Index name invalid"
        }
      ]
    }
  ],
  "jobID": "usw3p_d564bc60-ee13-406a-a81c-c704aee704e0",
  "status": "failed"
}
Status:
Not an Issue
The reason this specific request fails is due to an invalid index name. The api-key is associated with a different index name as specified. I.e. the api-key and the current request are using sfdc_idol_index whilst the api-key is associaed with an index created called – kindex9
0 Likes
Status:
Completed

Not able to delete or query a text index

Status:
Completed
by hdas New Member on ‎07-12-2014 03:34

This is very weird. The text index is not working as expected. It seems to have a lot of bugs.

  1. Once the text index is created, it can not be deleted
  2. Even it can not be delected from IDOL on demand's UI interface
  3. API also can not delete it saying "Job action failed"
  4. Can not query anything from text index, again same error "Job action failed".

This is now very urgent. Please fix these issues.

Status:
Completed

Hi hdas,

 

We introduce a number of improvements in our release last week to improve the resilience of the createtextindex and deletetextindex APIs, as well as making them quicker to execute.  This should resolve your issue.


Do let us know if you have any further questions, issues or feedback.


Regards


Chris

0 Likes
Status:
Open

Key Management Service Error 5100

Status:
Open
by bcormode New Member on ‎04-28-2016 01:49

I'm trying to create a Standard text index using the 'Create Text Index' on the Try It interface.

 

I was able to create and delete a Text Index earlier today (a couple of times), but now it's not working.

 

I'm getting the following error:

 

{
  "error": 5100,
  "reason": "Job actions failed",
  "actions": [
    {
      "errors": [
        {
          "error": 5100,
          "reason": "Key Management Service Error",
          "detail": "<html><head><title>Apache Tomcat/7.0.52 (Ubuntu) - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - Internal Server Error</h1><HR size=\"1\" noshade=\"noshade\"><p><b>type</b> Status report</p><p><b>message</b> <u>Internal Server Error</u></p><p><b>description</b> <u>The server encountered an internal error that prevented it from fulfilling this request.</u></p><HR size=\"1\" noshade=\"noshade\"><h3>Apache Tomcat/7.0.52 (Ubuntu)</h3></body></html>"
        }
      ],
      "status": "failed",
      "action": "createtextindex",
      "version": "v1"
    }
  ],
  "status": "failed"
}

I checked my Account Subscription Quotas and they seem to be fine. 

0 Likes
Status:
Completed

View Document - "Error 5000"

Status:
Completed
by GuillermoGomez New Member on ‎03-07-2016 09:44

Hi,

 

The view document feature was working fine for me about a week ago in my project.  Then I suddenly started recieving errors any time I make a request to the document viewer.  Other parts of the API work just fine, such as the text extraction.  

 

When testing on the haven on demand website I recieve the same errors (Tried this for both .docx and .txt files):

{
  "error": 5000,
  "reason": "Job actions failed",
  "actions": [
    {
      "errors": [
        {
          "error": 5000,
          "reason": "Backend request failed",
          "detail": "Worker request failed"
        }
      ],
      "status": "failed",
      "action": "viewdocument",
      "version": "v1"
    }
  ],
  "status": "failed"
}

 

All the files I have tried so far do contain content and I am not just passing it an empty file.

 

Any suggestions to fixing this problem is greatly appreciated, thanks in advance!

Status:
Completed
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:
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:
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:
Completed

Hi

 

I am using the HTTP connector to index a site. I see that lot of data is not relevant and i want to remove it.

 

I tried the OOTB feaure Pre0=HtmlExtraction in CFS.cfg however i still see some data. Is it possible to custimize this OOTB HTML Extraction?

 

OR  

 

Do I need to write a LUA script to remove all the irelevant content? Is it possible to share such a LUA script with regex?

 

I am using IDOL 10.0 for now and will be updating it to 10.9 soon.

 

 

Thanks

Status:
Completed

Hi @VabsSharma,

 

Our recent update added clipping functionality to our Web Connector. In particular the clip page parameter available is documented in the link below.

 

https://dev.havenondemand.com/docs/Connectors_Web.html

 

Regards,

 

Jenn

Haven OnDemand team

0 Likes
Status:
Completed

I'm trying to make an api call to the test api calls in the facial recognition api, but I am receiving the following error:

 

{
  "error": 1000,
  "reason": "MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error."
}

 

Any help would be greatly appreciated!

 

Thanks!

Status:
Completed

Hi Bishoff,


Our engineers have resolved this issue.  Do let us know if you are having any further issues.

 

Regards

 

Chris

0 Likes
Status:
Completed

timeouts

Status:
Completed
by sinpa New Member ‎12-30-2014 01:39 - edited ‎12-30-2014 01:43
Hi I'm getting timeouts. Sample response using my Account: "We were unable to perform this search, please try another search." For this req: https://api.idolondemand.com/1/api/sync/querytextindex/v1?text=electric&indexes=my_index&print=all&a... ... In postman I get: { "error": 7000, "reason": "Request took too long" } Please help with this, I'm trying to develop a demo for customer Thanks!
Status:
Completed

Let me know if anything changes!

0 Likes
Status:
Completed

Create Text Index Keeps Failiing

Status:
Completed
by jcs New Member on ‎12-30-2014 10:16

https://www.idolondemand.com/developer/apis/createtextindex#try

 

Keeps failing when I try to create a new index.

 

 

"error": 5000,
"reason": "Job actions failed",
"actions": [
{
"errors": [
{
"error": 5000,
"reason": "Backend request failed",
"detail": "couldn't find handler for action: _indexstatus/v1"
}
],
"status": "failed",
"action": "createtextindex",
"version": "v1"
}
],
"status": "failed"

 

 

 

Status:
Completed
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

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