Custom SDK Application Holds an IPM Session ID Causing a 'Catastrophic failureAccess Violation' Error

(Doc ID 445725.1)

Last updated on AUGUST 18, 2017

Applies to:

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


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:


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 12471807 in the session map


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