WebLogic installation Complete, console cannot log on one of the reasons

Case: WebLogic installation is not a problem, when entering the console input is: http: machine Name: 7001/console this time into the WebLogic console, the problem is no matter how to enter the user name and password can not log in. It is strange that shutting down the firewall is useless and the console has no error prompts.

Console output:

.. JAVA Memory arguments:-xms256m-xmx512m-xx:compilethreshold=8000-xx:permsize=48m-xx:maxpermsize=128m. WLS Start mode=development.classpath=c:\oracle\middle~1\patch_wls1032\profiles\default\sys_manifest_classpath\ Weblogic_patch.jar; C:\oracle\middle~1\jdk160~1.5-3\lib\tools.jar; C:\oracle\middle~1\utils\config\10.3\config-launch.jar; C:\oracle\middle~1\wlserv~1.3\serverlib\weblogic_sp.jar; C:\oracle\middle~1\wlserv~1.3\server\lib\weblogic.jar; C:\oracle\middle~1\modules\features\weblogic.server.modules_10.3.2.0.jar; C:\oracle\middle~1\wlserv~1.3\server\lib\webservices.jar; C:\oracle\middle~1\modules\orgapa~1.0/lib/ant-all.jar; C:\oracle\middle~1\modules\netsfa~1.0_1/lib/ant-contrib.jar; C:\oracle\middle~1\wlserv~1.3\common\eval\pointbase\lib\pbclient57.jar; C:\oracle\middle~1\wlserv~1.3\server\lib\xqrl.jar.path=c:\oracle\middle~1\patch_wls1032\profiles\default\ Native c:\oracle\middle~1\wlserv~1.3\server\native\win\32; C:\oracle\middle~1\wlserv~1.3\server\bin; C:\oracle\middle~1\modules\orgapa~1.0\bin; C:\oracle\middle~1\jdk160~1.5-3\jre\bin; C:\oracle\middle~1\jdk160~1.5-3\bin;d:\app\ning_zhang\product\11.1.0\db_1\bin; C:\Windows\system32; C:\Windows; C:\Windows\System32\Wbem; C:\Windows\System32\WindowsPowerShell\v1.0\; C:\Program Files\amd\ati. ace\core-static; C:\Program Files\java\jdk1.6.0_02\bin; C:\Program Files\java\jdk1.6.0_02\jre\bin;%catalina_home%\lib;%catalina_home%\bin; C:\Program Files\arcgis\arcsde\ora11gexe\bin; c:\oracle\middle~1\wlserv~1.3\server\native\win\32\oci920_8.**************************************************  * * To-start WebLogic Server, use a username and * * Password assigned to an Admin-level user. for * * Server administration, use the WebLogic server * * Console at Http:\\hostname:port\console **************** Starting WebLogic with Java Version:java version "1.6.0_14" Java (TM) SE Runtime Environment (build 1.6.0_14-b08) Java HotSpot (TM) Client VM (build 14.0-b16, Mixed mode) starting WLS with Line:c:\oracle\miDdle~1\jdk160~1.5-3\bin\java-client-xms256m-xmx512m-xx:compilethreshold=8000-xx:permsize=48m-xx:maxpermsize=  128m-dweblogic.name=adminserver-djava.security.policy=c:\oracle\middle~1\wlserv~1.3\server\lib\weblogic.policy -xverify:none-da-dplatform.home=c:\oracle\middle~1\wlserv~1.3-dwls.home=c:\oracle\middle~1\wlserv~1.3\server- dweblogic.home=c:\oracle\middle~1\wlserv~1.3\server-dweblogic.management.discover=true-dwlw.iterativedev=- dwlw.testconsole=-dwlw.logerrorstoconsole=-dweblogic.ext.dirs=c:\oracle\middle~1\patch_wls1032\profiles\ Default\sysext_manifest_classpath WebLogic. Server<2015-1-15 02:32 P.M. 31 sec cst> <Info> <WebLogicServer> <BEA-000377> <startingweblogic Server with Java HotSpot (TM) Client VMs Version 14.0-b16 from Sun Microsystems inc.><2015-1-15 02:32 P.M. 31 sec. cst> &L t;info> <Management> <BEA-141107> <version:weblogic Server 10.3.2.0 Tue Oct 12:16:15 PDT 2009 12679 ><2015-1-15 02:32 P.M. 32 seccst> <Notice> <WebLogicServer> <BEA-000365> <serverstate changed to Starting><2015-1-15 02:32 P.M. 32 sec cst> <Info> <WorkManager> <BEA-002900> <initializing self-tuning thread pool> <2015-1-15 02:32 P.M. 32 sec cst> <Notice> <LoggingService> <BEA-320400> <the log file C:\Oracle\ Middleware\user_projects\domains\weblogic\servers\adminserver\logs\adminserver.log'll be rotated. Reopen The log file if tailing has stopped. This can happen in some platforms like Windows.><2015-1-15 02:32 P.M. 32 sec cst> <Notice> <loggingservice&gt ; <BEA-320401> <the log file have been rotated to C:\Oracle\Middleware\user_projects\domains\weblogic\servers\ adminserver\logs\adminserver.log00009. Log messages'll continue to being logged in C:\Oracle\Middleware\user_projects\domains\weblogic\servers\AdminServerlogs \adminserver.log.><2015-1-15 02:32 P.M. 32 sec cst> <Notice> <log management> &LT;BEA-170019&GT <the Server log File C:\Oracle\Middleware\user_projects\domains\weblogic\servers\AdminServer\logs\ AdminServer.log is opened. All server side log events is Writtento this file.><2015-1-15 02:32 P.M. 34 seconds cst> <Notice> &LT;SECURITY&G T <BEA-090082> <security initializing using Security realm myrealm.><2015-1-15 02:32 P.M. 35 seconds cst> < Notice> <WebLogicServer> <BEA-000365> <serverstate changed to standby><2015-1-15 02:32 P.M. 35 sec cst> <Notice> <WebLogicServer> <BEA-000365> <serverstate changed to Starting><2015-1-15 02:32 P.M. 35 sec cst> <Notice> <LoggingService> <BEA-320400> <the log file C:\Oracle\Middleware\ User_projects\domains\weblogic\servers\adminserver\logs\weblogic.log'll be rotated. Reopen The log file if tailing has stopped. This can happen in some platforms like Windows.><2015-1-15 02:32 P.M. 35 sec cst> <Notice> <loggingservice&gt ; <BEA-320401> <thE log file has been rotated to C:\Oracle\Middleware\user_projects\domains\weblogic\servers\AdminServer\logs\ weblogic.log00009. Log messages'll continue to being logged in C:\Oracle\Middleware\user_projects\domains\weblogic\ Servers\adminserver\logs\weblogic.log.><2015-1-15 02:32 P.M. 35 sec cst> <Notice> <log management> <BEA-170027> <the Server have established connection with the Domain level Diagnostic Service successfully.>&lt ; 2015-1-15 02:32 P.M. 36 sec cst> <Notice> <WebLogicServer> <BEA-000365> <serverstate changed to Admin><2015-1-15 02:32 P.M. 36 sec cst> <Notice> <WebLogicServer> <BEA-000365> <serverstate Changed to resuming><2015-1-15 02:32 P.M. 36 sec cst> <Warning> <Server> <BEA-002611> < Hostname "Ning_zhang. Hold. Founder.com ", maps to multiple IP addresses:172.18.124.179, fe80:0:0:0:7a:c668:fd79:989c%11><2015-1-15 02:32 P.M. 36 sec cst> <Notice> <Server> <bea-002613> <channel "Default" is now listening on 172.18.124.179:7001 for protocols IIOP, T3, LDAP, SNMP, http.><2015-1 -15 02:32 P.M. 36 sec cst> <Notice> <Server> <BEA-002613> <channel "Default[3" "is now listening on FE80 : 0:0:0:0:5efe:ac12:7cb3:7001 for Protocols IIOP, T3, LDAP, SNMP, http.><2015-1-15 02:32 P.M. 36 sec cst> <notice& Gt <Server> <BEA-002613> <channel "default[2]" is now listening on fe80:0:0:0:7a:c668:fd79:989c:7001 for Protocols Iiop,t3, LDAP, SNMP, http.><2015-1-15 02:32 P.M. 36 sec cst> <Notice> <Server> <bea-002613& Gt <channel "Default[4]" is now listening on fe80:0:0:0:9080:59e2:d326:1a7:7001 for protocols IIOP, T3, LDAP, SNMP, http.& Gt;<2015-1-15 02:32 P.M. 36 sec cst> <Notice> <Server> <BEA-002613> <channel "default[6]" is now Listening on 127.0.0.1:7001 for protocols IIOP, T3, LDAP, SNMP, http.><2015-1-15 02:32 P.M. 36 sec cst> <Notice> <Server> &LT;BEA-002613&GT <channel "Default[5]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols IIOP, T3, LDAP, SNMP, http.><2015-1- 15 02:32 P.M. 36 sec cst> <Notice> <Server> <BEA-002613> <channel "Default[1" "is now listening on 172.1 8.114.121:7001 for Protocols Iiop, T3, LDAP, SNMP, http.><2015-1-15 02:32 P.M. 36 sec cst> <Notice> <weblogic  server> <BEA-000331> <started WebLogic Admin Server "adminserver" for Domain "WebLogic" running in development Mode><2015-1-15 02:32 P.M. 36 sec cst> <Notice> <WebLogicServer> <BEA-000365> <serverstate Changed to running><2015-1-15 02:32 P.M. 36 sec cst> <Notice> <WebLogicServer> <BEA-000360> < serverstarted in RUNNING mode>2015-1-15 14:32:42 com.sun.faces.config.ConfigureListener contextinitialized Info: Initializing Sun ' s JavaServer Faces Implementation (1.2_03-B04-FCS) for context '/console ' 2015-1-15 14:32:42 Com.sun.faces.config.ConfigureListener ContextinitializEd Info: Completed initializing Sun ' s JavaServer Faces Implementation (1.2_03-B04-FCS) for context '/console ' 

After testing: The URL address of the machine name, modified to localhost or 127.0.0.1 OK for the specific reasons have not yet found out what the reason, if you know friends also please leave a message thank you!

WebLogic installation Complete, console cannot log on one of the reasons