Admin server console forbidden

Hi,
in weblogic 11gR , in user projects, base-domain when click on Admin server console, in browser I will have HTTP 403 Forbidden. And in cmd box of start Admin server I have :
<30 avr. 2010 13 h 37 CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<30 avr. 2010 13 h 37 CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<30 avr. 2010 13 h 37 CEST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on
<30 avr. 2010 13 h 37 CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<30 avr. 2010 13 h 40 CEST> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <Servl
etContainerAdapter manager not initialized correctly.>Thank for help.

If you have Configuration Auditing enabled ( Domain -> Archive Configuration Count value greater than 0 )
- "The number of archival versions of config.xml saved by the Administration Server each time the domain configuration is modified." -
you would have older / backup copies of the config.xml created ( in the domain_home / configArchive.
If you are only maintaining 1 copy of config.xml, it is more difficult to restore a working version.
Is the console enabled in your config.xml?
<console-enabled>true</console-enabled>
<console-context-path>console</console-context-path>
<console-extension-directory>console-ext</console-extension-directory>
Is your admin server responding to telnet on that IP:Port combination?
Does the console page display at all? Or does it display but you are unable to login?
Is the listen port enabled?
<listen-port>7001</listen-port>
<listen-port-enabled>true</listen-port-enabled>

Similar Messages

  • Problem while starting Managed Servers from Admin Server console

    I am facing a problem while trying to start the managed servers in wlp8.1 portal from the admin server console.
    <Dec 7, 2004 4:52:14 PM IST> <Info> <NodeManager@*.*:5555> <Starting Server orbitPortalDomain::orbit_ManagedServer1 ...>
    <Dec 7, 2004 4:52:16 PM IST> <Info> <NodeManager@*.*:5555> <Server orbitPortalDomain::orbit_ManagedServer1 started, process id = 1,832>
    <Dec 7, 2004 4:52:17 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_04-b05 from Sun Microsystems Inc.>
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://10.6.0.212:7001 to check if there exists a running admin server at this URL.>
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://10.6.0.212:7001 to retrieve the initial configuration.>
    <Dec 7, 2004 4:52:21 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file D:\bea_turner\weblogic81\common\nodemanager\orbit_ManagedServer1\orbit_ManagedServer1.log is opened. All server side log events will be written to this file.>
    The WebLogic Server did not start up properly.
    java.lang.NoClassDefFoundError: com/bea/wsrp/util/debug/Debug
    at com.bea.wsrp.security.WSRPIdentityAsserterProviderImpl.<clinit>(WSRPIdentityAsserterProviderImpl.java:45)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
    at java.lang.Class.newInstance0(Class.java:308)
    at java.lang.Class.newInstance(Class.java:261)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.createSecurityProvider(SecurityServiceManagerDelegateImpl.java:232)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:939)
    at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
    at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:257)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManagerDelegateImpl.java:581)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegateImpl.java:420)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.java:698)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelegateImpl.java:731)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl.java:874)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:717)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:822)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
    at weblogic.Server.main(Server.java:32)
    Reason: com/bea/wsrp/util/debug/Debug
    pls advice
    Thanks
    Sasanka

    Hello,
    There is a lot of stuff on this thread:
    http://forum.java.sun.com/thread.jspa?threadID=567363&messageID=2801617
    these guys are trying to run weblogic with JBuilder.
    Looks like your classpath is incorrect, can you go to your admin console-->server-->remote start
    copy the classpath and post it here.
    Check for spaces in your classpath, missing jars or directories and miss spelt paths.
    Has this problem been occuring as soon as you installed WLP or not?
    Cheers,
    Hoos

  • Errors & warnings when using the Admin Server Console - Help Needed

    hi,
    i just installed weblogic 12c and created a new domain which contains an adminServer and managedServer under
    one cluster.
    after finishing the installation, i started the Admin Server and afterwards started the admin server console.
    and i got the next warning and errors.
    the warning look like this:
    <20:00:35 IST 23/03/2012> <Warning> <Munger> <BEA-2156203> <A version attribute
    was not found in element "web-app" in the deployment descriptor C:\Oracle\Middle
    ware\user_projects\domains\base_domain\servers\AdminServer\tmp\_WL_internal\cons
    oleapp\jxhze9\console-ext\sipserver-console-ext\WEB-INF\web.xml. A version attri
    bute is required, but this version of the WebLogic Server will assume that the l
    atest version is used. Future versions of WebLogic Server will reject descriptor
    s that do not specify the Java EE version. To eliminate this warning, add an app
    ropriate "version=" to element "web-app" in the deployment descriptor.>
    the errors look like this:
    <20:01:51 IST 23/03/2012> <Error> <netuix> <BEA-423158> <No content found at con
    tentUri = /PortalConfig/security/providers/AuthenticatorConfigCommon.portlet.>
    what is the problem? anyone knows?

    If you want to have an weblogic environment with one domain having server spread across different physical machines , then you will have to perform the installations of the weblogic server separately on all the machines . Also make sure that the version of the Weblogic server you are installing is same across the machines and the directory structure is also exactly same.
    In short you will have to perform the below steps :
    1 : install the weblogic server on all the machines with exactly same version and same dir structure .
    2 : Create domain on MachineA providing all the details of the Managed Server and different machine hostnames.
    3 : Start the Admin Server on machineA and then shut down it.
    4 : execute the WLST pack command on MachineA creating a domain template JAR file.
    5 : copy the create jar file on all the Machines ( B , C , D ) you have to distribute your domain.
    6 : Execute the WLST unpack command on all the machines ( B , C , D ) .
    7 : Execute the WLST nmEnroll () command on all the machines ( B, C , D ).
    8 : Start the Managed Servers on all the machines ( B , C , D )

  • Administrator Login & Issue with Weblogic Admin Server Console

    I recently applied a PeopleTools patch to a test environment. I will be doing this to production soon, and as I was going through my screenshots of what I did in test, I ran across an area that may cause me an issue when I apply it to production.
    There is a screen which prompts you for the administrator login and password for the weblogic domain. I wasn't sure of this when I did it in test, but in the PeopleTools install doc, it said the default is system/Passw0rd
    This worked fine in test. However, the person who set this up in production may have used a different password. I don't want to get halfway through the patch and have to abort because I don't know the password.
    I did some research and read there was a file with this info. I think it was boot.properties, but it was encrypted.
    I then started the Weblogic Admin Server Console in test and was able to login with system/Passsw0rd so that verified a way of confirming the password in test.
    I tried to do the same in production, but the Weblogic Admin Server Console page does not come up. The webserver is running, and if it wasn't, my phone would be ringing. Why does the console not come up?
    However, the screen that comes up during the patch that prompts you for this asks you to enter your password, and re-enter it on the next line, so maybe its setting the password, not verifying that you know it. Is this true, I could make it whatever I want?
    The WebLogicAdmin_weblogic.log file has not been updated in months. This may have been when we did the last upgrade.
    Can you tell me how to determine/verify this password?
    Thanks,
    Roger

    I'm not sure if there's an easy way to verify this. If I'm not mistaken you'll have batch file called startweblogicadmin.bat in the bin directory. You have to start this to get the administrator console running. It will be running on port :9999 by default if you haven't changed this.

  • Admin Server Console is not working

    Hi,
    I have installed weblogic server 9.2 wirh SIP server on win2k the created domain successfully. With "Admin Server Console", I can not do anything because I get following errors;
    It seems XML to HTML transform is not working? Any help is appreciated.
    "The template you provided at /WEB-INF/templates/form.xml could not be processed"
    "ERROR: 'Instruction unknown: loadinstruction'
    FATAL ERROR: 'Could not compile stylesheet'

    You are getting below exception when trying to start Weblogic Server or while accessing the Weblogic console URL?
    - - Weblogic Consultant

  • Cannot access weblogic admin server console

    All,
    I am not able to access https://<myhostname>:7001/console URL after sucessfull installation of web logic server on linux. During installation I also created base_domain.
    Here is the log during the AdminServer startup :-
    <Oct 4, 2009 9:02:02 AM PDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Oct 4, 2009 9:02:02 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Oct 4, 2009 9:02:02 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:20c:29ff:fe28:8f5b:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.119.129:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Production Mode>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Oct 4, 2009 9:02:03 AM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    From the above it looks like there was no issue in starting up the admin server. But when I try to access the weblogic admin server url, it does not show up.
    Can you please help me to resolve the issue if any so that I can access the admin console?
    THanks,
    Amit

    hey, same here...
    this is what i get when starting up the console
    <May 4, 2010 12:52:51 PM WIT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on xxx.xxx.xxx.xxx:7777 for protocols iiop, t3, ldap, snmp, http.>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7777 for protocols iiop, t3, ldap, snmp, http.>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "xxxxxDomain" running in Production Mode>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <May 4, 2010 12:52:51 PM WIT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    but when i go to the browser
    http://xx.xx.xx.xx:7777/console..
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    xx.xx.xx 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.
    i still try to fix this..

  • Admin Server console not showing Managed Server is running

    I am using WLS 7.0.1.0 SP1 runing on Windows 2000. I have setup a node manager, Admin server and Managed Server as Windows Services. Admin Server has -delaySeconds as 2min. Manager Server(MS) has been made to depend on Admin Server start. When I boot my machine, all the three services come up properly. I can access my application which is running on MS properly. But for some reason the Admin Console doesn't show the MS as running. If I use the Admin Console now to start up MS all it does it "Reconnects to the admin server" since the MS is in started state. What is the reason for this

    It could be the ordering dependency and the rediscovery of the MS by the AS.
    An AS has a notion of where MS's live on disk and it could be an issue with
    AS bouncing in between MS's constant state of upness.
    Cheers
    mbg
    "Ajay Kulkarni" <[email protected]> wrote in message
    news:3ede0306$[email protected]..
    I am using WLS 7.0.1.0 SP1 runing on Windows 2000. I have setup a nodemanager, Admin server and Managed Server as Windows Services. Admin Server
    has -delaySeconds as 2min. Manager Server(MS) has been made to depend on
    Admin Server start. When I boot my machine, all the three services come up
    properly. I can access my application which is running on MS properly. But
    for some reason the Admin Console doesn't show the MS as running. If I use
    the Admin Console now to start up MS all it does it "Reconnects to the admin
    server" since the MS is in started state. What is the reason for this

  • Problem starting Admin server console

    hi guys,
    i have problem starting my console server. The error msg is
    " cannot connect to admin server http://simple.cwmgroup.org:390. The URL is not correct or server is not running."
    i had earlier used :
    /usr/sbin/ directoryserver start command to start directory server and
    /usr/sbin/mpsadmserver start to start the admin server and finally tried
    usr/sbin/mpsadmserver startconsole and it seems not to be working (but used to).
    And i 'm very sure the url is correct and the server is also running b/c i v been using the comand successfully b/4.
    guys what can i do to get it working? can anyone hlp?

    If you want to check your DS5.2 configuration, using command line.
    # ./saveconfig
    saving configuration ...
    ldiffile: /var/Sun/mps/slapd-ldap1/confbak/2005_07_29_003704.ldif
    [29/Jul/2005:00:37:07 -0400] - export NetscapeRoot: Processed 100 entries (100%).
    # grep Port /var/Sun/mps/slapd-ldap1/confbak/2005_07_29_003704.ldif
    nsServerPort: 389
    nsSecureServerPort: 636
    nsServerPort: 390
    (The 2nd nsServerPort is admin port at 390)
    Gary

  • Admin server console Certificate

    Hi everyone
    I try to change the default certificate in the web server 7.0 u5 console but i don't find any doc or steps to make this.
    it's possible change the web console certificate ?
    Best Regards!

    admin server by default creates and installs self signed certificate. we do not expose changing this default certificate with your own certificate. having said that, it is however possible to install your own certificate by using the command line tools installed as part of our product.
    however, we would like to understand more on the reason to install your own certificate

  • WebLogic Admin Server Console: Is it secure?

    Hello,
    I've attended both WebLogic classes (Basic and Advanced) and have never heard my instructor state that the Admin console is unsecure as opposed to WLST. I asked spcifically durin the Advanced class about this and was told all that was needed was to change the console name and port.
    Another indiviudal who attended the first class with a different instructor told me his told him the console was not secure because everybody would have access to the console and could make changes, and that a lot of companies were not using it according to blogs.
    The problem is he is telling a lot of people this, when I don't believe it.
    Whose right?
    Thanks

    Hi,
    You are right. You need to provide a user name and a password to access the Console so it is secure.
    Default SSL is not used so some might argue the it is not secure since user name and password is send in clear text and can be sniffed. But in most situation the Weblogic installation are placed in a special network segment with a DMZ in front of it so I don't see the need for using SSL. But if needed you can just enable SSL for the Console and then it is more secure.
    Also using the default port is fine since you have to provide a user name and password. On production systems I tend to not use weblogic as the default administrator user name. Then a hacker has to not only guss the password but also the user name.
    Regards Peter Lorenzen
    Edited by: Peter Lorenzen on Jun 21, 2011 4:17 AM

  • Deploying applications on the Admin Server

    Hi there
    I have recently moved to a new project team who have been deploying their applications to the admin server. They have been doing this for years with no issues.
    I was always led to believe that the best practice was to keep the admin server completely separate. And I always deployed to a managed server (or a cluster of servers).
    Does anyone know of any specific reasons why applications should not be deployed to an admin server.
    Thanks in advance.

    Typically, you want your managed servers to focus on applications, and the admin server to focus on management of the servers. If you have your heavy load applications deployed to the admin server, then that impacts both your applications and the management of those applications.
    If your applications are deployed to the managed server, and not the admin server, you can recycle applications remotely just through the admin server console. If you need to restart the application, and it's running on the admin server, then you'll have to take additional steps to get the server running again.

  • How to configure ftpadapter JNDI in server Console for oracle soa suite 11g

    Hi All,
    I need to configure a ftp adapter in one of my bpel process. Could any one guide me pleas ,how to do FTP adapter jndi configure in admin server console?
    Thank you.
    Regards,
    Satish

    http://www.oracle.com/technology/architect/soa-suite-series/dynamic_endpoints.html
    Configuring the End Point Properties for an Adapter through Oracle Enterprise Manager
    does that help ?

  • Cloned OMS - WebLogic Admin Server not available....

    Greetings,
    We are working our way through an active active R4 OMS setup, and we just successfully cloned oms1 to oms2 via cloud control, and executed the post install steps. We now need to access each of the OMSs WebLogic Admin Server Console to confirm LDAP settings, and the oms2 WebLogic Admin Server Console is unavailable. The oms2 clone has the same WebLogic Admin Server details as oms1 (see below).
    Is that by design, i.e. only one WebLogic Admin Server Console with two load balanced OMSs?
    Which files do we need to edit on oms2 to get oms2's WebLogic Admin Server on-line?
    oms1:
    /u01/app/oracle/product/middleware_r4/oms/bin/emctl status oms -details
    WLS Domain Information
    Domain Name            : GCDomain
    Admin Server Host      : oms1.mastec.com
    Admin Server HTTPS Port: 7102
    Admin Server is RUNNING
    oms2:
    WLS Domain Information
    Domain Name            : GCDomain
    Admin Server Host      : oms1.mastec.com
    Admin Server HTTPS Port: 7102
    Thank you,

    The WLS admin server only exists on the first OMS host. Usually an SLB is used for load balancing.
    For information on HA (High Availability) solutions, see:
    http://docs.oracle.com/cd/E24628_01/install.121/e24089/ha_intro.htm#EMADV9611
    Regards,
    - Loc

  • JES 2005Q4 Administration Server Console Problem

    Hello, I have installed JES on Sol 10x86.
    I've used /usr/sbin/mpsadmserver configure to configure the Admin Server Console.
    I used the default user;admin
    I used a password that I know,
    I used the default port of 390.
    when I type /usr/sbin/mpsconsole I put in
    user id admin
    password ********
    http://fqdn:390
    It comes back with the error message
    "Cannot login because of an incorrect User ID, incorrect password or directory problem. java.io.interuptedIOException:Http Responce Time Out"
    I've used /usr/sbin/mpsadmserver unconfig to remove and reinstall it and still nothing.
    Thanks in advance for the help.

    I thought the proper order of doing things are:
    download sw image
    unpack.
    read release notes and install guide
    acertain install sw/hw requirements
    install required SW component, I think JDK/JRE 1.4.2 or later needed
    install required OS/kernel/LDAP/JES patches
    When encountering error...
    read the error and/or access log file
    read the install log file, usually somewhere, may be in /tmp or /var/sadm/...
    turn on debugging mode of installer, if there is, someting like:
    # ./installer -d
    or
    # ./setup -d
    The above is compressed archive install, I tried to avoid pkg install as pkg method seems more problematic, I may be wrong.
    If you use the compressed archive method, then at the end of the successful run of "installer", simply:
    # ./startconsole
    instead of running "mpsconsole"
    Gary

  • Console cannot connect to Admin Server in a local network

    Hi,
    This issue may has been asked before, but I didn't find corresponding answer. So I ask again:
    The Directory server 5.2 P4 is running on Windows XP and a console running on the same server (192.168.1.80) works fine. However second console which is running on 192.168.1.50 can not connect to admin server. Error message is:
    Cannot connect to the Admin Server "http://homeserver.keiban.com:5201/" The URL is not correct or the server is not running.
    I noticed that if I use http://192.168.1.80:5201 to connect admin server instead of http://homeserver.keiban.com, it took 10 seconds to show Initialization Failure:
    Connect connect to the Directory Server "ldap://homeserver.keiban.com:5200" LDAP error: failed to connect to server ldap://homeserver.keiban.com;5200 Would you like to attemt to restart the Directory Server?
    In Control Panel -> Windwos Firewall -> Exceptions, I have added port number 5201 for Sun ONe Admin Server 5.2 on TCP.
    In etc/host file, an entry is already added:
    192.168.1.80 homeserver.keiban.com homeserver
    Both computers are in a local network and via cable DSL to connect to Internet. Is there some thing I am missing?
    Your help will be appreciated,

    1. Make sure your FQDN is set up correct on both
    client and Server.Victor, you are right! I setup FQDN on server properly, but forgot to have FQDN setup to map FQDN to IP address on client. So the Console goes to Internet to find the directory server in which it causes failure.
    Thanks your hint,
    a. ping xxx.xxx.xxx.xxx from client to Server
    Check the Admin Server for Client Access Control
    configuration.
    Victor

Maybe you are looking for