DRM Import Profiles That Worked in the Past Fail to Run After Changes Have Been Made to the EPMA Installation
Last updated on MARCH 08, 2017
Applies to:Hyperion Data Relationship Management - Version 184.108.40.206.501 and later
Information in this document applies to any platform.
DRM import profiles which were working in the past are no longer working when they are run from EPMA and errors like the following are seen in the EPMA DimensionServer.log:
Followed by an error like this in the EPMA DimensionServer.log indicating that there was a problem listing the versions with the getVersions method of the DRM web service:
at Hyperion.DimensionServer.Global.HandleThreadContext(Guid sessionID, ThreadContextDelegate method)
at Hyperion.DimensionServer.BaseProxy.HandleAPICall(Guid sessionID, ThreadContextDelegate method)
Similar errors could also potentially be seen when configuring DRM web service integration with EPMA for the first time.
Changes may have been made to the EPMA installation.
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