6 Replies Latest reply on Jan 10, 2019 8:40 PM by 3289602

    EM 12C LOGIN FAILED

    3289602

      I have a domain in production. Version 12.2.1.0.0 is presenting that the EM can not access but to the console of the servicebus and the weblogic I can enter. The error that indicates to me is the following: Login failed. Error connecting to the Server. Make sure that WebLogic connection information and the credentials entered are correct

       

        • 1. Re: EM 12C LOGIN FAILED
          3289602

          The following error also occurs: java.io.IOException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'

           

          [2018-12-26T11:42:18.131-04:00] [AdminServer] [ERROR] [] [oracle.sysman.core.model.targetauth.AppServerLogin] [tid: [ACTIVE].ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: eb57f0f0-97b3-4279-a6c4-50ea8428ac30-00000a9a,0] [APP: em] [partition-name: DOMAIN] [tenant-name: GLOBAL] Got exception while login- Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'[[

          java.io.IOException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'

           

          Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers']; remaining name 'domainruntime'

                  at weblogic.utils.StackTraceDisabled.unknownMethod()

          Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'

                  ... 1 more

          • 2. Re: EM 12C LOGIN FAILED
            Krishna vamsi

            Hi,

             

            Please check status of EM deployment from weblogic console

            • 3. Re: EM 12C LOGIN FAILED
              3289602

              hi, Krishna

               

              The EM status is active, the problem seems to be some user

              • 4. Re: EM 12C LOGIN FAILED
                Dirk.Nachbar

                Hi,

                 

                can you check what messages you got in $DOMAIN_HOME/sysman/log/emoms.log ?

                 

                Regards

                 

                Dirk

                • 5. Re: EM 12C LOGIN FAILED
                  3289602

                  Hello, Dirk

                  Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'we      blogic.management.mbeanservers']; remaining name 'domainruntime'at weblogic.utils.StackTraceDisabled.unknownMethod()

                  Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'

                   

                  Try to renable the compatibility mbeanserver,specify that the CompatibilityMBeanServerEnabled property has a value of "true". This can be done in several different ways:

                   

                   

                  1) Try to specify System property - the server should be started with

                   

                   

                  -Dweblogic.jmx.CompatibilityMBeanServerEnabled=true

                  • 6. Re: EM 12C LOGIN FAILED
                    3289602

                    <Property NAME="isAdminServer" VALUE="YES"/>  in some mserver. An SR was opened and the problem solved. Basically, multiple servers were run with the "YES" parameter