My Oracle Support Banner

Custom SDK Application Holds an IPM Session ID Causing a 'Catastrophic failureAccess Violation' Error (Doc ID 445725.1)

Last updated on SEPTEMBER 10, 2019

Applies to:

Oracle Imaging and Process Management - Version 7.6.2.0.0 to 10.1.3.6 [Release Stellent to 10gR3]
Information in this document applies to any platform.

Symptoms

When a custom SDK application holds an IPM session id, the below symptoms may occur:

On a Workstation:

TITLE: DocumentActionsToolInitInstance Error:-2147418113

catastrophic failureAccess Violation(0xc0000005)
class ATL::CComObject <class CRoot>::Put_UserToken
class ATL::CComObject <class CRoot>::Put_UserToken

Click on OK and the next error appears:

TITLE: IBPM Error!

OK DETAILS (Click on Details):

The CoCreateInstance call failed on the following ITool:
Document Actions Tool

Also within the UCON logs. the following error appears:

UCON failed to find sessionID XXXXXXXX in the session map

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution

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