Unable to login to Essbase Admin Console

Error:
[2015-11-27T18:48:48.084+04:00] [EssbaseAdminServices0] [WARNING] [ESSEAS-00100] [oracle.epm.essbase.eas] [tid: 11] [userId: <anonymous>] [ecid: 00iX1oIWGFJFw00Fzzw0w00000ek0000Dz,0:1] [APP: EAS#11.1.2.0] [URI: /eas/eas] Unknown error occurred. See below stack trace for details[[
java.text.ParseException: Unparseable date: "0110"
    at java.text.DateFormat.parse(DateFormat.java:337)
    at com.essbase.eas.essbase.server.ServerPrimitives.getPropertiesLicense(Unknown Source)
    at com.essbase.eas.essbase.server.ServerLogic.getProperties(Unknown Source)
    at com.essbase.eas.essbase.server.ServerCommandListener.getProperties(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.essbase.eas.framework.server.application.AbstractCommandListener.handleEvent(Unknown Source)
    at com.essbase.eas.framework.server.application.DefaultCommandDispatcher.dispatchEvent(Unknown Source)
    at com.essbase.eas.framework.server.application.DefaultEventController.handleEvent(Unknown Source)
    at com.essbase.eas.framework.server.application.EventDispatcherWorkListener.handleEvent(Unknown Source)
    at com.essbase.eas.framework.server.application.DefaultWorkDispatcher.dispatchEvent(Unknown Source)
    at com.essbase.eas.framework.server.application.DefaultEventController.handleEvent(Unknown Source)
    at com.essbase.eas.framework.server.application.DefaultApplication.generateWorkEvent(Unknown Source)
    at com.essbase.eas.server.DefaultServlet.handleRequest(Unknown Source)
    at com.essbase.eas.server.AppManServlet.doPost(Unknown Source)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)



Solution:

This error can be ignored. If you see this error and you are facing issue with logging into the EAS Console then these two are pretty much unrelated errors. This error can be safely ignored. I have not been able to find the cause of it but I have seen it occurs in environments where upgrade was done from 11.1.2.3 to 11.1.2.4.
Client was not able to login to the server and a restart just fixed the issue.