My Oracle Support Banner

EPM: Unable to access EPM applications after Oracle Critical Patch Update, Workspace Error: 'Error 404--Not Found', 'Invalid or could not find module configuration "hfmadf.application"', 'Invalid or could not find module configuration "aif.launch"' (Doc ID 2983171.1)

Last updated on OCTOBER 25, 2023

Applies to:

Hyperion Financial Management - Version 11.2.14.0.000 and later
Hyperion BI+ - Version 11.2.14.0.000 and later
Information in this document applies to any platform.

Symptoms

Unable to access EPM products after applying Oracle Critical Patch update.

When Foundation servers are affected, error can occur when trying to access Workspace page:

Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

HyS9FoundationServices_epmsystem1-sysout.log will show errors like the following during startup:

<Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application "SHAREDSERVICES [Version=11.1.2.0]".
weblogic.application.ModuleException: java.lang.ClassNotFoundException: org.codehaus.jackson.jaxrs.JacksonJsonProvider 

 

When HFM Web servers are affected, error can occur when trying to open HFM application or Consolidation Administration:

 

Description: Invalid or could not find module configuration "hfmadf.application".
The required application module "hfmadf.application" is not configured.
A "Not Found" error occurred communicating with the server. 

 

HyS9FinancialManagementWeb_epmsystem1-sysout.log will show errors like the following during startup:

 

<Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: com/oracle/adfm, Specification-Version: 1, referenced from: D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\HFMWeb0\tmp\servers\HFMWeb0\tmp\_WL_user\FMADFWEB_11.1.2.0\jiemyk]. Ensure that the referenced optional package has been deployed as a library.>

<Warning> <EJB> <BEA-011157> <An exception occurred while preparing the EJB module AppAsyncMdb.jar.
weblogic.application.ModuleException: The following exception occured while processing annotations: Error processing annotations: .
at weblogic.ejb.container.deployer.EJBMetadataHandler.processAnnotations(EJBMetadataHandler.java:167)
at weblogic.ejb.container.deployer.EJBMetadataHandler.processAnnotations(EJBMetadataHandler.java:157)
at weblogic.ejb.container.deployer.EJBModule.processAnnotations(EJBModule.java:175)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:370)
at weblogic.application.internal.ExtensibleModuleWrapper$PrepareStateChange.next(ExtensibleModuleWrapper.java:295)
Truncated.
Caused By: java.lang.ClassNotFoundException: org.codehaus.jackson.jaxrs.JacksonJaxbJsonProvider

 

 

When FDMEE servers are affected, error can occur when trying to open Data Management:

 

An error occurred processing the result from the server.Description: Invalid or could not find module configuration "aif.launch".

 

HyS9aifWeb_epmsystem1-sysout.log will show errors like the following during startup:

 

<Error> <Deployer> <BEA-149205> <Failed to initialize the application "AIF [Version=11.1.2.0]" due to error weblogic.application.ModuleException: Error getting classes annotated @ManagedBean, @Interceptor or @Interceptors

weblogic.application.ModuleException: Error getting classes annotated @ManagedBean, @Interceptor or @Interceptors

at weblogic.managedbean.ManagedBeanModuleExtensionFactory.create(ManagedBeanModuleExtensionFactory.java:93)

at weblogic.application.internal.ExtensibleModuleWrapper.createModuleExtensions(ExtensibleModuleWrapper.java:264)

at weblogic.application.internal.ExtensibleModuleWrapper.initDrivenObjectArray(ExtensibleModuleWrapper.java:232)

at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:107)

at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)

Truncated.

Caused By: java.lang.ClassNotFoundException: org.codehaus.jackson.jaxrs.JacksonJaxbJsonProvider

 

 

Changes

 Applied Critical Patch Update (CPU) to working environment

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.