' Bad Abbrevation ' Error When Logging Into Financial Close Management (Doc ID 2213253.1)

Last updated on FEBRUARY 07, 2023

Applies to:

Symptoms

1) Cannot log into Financial Close Management or Account Reconciliation Manager

2) When attempting to log into FCM, the following errors can be seen in the logs:

From the FinancialClose.log

[2016-11-04T08:28:09.510-04:00] [FinancialClose#] [ERROR] [] [oracle.apps.epm.fcc.model] [tid: 21] [userId: XXXX] [ecid: 0000LWjJiOY7y0opGSO5yf1O6yXm0000Ij,0] [APP: FINANCIALCLOSE#11.1.2.0] [URI: /FCC-DataModel-context-root/SOAAMService] [SRC_CLASS: oracle.apps.epm.fcc.model.applicationModule.validation.FCMValidationManager] [SRC_METHOD: initSOAValidationVO] weblogic.rjvm.PeerGoneException: ; nested exception is: [[
java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
weblogic.rjvm.BubblingAbbrever$BadAbbreviationException: Bad abbreviation value: '87' oracle.bpel.services.workflow.client.WorkflowServiceClientException: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
.....................................................
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
weblogic.rjvm.BubblingAbbrever$BadAbbreviationException: Bad abbreviation value: '87'
.................................................
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
... 6 more
Caused by: java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
weblogic.rjvm.BubblingAbbrever$BadAbbreviationException: Bad abbreviation value: '87'
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:507)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:330)

From the Admin Server log:

2) ####<Nov 3, 2016 10:25:32 PM EDT> <Error> <Console> <SERVERNAME> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <epm_admin> <> <9c99ee0393199006:68297c89:1582cf51883:-8000-000000000000032d> <1478226332375> <BEA-240003> <Console encountered the following error weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090294]could not get connection
at weblogic.security.providers.authentication.LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3492)
at weblogic.security.providers.authentication.LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3479)
at weblogic.security.providers.authentication.LDAPAtnDelegate.listUsers(LDAPAtnDelegate.java:2267)
at weblogic.security.providers.authentication.LDAPAuthenticatorImpl.listUsers(LDAPAuthenticatorImpl.java:178)
at weblogic.security.providers.authentication.ActiveDirectoryAuthenticatorMBeanImpl.listUsers(ActiveDirectoryAuthenticatorMBeanImpl.java:227)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...........................................
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.lang.reflect.InvocationTargetException
at weblogic.security.providers.authentication.LDAPAtnDelegate$LDAPFactory.newInstance(LDAPAtnDelegate.java:4166)
at weblogic.security.utils.Pool.newInstance(Pool.java:37)
at weblogic.security.utils.Pool.getInstance(Pool.java:33)
at weblogic.security.providers.authentication.LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3487)

Cause

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