E1: UBE: All UBE Fails With Error "Failed to get extended token: eSecInvalidToken: The security token is invalid" (Doc ID 641644.1)

Last updated on AUGUST 14, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Symptoms

Information Center: Overview of Universal Batch Engine in the JD Edwards EnterpriseOne Tools and Technology Product > Information Center: Troubleshooting Universal Batch Engine in the JD Edwards EnterpriseOne Tools and Technology Product > Note 1513116.2

 

You have upgraded from Xe to 8.10. PORTTEST completes successfully, however unable to run any UBEs on the Enterprise Server nor locally.
In client jde.log the following errors are captured:

1352/1980 Mon Jun 27 19:45:35.499 Env.cpp136
Solution Explorer Started

1352/2000 Mon Jun 27 19:45:55.858 jdecsec.c1933
Failed to get extended token: eSecInvalidToken: The security token is invalid

1352/2000 Mon Jun 27 19:53:30.483 Jdbodbc.c5229
ODB0000163 - wSQLFetch failure. rc=-1

1352/2000 Mon Jun 27 19:53:30.483 Jdbodbc.c5229
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

1352/2000 Mon Jun 27 19:53:30.499 Jdb_drvm.c1566
JDB9900189 - Failed to verify that table exists in Versions - DV810

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