Cann't connect to Administrator Port of OAS 4.0.7

Hi,everyone
My web server 4.0.7 runs on Solaris 2.5.1 and Oracle 7.3.4. The connection to normal ports (etc.,80) is successful but to administrator port(etc., 8088) is failed. The message for command OWSSTAT shows normal. Please give me your idea.
Best.

Similar Messages

EAS server error: Could not connect to administration Server

Hi,
I have installed Hyperion suite in Windows server 2008 R2. It was working fine but now when i tried to login in to the EAS console, I am getting the following error:
"Server Error: Could not connect to administration server".
I tried accessing the same through the web URL and I found "404 error - file or directory not found".
I verified all my services are up and running fine. I am able to connect to the essbase sever through Excel as well as planning.
The log retireved from the HyS9eas-sysout.log file is below:
<Sep 11, 2013 7:06:56 AM JST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Sep 11, 2013 7:06:57 AM JST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Sep 11, 2013 7:06:58 AM JST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.2-11-135406-1.6.0_20-20100624-2119-windows-x86_64 from Oracle Corporation>
<Sep 11, 2013 7:07:04 AM JST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<Sep 11, 2013 7:07:15 AM JST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://localhost:7001.>
<Sep 11, 2013 7:07:15 AM JST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Sep 11, 2013 7:07:15 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Sep 11, 2013 7:07:15 AM JST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Sep 11, 2013 7:07:16 AM JST> <Notice> <LoggingService> <BEA-320400> <The log file E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Sep 11, 2013 7:07:16 AM JST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log00410. Log messages will continue to be logged in E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log.>
<Sep 11, 2013 7:07:16 AM JST> <Notice> <Log Management> <BEA-170019> <The server log file E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log is opened. All server side log events will be written to this file.>
<Sep 11, 2013 7:07:48 AM JST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Sep 11, 2013 7:07:56 AM JST> <Warning> <JTA> <BEA-110503> <The migrator(the AdminServer for manual JTA migration policy, or the Singleton Master for automatic JTA migration policy) is not available. Will skip JTA TRS failback because isStrictOwnershipCheck is [false]. This may lead to potencial TLOG corruption if TRS of EssbaseAdminServices0 has been migrated to backup server and the backup server is accessing the TLOG of EssbaseAdminServices0. More safety can be achieved by setting isStrictOwnershipCheck to [true].>
<Sep 11, 2013 7:08:35 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Sep 11, 2013 7:08:35 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getDomainConfiguration()
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getRuntimeService()
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
return com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean
return com.bea:Name=EPMSystem,Type=Domain
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Domain location is 'E:\Oracle\Middleware\user_projects\domains\EPMSystem'
Calling getRuntimeService()
return com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Checking E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\registry_update.xml file
EPM_ORACLE_HOME: E:\Oracle\Middleware\EPMSystem11R1
Template for EAS#11.1.2.0: E:\Oracle\Middleware\EPMSystem11R1\common\templates\applications\epm_eas_11.1.2.1.jar
Dependencies for E:\Oracle\Middleware\EPMSystem11R1\common\templates\applications\epm_eas_11.1.2.1.jar: [Oracle EPM Common, Oracle EPM Calcmgr, Oracle EPM Planning libraries, Oracle EPM EAS libraries, Oracle EPM Misc libraries, Oracle EPM Xerces libraries]
BPMUI shared webapp not referenced from EAS#11.1.2.0
Application name: EAS#11.1.2.0
Application source: eas.ear
Server name: EssbaseAdminServices0
Server port: 10080
Server SSL port: 10083
Application context: eas
Registry product type: ESSBASE_PRODUCT
Registry physical web application type: ADMIN_SERVICES_WEB_APP
weblogic.Name property is 'EssbaseAdminServices0', seems to be WebLogic mode
registry.isRegistryDatabaseCreated()true
Registry was initialized sucessfully
Executing pre custom update for EAS#11.1.2.0
EPM_ORACLE_INSTANCE: E:\Oracle\Middleware\user_projects\epmsystem1
<Sep 11, 2013 7:09:06 AM JST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'EAS [Version=11.1.2.0]' due to error java.lang.NullPointerException.
java.lang.NullPointerException
at java.io.File.<init>(File.java:222)
at com.hyperion.hit.tool.deploy.update.util.RegistryHelper.createPhysicalWebApp(RegistryHelper.java:168)
at com.hyperion.hit.tool.deploy.update.RegistryUpdater.update(RegistryUpdater.java:36)
at com.hyperion.hit.tool.deploy.update.RegistryUpdateListener.preStart(RegistryUpdateListener.java:91)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NullPointerException
at java.io.File.<init>(File.java:222)
at com.hyperion.hit.tool.deploy.update.util.RegistryHelper.createPhysicalWebApp(RegistryHelper.java:168)
at com.hyperion.hit.tool.deploy.update.RegistryUpdater.update(RegistryUpdater.java:36)
at com.hyperion.hit.tool.deploy.update.RegistryUpdateListener.preStart(RegistryUpdateListener.java:91)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
Truncated. see log file for complete stacktrace
>
<Sep 11, 2013 7:09:06 AM JST> <Emergency> <Deployer> <BEA-149259> <Server 'EssbaseAdminServices0' in cluster 'EssbaseAdminServices' is being brought up in administration state due to failed deployments.>
<Sep 11, 2013 7:09:17 AM JST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Sep 11, 2013 7:09:17 AM JST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of EssbaseAdminServices.>
<Sep 11, 2013 7:09:22 AM JST> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file E:\Oracle\Middleware\jrockit_160_20\jre\lib\security\cacerts.>
<Sep 11, 2013 7:09:48 AM JST> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: Sun RSA public key, 512 bits
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Fri Mar 22 05:12:27 JST 2002,
               To: Wed Mar 23 05:12:27 JST 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [    33f10648 fcde0deb 4199921f d64537f4]
Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Algorithm: [MD5withRSA]
Signature:
0000: 9D 26 4C 29 C8 91 C3 A7   06 C3 24 6F AE B4 F8 82 .&L)......$o....
0010: 80 4D AA CB 7C 79 46 84   81 C4 66 95 F4 1E D8 C4 .M...yF...f.....
0020: E9 B7 D9 7C E2 23 33 A4   B7 21 E0 AA 54 2B 4A FF .....#3..!..T+J.
0030: CB 21 20 88 81 21 DB AC   90 54 D8 7D 79 63 23 3C .! ..!...T..yc#<
] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[6]" is now listening on 127.0.0.1:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[6]" is now listening on 127.0.0.1:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[7]" is now listening on 0:0:0:0:0:0:0:1:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[7]" is now listening on 0:0:0:0:0:0:0:1:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:0:5efe:a0e:daee:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 10.14.126.11:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[5]" is now listening on fe80:0:0:0:0:5efe:a0e:224b:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[3]" is now listening on fe80:0:0:0:0:5efe:a0e:daee:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[1]" is now listening on 10.14.126.11:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on fe80:0:0:0:0:5efe:a0e:224b:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 10.14.34.75:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[4]" is now listening on fe80:0:0:0:0:5efe:a0e:7e0b:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 10.14.218.238:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.14.218.238:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[2]" is now listening on 10.14.34.75:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:0:5efe:a0e:7e0b:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <WebLogicServer> <BEA-000358> <Started WebLogic Independent Managed Server "EssbaseAdminServices0" for domain "EPMSystem" running in Production Mode>
<Sep 11, 2013 7:09:48 AM JST> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
<Sep 11, 2013 7:09:48 AM JST> <Warning> <Server> <BEA-002611> <Hostname "SJ015040", maps to multiple IP addresses: 10.14.126.11, 10.14.34.75, 10.14.218.238, 0:0:0:0:0:0:0:1>
<Sep 11, 2013 7:09:53 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Sep 11, 2013 7:09:53 AM JST> <Notice> <WebLogicServer> <BEA-000360> <Server started in ADMIN mode>
HyS9eas-syserr.log is empty and I dont find anyother details from the other log files.
Kindly help me out in solving this issue.
Thanks in advance.
Regards,
Balaji P

Hi John,
Sorry for replying late.
I ran the EPM diagnostic and found EAS & APS application are failed. So as you mentioned, i tried re-deployment through EPM configurator.
But Re-configuration fails with error "An unexpected error occurred and the application will have to shut down" .
When i looked in to the Config tool.log,I got the following messages.
[2013-09-17T18:17:04.635+09:00] [EPMCFG] [TRACE] [EPMCFG-01001] [oracle.EPMCFG] [tid: 17] [ecid: 0000K4fDMY^0zkgpxC^AyW1IE1pJ000003,0:325] [SRC_CLASS: com.hyperion.hit.tool.deploy.utils.UIPortUtil] trace: Parsing server FinancialReporting0 on port 8200 from registry
[2013-09-17T18:17:04.827+09:00] [EPMINS] [ERROR] [EPMINS-00001] [oracle.EPMINS] [tid: 17] [ecid: 0000K4fDMY^0zkgpxC^AyW1IE1pJ000003,0:325] [SRC_CLASS: com.hyperion.hit.wizard.Wizard] trace: Unexpected error:[[
java.lang.NullPointerException
at com.hyperion.hit.tool.deploy.utils.UIPortUtil.<init>(UIPortUtil.java:83)
at com.hyperion.hit.tool.deploy.utils.UIPortUtil.getInstance(UIPortUtil.java:53)
at com.hyperion.config.wizard.DeploymentField.getAppServerDeploymentData(DeploymentField.java:235)
at com.hyperion.config.wizard.DeploymentField.<init>(DeploymentField.java:56)
at com.hyperion.config.wizard.impl.DeploymentForm.<init>(DeploymentForm.java:57)
at com.hyperion.config.wizard.impl.DeploymentState.initializeBeforeShowOnNext(DeploymentState.java:56)
at com.hyperion.hit.wizard.Wizard$NextClass.run(Wizard.java:522)
at java.lang.Thread.run(Thread.java:619)
Since it is similare to the Oracle konwledge base article - (Doc ID 1570293.1), I tried adding the shared service domain to the Windows host file. But i am still recieveing the same error message as above.
Appreciates your help.
Thanks & Regards,
Balaji P

Administration port - network channel for admin traffic

I am trying to configure a separate channel for Administration traffic on weblogic. I followed the oracle docos and configured the SSL, domain wide admin port, server listen address, ‘admin’ channel.
The issue is admin traffic in not happening through the newly created channel.
L2 network is not getting used. I can’t see any activity in the monitoring tab of new Channel. Also the netstat is showing that the port 9101/9102 is getting used on the 192.168.100.218 and not on 10.254.252.849.
I also tried by setting up the newly created channel weight as 51, but no luck.
Is JMX connectivity related to admin channel?
Any help is highly appreciated. Thanks.
Ipconfig:
Admin: adminserver701.mycompany.internal, 192.168.100.238, 10.254.252.808
Managed: appserver701.mycompany.internal, :192.168.100.218, 10.254.252.849
Domain wide admin port: 9101
Admin:
Listen address –> adminserver701.mycompany.internal
Channel –> admin -> 10.254.252.808/9101
Startup -> -Dweblogic.admin.ListenAddress=admin://10.254.252.808:9101
Managed:(appserver701)
Listen address –> appserver701.mycompany.internal
Admin port override: 9102
Channel –> admin -> 10.254.252.849/9102
Startup -> -Dweblogic.admin.ListenAddress=admin://10.254.252.849:9102
AdminServer Logs:
####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613346> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.runtime .>
####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613353> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.edit .>
####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613367> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.domainruntime .>
####<Feb 18, 2013 1:53:36 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159616699> <BEA-002613> <Channel "DefaultAdministration" is now listening on 192.168.100.238:9101 for protocols admin, ldaps, https.>
####<Feb 18, 2013 1:53:36 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159616700> <BEA-002613> <Channel "Channel-0" is now listening on 10.254.252.808:9101 for protocols admin, ldaps, https.>
####<Feb 18, 2013 1:55:12 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-000000000000001a> <1361159712920> <BEA-002613> <Channel "Default" is now listening on 192.168.100.238:7001 for protocols iiop, t3, ldap, snmp, http.>
####<Feb 18, 2013 1:55:12 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-000000000000001a> <1361159712920> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.100.238:7002 for protocols iiops, t3s, ldaps, https.>
ManagedServer Logs:
####<Feb 18, 2013 2:54:19 PM EST> <Info> <JMX> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163259911> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://appserver701.mycompany.internal:9102/jndi/weblogic.management.mbeanservers.runtime .>
####<Feb 18, 2013 2:54:20 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163260350> <BEA-002613> <Channel "Channel-0" is now listening on 10.254.252.849:9102 for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
####<Feb 18, 2013 2:54:20 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163260350> <BEA-002613> <Channel "DefaultAdministration" is now listening on 192.168.100.218:9102 for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
####<Feb 18, 2013 2:54:58 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <d3208ed6c2482016:-46ac5fed:13ceba69a8e:-7ffe-000000000000000e> <1361163298045> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.100.218:7102 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
####<Feb 18, 2013 2:54:58 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <d3208ed6c2482016:-46ac5fed:13ceba69a8e:-7ffe-000000000000000e> <1361163298045> <BEA-002613> <Channel "Default" is now listening on 192.168.100.218:7101 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
AdminServer logs update while starting managed:
####<Feb 18, 2013 2:54:57 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-0000000000000162> <1361163297488> <BEA-149506> <Established JMX Connectivity with adp_ms01 at the JMX Service URL of service: jmx:admin://appserver701.mycompany.internal:9102 /jndi/weblogic.management.mbeanservers.runtime.>
Admin Server :
[oracle@adminserver701 bin]$ netstat -an | grep 9101
tcp 0 0 10.254.252.808:9101 0.0.0.0:* LISTEN
tcp 0 0 192.168.100.238:9101 0.0.0.0:* LISTEN
tcp 0 0 192.168.100.238:9101 192.168.100.218:59038 ESTABLISHED
I am wondering if the JMX connectivity is using the server listen address (adminserver701.mycompany.internal) which will by default resolve to 192.168.100.238. Is there a way to force JMX to use 10.254.252.808?

Hi
For first question the answer is no. With the administration port, you enable the SSL between the admin server and Node manager-managed Servers. You can still use the web console.
For teh second question, you can use ANT or can use the WLS Scripting ..you can get more details in dev2dev.bea.com
Jin

Essbase Administration Services: Cant connect to Administration Server

Cant connet to Administration Server via EAS console. I would appreciate any hints that might help me overcome this next unknown.
Background follows:
I installed EPMA 11.1.2.2, and then went to the workspace wondering where the sample data was (after I created a sample app). I discovered in docs and forumns that I had to load it through the Essbase Administration Services console. Now I'm trying to get that to work. I installed it after posts revealed that it is part of the client installers (thanks John) package. Now that it is installed I run it, try to login, and get an error message that says "could not connect to Administration Server." I reinstalled the EAS database as a new install to my server.mydomainb.org:1433 via the configurator. Then I redployed all the apps to the app server. And lastly started all of the services. Still I get the same message. I've done this about 4 times hoping that a reconfig will somehow fix something but still no joy. I've also tried loggin in with different names for the server such as myserver:1433 or myserver.mydomain.org:1433 or myserver and none of those helped either.
I have manually started all the services so they appear to be working. I may be missing one but I wouldn't know.
The services that are running include:
Hyperion EPM Server - Web Application
Hyperion EPMA Server
Hyperion Financial Data Quality Management
Hyperion Integration Services
Hyperion Reporting and Analysis Framework
Hyperion Studion Services BPMS bpms1
Some in posts have suggested also going to the logs. 11.1.2.2 docs say that the EAS logs are located at oracle_home\user_projects\domains\epmsystem\servers\EssAdm..Services0\logs\easserver.log. But I found mine at:
<oracle_home>\user_projects\domains\epmsystem1\servers\logs. You will notice that my empsystem is empsystem1 instead. There I found that the easserver.log file is empty but I did find one error in the file EPMServer0.log. The error I found is as follows:
####<Apr 4, 2013 11:42:09 AM MDT> <Error> <JDBC> <SLCBRASSTEST> <EPMServer0> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1365097329966> <BEA-001112> <Test "select count(*) from SERVERLOGID" set up for pool "eas_datasource" failed with exception: "java.sql.SQLSyntaxErrorException: [FMWGEN][SQLServer JDBC Driver][SQLServer]Invalid object name 'SERVERLOGID'.".>
I'm not sure what to try next so any suggestions would be helpful. Thanks!

"Hyperion EPM Server - Web Application" indicates that the web apps have been deployed to a single managed server, this means the web apps will be running a default port of 9000, the EAS console is not aware of the port so you will need to include it when you add the server in the console e.g. servername:9000
Cheers
John
http://john-goodwin.blogspot.com/

Administration Port / command line / console gui question

In the Admin_ref.pdf doc it says "After enabling the administration port, all Administration Console traffic must connect via the administration port". Does this mean that you can no longer use the web gui console to manage the servers?
I would like the option to script deployments (deploy ears, stop start servers etc.) via command line to reduce the possibility of user error during routine deployments.
I do config mgmt. and am not a developer so I may be getting hung up on the language here.
Thanks,
gj

Hi
For first question the answer is no. With the administration port, you enable the SSL between the admin server and Node manager-managed Servers. You can still use the web console.
For teh second question, you can use ANT or can use the WLS Scripting ..you can get more details in dev2dev.bea.com
Jin

Error: All administrative tasks must go through an Administration Port

Hi,
I run weblogic's example MedRec as a cluster. I follow the
instruction and it works.
I have a java application (swing) connecting to the cluster.
When I set MedRec to use 7001 port for both admin and other
tasks, it works fine.
Now, I set weblogic to have separated administration port
(9002). I set ssl as requested. I can deploy ejbs to the
cluster from my swing application. So, the cluster setting
seems okay.
But I want to access ejbs from my swing application. When I
try to get InitialContext using url like "t3://mymachine:8001"
or "t3s://mymachine:7002" I get error:
"All administrative tasks must go through an Administration Port"
For my understanding, request an instance of InitialContext
is not an administration task. What is wrong here? What should I do?
Any information would be appreciated. Thanks in advance.

Jimmy Ivanov <[email protected]> writes:
If you use the admin credentials then its an admin task. Try using a
different user.
andy
Hi,
I run weblogic's example MedRec as a cluster. I follow the
instruction and it works.
I have a java application (swing) connecting to the cluster.
When I set MedRec to use 7001 port for both admin and other
tasks, it works fine.
Now, I set weblogic to have separated administration port
(9002). I set ssl as requested. I can deploy ejbs to the
cluster from my swing application. So, the cluster setting
seems okay.
But I want to access ejbs from my swing application. When I
try to get InitialContext using url like "t3://mymachine:8001"
or "t3s://mymachine:7002" I get error:
"All administrative tasks must go through an Administration Port"
For my understanding, request an instance of InitialContext
is not an administration task. What is wrong here? What should I do?
Any information would be appreciated. Thanks in advance.--

How to monitor WebLogic Server when enable the Administration Port

It works fine when use Listenport 7001, but when enable the Administration Port(9002), it does not work.
Maybe I should do something to set the system environment property, but how?
help~
Sorry for my poor English~
Thanks~

HI,
If the admin port is enabled then you have to use these parameters to run any scripts
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.TrustKeyStore=DemoTrust
-The you can use Admin URL: t3s://localhost:9002 with Admin Port and Secure Protocol.
Example:
java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust weblogic.WLST application_status.py
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3s://localhost:9002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'Domain_7001'.
.Regards,
Ravish Mody
http://middlewaremagic.com/weblogic
Come, Join Us and Experience The Magic…

Cann't connect to was302

Hello.
I cann't connect to was302 from web brosers.
i start wrb- all seems to be OK.
then :
owsctl star admin
it said:
inforamation: listening on NORM port 8888 address 0.0.0.0
started listener: pid...
monitor now running as process ...
is it normal ? What dose it mean - NORM.
Help me please.
Yours ANdrey
null

The problem is that the driver name you specified is incorrect. The site Kate pointed you to is very good for sorting out this sort of thing. In addition, try to find a native ADO or OLEDB drivers. You will get much better performance.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Cann't connect to WLC 2504

Good day.
I have new installation of AIR-CT2504. I try to connect by console, but no response on terminal. (Use notebook+ USB -COM + console cable). When connect ethernet cable to 1st port of WLC and switch port(SF200) i see controller by CDP. At first, when I see IP-address of WLC, connect notebook to it's port, and configure controller with Web-interface (maybe somthing incorrect). I change IP-address of management interface. WLC reboot, and now i cann't connect to it anymore.
By CDP I see new IP and native VLAN 0, but cann't ping it.
How can I configure WLC now? Or what trouble with console?
P.S. Sory for my bad english.

Well the wireless equipment is different. If you console into the AP, does it work? If not, then double check your settings.
Make sure of this. This can be different from the switches and routers.
No hardware flow control
Sent from Cisco Technical Support iPhone App

Cann't connect to the Admin Server!

Hi,everyone:
when I "startconsole",error appears:
"Cann't connect to Admin Server:http://myhostname.mydomain:port number,the URL is not correct or the server is not running "
how can I resolve this problem?
Thanks

This may seem like a dumb question, but
Is the Admin Server running on myhostname.mydomain:port number?

Cann't connect to PostgreSQL

I cann't connect to PostgreSQL.
I have database_connectivity_toolkit, and thy to connect PostgreSQL with ODBC driver, but have a error:
Also I have LabSQL. And when I try connect with next string: "Driver={PostgreSQL};Server=localhost;Port=5432;Database=postgres;Uid=postgres;Pwd=mypass;"I also have error:
I cann't find good information about this in internet and don't know what to do. Help me.

The problem is that the driver name you specified is incorrect. The site Kate pointed you to is very good for sorting out this sort of thing. In addition, try to find a native ADO or OLEDB drivers. You will get much better performance.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Essbase Administration Services "Can not Connect to Administration Server"

Hi
Here I am installed Oracle EPM 11.1.2.2 Essbase,Planning and Reporting and after sucessfull configuration. When I tried to open Essbase Administration Console and there is no option to open administration console and I opened the Hyperion extraction setup folder and I installed Essbase Administration Console setup manuallay and after sucessful installation I try to Open and when I create new server and ir=ts created and then I am trying to connect server its throw this error
Error: Can not Connect to Administration Server
Please give me possitive things.
Thanks in advance..

Did you deploy the web applications to one managed server in the configurator, if you did then EAS is probably running on port 9000 so you would need to enter the server in the EAS console as servername:9000
Cheers
John
http://john-goodwin.blogspot.com/

ASM instance crash due to error ORA-27506: IPC error connecting to a port

Hi All,
Today the ASM instance goes down.
When i checked the alert log I found the below error.
ORA-27506: IPC error connecting to a port
ORA-27300: OS system dependent operation:sendmsg failed with status: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: sskgxpsnd1
Please find the environment details.
OS : RHEL-5
DB: 11.1.0.7 2-node RAC
I want to know the root cause of this issue.
Please suggest.
Thanks and Regards,

Hi,
Could you please upload cluster alert log and cssd.log?
regards,
Kishore

"Device connected to USB port has malfunctioned and is not recognized"

When I hooked my nano up to my computer today, the screen went black with a silver apple icon on it...it's still all lite up and on...but it won't change from that screen.
And my computer says, "Device connected to USB port has malfunctioned and is not recognized", so it won't show up in iTunes.
What do I do?? Thanks.
Windows

iPod appears in Windows Explorer but does not appear in iTunes.
iPod does not appear in iTunes.
Fast user switching in Windows XP is not supported.
Strange iPod behavior.

Error in fax set up - connected to wrong port, although i'm not

Hi
I'm not a technical whizz kid...
Trying to set up my all in one to send faxes (I only need to be able to send the odd fax).
On the test I'm getting:
Fax hardward test PASS
Fax connected to active telephone wall jack PASS
Phone cord connected to correct port on fax FAIL.
Below that is says that the phone cord is connected to 2-ext on the bank of my device and that i should change it to 1-Line. As I said, I'm not whizz kid, but it is defintiely connected to 1-Line. I even tried switching them and I got fail on point 2, so I put it back in 1-Line but it's still not working.
I'm struggling to find any help with this particular error.
thanks
Mig

Hi @MigGilbert,
Welcome to the HP Support Forums! I see you would like to set up the Fax feature on your HP Officejet 8610, everything passes when you run the test except the correct port connection.
I would like you to start troubleshooting here: Cannot Send or Receive Faxes
Please let me know the outcome, are you now able to send a Fax?
I hope to hear from you soon.
HevnLgh
I work on behalf of HP
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to the left of the reply button to say “Thanks” for helping!

Cann't connect to Administrator Port of OAS 4.0.7

Similar Messages

Maybe you are looking for