My Oracle Support Banner

Presentation API queries against MDEX 6.2 fail with "Navigation Engine not able to process request" ENEException messages (Doc ID 1399513.1)

Last updated on FEBRUARY 13, 2020

Applies to:

Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 6.2.0 and later
Information in this document applies to any platform.


Queries sent to MDEX 6.2 dgraphs via the Oracle Endeca Presentation API fail with "Navigation Engine not able to process request" ENEException messages along these lines:

com.endeca.navigation.ENEException: Navigation Engine not able to process request 'http://<mdexhost>:15000/graph?node=0&offset=0&nbins=10&irversion=601'.

When this occurs, the dgraph error log shows two messages of ERROR and WARN levels, respectively:

ERROR 04/06/12 15:38:39.501 UTC (1315323519501) DGRAPH {dgraph} Requested output IR version '601' is supported by this release of the software but not enabled. Use the --back_compat flag to enable the older IR version. 

WARN 04/06/12 15:38:39.501 UTC (1315323519501) DGRAPH {dgraph} Error processing HTTP exchange 2: Error:[MDEX] Failed to parse URL: '/graph?node=0&offset=0&nbins=10&irversion=601' 


This issue is typically encountered when installing or upgrading the MDEX.  In this example MDEX 6.2 is the version being upgraded to but this issue applies when upgrading most MDEX versions, where --back_compat will need to be adjusted.


To view full details, sign in with your My Oracle Support account.

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

In this Document
 Install Presentation API version 6.2.x in Front-End Application
 Enable --back_compat flag in dgraph options

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.