Why Intent Responses and Managed Answers are not showing correctly - error: Unable to decrypt string (Doc ID 1040106.1)

Last updated on APRIL 27, 2016

Applies to:

Oracle Knowledge - Version 8.0.x and later
Information in this document applies to any platform.
Information in this document applies to any platform.

Symptoms

When an Intent Response or a Managed Answer holds a reference to IM doc ( in the form of docID:channel_refkey/@field for intent responses) IMWS is called to validate and retrieve the doc.  From testdrive or the runtime, if the IMWS connection is not working, then an error will occur.

From testdrive:

"The Response content referenced by 'MAR13:X_MANAGED_RESPONSE/@TITLE' was not loaded from the Information Manager for the following reason:

Unable to decrypt string
Given final block not properly padded"

From workbench this error can be a number of things.  once you say ok to the error then the stack trace and java exception should appear.

This error will occur if all the locale tabs used are not enabled in the number.xml file.  Go to the languages tab in system manager and enable all the locales in the intent response.

java.lang.NullPointerException
at com.inquira.workbench.language.intents.AnswerFrame.populateFromObject(AnswerFrame.java:523)
at com.inquira.workbench.language.intents.AnswerFrame.createFrame(AnswerFrame.java:109)
at com.inquira.workbench.language.DomainDataObjectFrame.createFrame(DomainDataObjectFrame.java:734)
at com.inquira.workbench.language.search.FoundItem.createFrame(FoundItem.java:131)
at com.inquira.workbench.language.search.Roster$2.task(Roster.java:677)
at com.inquira.workbench.StatusTask.doWork(StatusTask.java:147)
at com.inquira.workbench.StatusTask.access$000(StatusTask.java:51)
at com.inquira.workbench.StatusTask$2.construct(StatusTask.java:118)
at com.inquira.swingx.sun.SwingWorker$2.run(SwingWorker.java:142)
at java.lang.Thread.run(Thread.java:662)

From the workbench or the runtime.

When this Intent Response is triggered, the rule engine tries to retrieve this IR's value , which is retrieved thru IMWS call to IM side.  After the initial call the value and its contentdata are cached in the IMWSClient on the runtime.  The next time the same Intent Response is fired, the cached data is used.  The data is not retrieved from IMWS again and the connection to IM is irrelevant here ( IMWS, IM or IM DB ). 

Changes

 If the IM document is not showing correctly in the search results here are the things to check.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms