Web server error: Could not register a HeartbeatMonitor

          Hi:
          When I use weblogic thin client (wljmsclient) and createTopicConnection()
          causes weblogic server exception below.
          Seems it depends on where my client runs. Not sure if it is related to
          network configuration for different subnet.
          Thanks in advance for your help. (weblogic server 8.1.1 or 8.1.2, IIOP protocol
          for client connection)
          Here is the exception:
          weblogic.jms.dispatcher.DispatcherException: Could not register a HeartbeatMonit
          orListener for [weblogic.iiop.IIOPRemoteRef@8b4c94fa] for weblogic.jms.C:HP01:4t
          :-38
          at weblogic.jms.dispatcher.DispatcherWrapperState.addPeerGoneListener(Di
          spatcherWrapperState.java:569)
          at weblogic.jms.dispatcher.DispatcherManager.dispatcherAdd(DispatcherMan
          ager.java:106)
          at weblogic.jms.dispatcher.DispatcherManager.addDispatcherReference(Disp
          atcherManager.java:196)
          at weblogic.jms.frontend.FEConnectionFactory.connectionCreateInternal(FE
          ConnectionFactory.java:413)
          at weblogic.jms.frontend.FEConnectionFactory.connectionCreateRequest(FEC
          onnectionFactory.java:385)
          at weblogic.jms.frontend.FEConnectionFactory_WLSkel.invoke(Unknown Sourc
          e)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
          at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
          ef.java:108)
          at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
          dSubject.java:353)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
          144)
          Tony
          

Hi Tony,
          I wonder if there was a regression between 8.1.1 and 8.1.2? Anyhow,
          since the weblogic.jar works on the client, and since you verified
          your classpaths, it seems quite likely the problem is in WebLogic.
          I recommend two things:
          (1) ensure that you are using a supported version of the JVM
          (2) filing a support case and using weblogic.jar
          as a temporary work-around while the problem gets fixed
          Sorry I couldn't help you more.
          Tom
          tony wrote:
          > Tom:
          >
          > Thanks.
          > See my answer below:
          >
          >
          > Tom Barnes <[email protected].bea.com>
          > wrote:
          >
          >>Hi Tony,
          >>
          >>Some questions/thoughts:
          >>
          >>Is that the full stack trace?
          >
          >
          > There are few more lines: (paste from weblogic server log)
          >
          > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
          > 144)
          > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > :404)
          > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > java:30)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          > aused by: weblogic.rmi.extensions.server.HeartbeatMonitorUnavailableException:
          > ould not register a HeartbeatMonitorListener for [weblogic.iiop.IIOPRemoteRef@a8
          > 2e47e4]
          > at weblogic.rmi.extensions.server.HeartbeatMonitor.addHeartbeatMonitorLi
          > tener(HeartbeatMonitor.java:86)
          > at weblogic.jms.dispatcher.DispatcherWrapperState.addPeerGoneListener(Di
          > patcherWrapperState.java:559)
          > ... 14 more
          >
          >
          >
          >
          >>Did you use 8.1.2 jars for BOTH the client and the server?
          >
          >
          > yes
          >
          >
          >>Check that the server has no thin client jar in
          >>its classpath and that the client has no weblogic.jar in
          >>its classpath?
          >
          > Double checked.
          > Actually if client uses weblogic.jar, instead of wljmsclient and wlclient (thin
          > client), it works, and no this exception.
          >
          > Tony
          >
          >>Tom
          >>
          >>Tony wrote:
          >>
          >>>Hi:
          >>>
          >>> When I use weblogic thin client (wljmsclient) and createTopicConnection()
          >>>causes weblogic server exception below.
          >>> Seems it depends on where my client runs. Not sure if it is
          >>
          >>related to
          >>
          >>>network configuration for different subnet.
          >>> Thanks in advance for your help. (weblogic server 8.1.1 or 8.1.2,
          >>
          >>IIOP protocol
          >>
          >>>for client connection)
          >>>
          >>> Here is the exception:
          >>>
          >>>weblogic.jms.dispatcher.DispatcherException: Could not register a HeartbeatMonit
          >>>
          >>>orListener for [weblogic.iiop.IIOPRemoteRef@8b4c94fa] for weblogic.jms.C:HP01:4t
          >>>
          >>>:-38
          >>>
          >>> at weblogic.jms.dispatcher.DispatcherWrapperState.addPeerGoneListener(Di
          >>>
          >>>spatcherWrapperState.java:569)
          >>>
          >>> at weblogic.jms.dispatcher.DispatcherManager.dispatcherAdd(DispatcherMan
          >>>
          >>>ager.java:106)
          >>>
          >>> at weblogic.jms.dispatcher.DispatcherManager.addDispatcherReference(Disp
          >>>
          >>>atcherManager.java:196)
          >>>
          >>> at weblogic.jms.frontend.FEConnectionFactory.connectionCreateInternal(FE
          >>>
          >>>ConnectionFactory.java:413)
          >>>
          >>> at weblogic.jms.frontend.FEConnectionFactory.connectionCreateRequest(FEC
          >>>
          >>>onnectionFactory.java:385)
          >>>
          >>> at weblogic.jms.frontend.FEConnectionFactory_WLSkel.invoke(Unknown
          >>
          >>Sourc
          >>
          >>>e)
          >>>
          >>> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
          >>>
          >>> at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
          >>>
          >>>ef.java:108)
          >>>
          >>> at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
          >>>
          >>> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
          >>>
          >>>dSubject.java:353)
          >>>
          >>> at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
          >>>
          >>>144)
          >>>
          >>>
          >>>
          >>>Tony
          >>>
          >>>
          >>
          >
          

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

  • While installing the itunes setup i am getting an error"Could not register type library for file ipodsevice.exe" What to do now?

    While installing the itunes setup i am getting an error"Could not register type library for file ipodsevice.exe" What to do now?

    Try posting in the iTunes forum.  You have an iTunes problem not an iPod problem

  • Server error:Could not find a client that is able to launch the selection.

    server error
    Hi all,
    When i try to run jsp file on server, RAD prompt me this error: Could not find a client that is able to launch the selection.
    Please help,
    thanks

    Hi
    A question. The deploy is right?
    thank you

  • Deploy Web Site Error:Could not load file or assembly 'System.Data.SqlServerCe, Version=4.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies

    I have created a ASP.NET web Site (not Web application), using Visual Studio 2012 Ultimate and "SQL Server Compact 4.0 Local Database" in my C# Code.
    I am able to successfully compile & publish the website to another IIS Web Server, with Operating System Windows Server 2008 R2 Standard. I can even test, successfully, this website on the machine I developed it in.
    I am publishing the website, from within Visual Studio, to a Network web server running IIS.  To Publish I am using Build-> "Publish Web Site".  In the Publish Profile, I am using Web Deploy Method. Even though I am using, successfully,
    "SQL Server Compact 4.0 Local Database" in my website, the "settings" (in Publish Profile) does not detect any Databases in the project. Which may not be a problem.
    When I try to bring up the web site on the IIS Web Server machine I get the following error..    
    Could not load file or assembly 'System.Data.SqlServerCe, Version=4.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies .
    As my project is a Web Site, not Web Site Application, I do not have a references node in the Solution Explorer. I think the System.Data.SqlServerCe.dll, which is type GAC in my project, is not getting published to the webserver, which is causing this Error.
    Can I copy this .dll over manually ? If yes, where to put on the ISS Web Server ? I do not see any bin folder.
    Any help to resolve this error will be appreciated.
    diana4

    Hello.. I went ahead and created web application project and have gone past that error. But I have a new error now
    System.Data.SqlServerCe.SqlCeException: Unable to load the native components of
    SQL Server Compact corresponding to the ADO.NET provider of version 8876.
    Install the correct version of SQL Server Compact. Refer to KB article 974247
    for more details.
    Compiling and Publishing (Deployment) are both successful 
    In my project, when adding reference to SQL Server Compact Edition , there are 2 possible locations to reference the DDL from:
    C:\Program Files\Microsoft SQL Server Compact Edition\v4.0\Private
    C:\Program Files\Microsoft SQL Server Compact Edition\v4.0\Desktop.
    I have tried both. I get the same error as shown above.
    Interestingly, in My WebConfig, I do not see any reference to System.Data.SqlServerCe.
    Yet, the Website works when I click on Ctrl+F5 
    diana4

  • Custom Timer Job to execute WCF web service error - Could not find default endpoint element that references contract

    Hi,
    I am currently creating custom timer job to call WCF web service to perform nighty job to update employee document library metadata. If I update regular list/library items it updates correctly on a specified interval basis. However when I try to integrate
    the WCF client, it throws error shown below :
    Could not find default endpoint element that references contract EmployeeServiceReference.
    EmployeeServiceClient in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element.
    I followed exact instructions Andrew Connell has provided but included my logic in execute()
    public
    override
    void Execute(Guid
    targetInstanceId)
    var empClient =
    new
    'ServiceReference.EmployeeServiceClient();
    var employee = empClient.EmployeesMethod();
    I have tried all approaches to manually adding app.config settings in sharepoing web.config but still it throws the error mentioned. It seems that application config and sharepoint site config binding issue still exist and cannot be resolved.
    <system.serviceModel>
    <bindings>
    <basicHttpBinding>
    <binding
    name="BasicHttpBinding_EmployeeService"
    />
    </basicHttpBinding>
    <netTcpBinding>
    <binding
    name="CustomBinding_EmployeeService">
    <security>
    <transport
    protectionLevel="None"
    />
    </security>
    </binding>
    </netTcpBinding>
    <wsHttpBinding>
    <binding
    name="WSHttpBinding_EmployeeService">
    <security
    mode="None"
    />
    </binding>
    </wsHttpBinding>
    </bindings>
    <client>
    <endpoint
    address="http://services.mycomp.com/EmployeeService.svc"
    binding="wsHttpBinding"
    bindingConfiguration="WSHttpBinding_EmployeeService"
    contract="EmployeeServiceReference.EmployeeService"
    name="WSHttpBinding_EmployeeService"
    />
    <endpoint
    address="http://services.mycomp.com/EmployeeService.svc/soap"
    binding="basicHttpBinding"
    bindingConfiguration="BasicHttpBinding_EmployeeService"
    contract="EmployeeServiceReference.EmployeeService"
    name="BasicHttpBinding_EmployeeService"
    />
    <endpoint
    address="net.tcp://crmapp.mycomp.com:5050/EmployeeService.svc/tcp"
    binding="netTcpBinding"
    bindingConfiguration="CustomBinding_EmployeeService"
    contract="EmployeeServiceReference.EmployeeService"
    name="CustomBinding_EmployeeService">
    <identity>
    <userPrincipalName
    value="[email protected]"
    />
    </identity>
    </endpoint>
    </client>
    </system.serviceModel>
    Will you please help resolving this issue?

    Hi,
    You can use any of the three approaches:-
    1) Access web application's web.config programmatically in Execute() method.
    http://praveenkasireddy.wordpress.com/2012/12/14/access-web-application-configuration-values-in-timer-job-sharepoint/
    2) Store the configuration in xml and upload it to SharePoint document library then read from there
    http://www.sharepointdynamics.net/2011/08/using-an-xml-settings-file-to-store-values-for-your-sharepoint-projects/
    3) Programmatically configure a WCF endpoint.
    http://msdn.microsoft.com/en-us/library/ff647110.aspx
    Regards, Shruti

  • Administration server error: could not connect to server

    I was just viewing some outlines and calc scripts. I got un error trying to close a clac script. It said unable to unlock and then closes EAS. I tried to log back in and I am getting a could not connect error. How do I fix this or do I just recycle the server

    A little less drastic is to restart the EAS service. I've had an occasion or two where the service just up and stopped for no apparent reason, leaving me hanging with several hours of work to be redone in an outline... <sigh>
    Anyway, restarting the EAS service may be all that you needed to do, it may have aborted or hung itself.
    Edit: clearer to say service here rather than server.

  • Java web server error when not connected to network

    If my laptop is not connected to a network, when I execute the java web server, it fails at start up with the exceptions listed below. When debugging, I need access only to local host, so it seemed reasonable to me that the web server should execute in the absence of a network.
    I just found that I get the same failure, if I'm connected to the network via a dialup connection.
    Any ideas on how to configure my system so that the web server will function in the absence of a network connection?
    Microsoft Windows 2000 [Version 5.00.2195]
    (C) Copyright 1985-2000 Microsoft Corp.
    C:\>j2ee -verbose
    J2EE server listen port: 1050
    org.omg.CORBA.INTERNAL: minor code: 1398079697 completed: No
    at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
    253)
    at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:202
    at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
    37)
    at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:48
    4)
    at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:144
    at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:102)
    at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:109)
    at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:127)
    at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:23)
    at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
    2159)
    at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
    va:2110)
    at com.sun.enterprise.server.J2EEServer.run(../../src/share/com/sun/ente
    rprise/server/J2EEServer.java:192)
    at com.sun.enterprise.server.J2EEServer.main(../../src/share/com/sun/ent
    erprise/server/J2EEServer.java:901)
    java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
    ports in use by another process
    at com.sun.enterprise.server.J2EEServer.run(../../src/share/com/sun/ente
    rprise/server/J2EEServer.java:202)
    at com.sun.enterprise.server.J2EEServer.main(../../src/share/com/sun/ent
    erprise/server/J2EEServer.java:901)
    java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
    ports in use by another process
    at com.sun.enterprise.server.J2EEServer.run(../../src/share/com/sun/ente
    rprise/server/J2EEServer.java:202)
    at com.sun.enterprise.server.J2EEServer.main(../../src/share/com/sun/ent
    erprise/server/J2EEServer.java:901)
    java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
    ports in use by another process
    at com.sun.enterprise.server.J2EEServer.run(../../src/share/com/sun/ente
    rprise/server/J2EEServer.java:347)
    at com.sun.enterprise.server.J2EEServer.main(../../src/share/com/sun/ent
    erprise/server/J2EEServer.java:901)
    J2EE server reported the following error: Unable to create ORB. Possible causes
    include TCP/IP ports in use by another process
    Error executing J2EE server ...

    Has anyone else ever seen this failure?

  • Web service handler could not registered/called in client web service

    Hi Expert,
    I have two web service ServiceA & ServiceB and both implemented in weblogic.
    The ServiceA is SSL enable and protocol is https which is not published by me.
    The ServieB is my web service(wls8.1) and act as client for ServiceA.
    My problem is when i hit my service, its not able set the handler when it call ServiceA but it is invoking the service and giving application exception like authentication error.
    My service file:
    import java.util.ArrayList;
    import java.util.HashMap;
    import java.util.Iterator;
    import java.util.List;
    import java.util.Map;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.handler.HandlerInfo;
    import javax.xml.rpc.handler.HandlerRegistry;
    import javax.xml.rpc.handler.soap.SOAPMessageContext;
    import weblogic.webservice.client.SSLAdapterFactory;
    import weblogic.webservice.client.WLSSLAdapter;
    public class HelloService {
    String wsdl = "https://188.122.123.23/RemoetService?WSDL";
    static     {
              SSLAdapterFactory factory =                SSLAdapterFactory.getDefaultFactory();
              WLSSLAdapter adapter = (WLSSLAdapter)     factory.getSSLAdapter();
              adapter.setTrustedCertificatesFile("D:\\lib\\certs\\cacerts");
              factory.setDefaultAdapter(adapter);
              System.setProperty("weblogic.xml.encryption.verbose","true");
              System.setProperty("weblogic.xml.signature.verbose","true");
              System.setProperty("weblogic.webservice.verbose","true");
         public String sayHello(String user) {
              RemoteService_Impl service = new RemoteService_Impl(wsdl);
              RemotePortType port = service.getRemoteServicePort1();
              String namespace = service.getServiceName()
                        .getNamespaceURI();
              QName portName = new QName(namespace,
                        "RemoteServicePortType");
              HandlerRegistry reg = service.getHandlerRegistry();
              List handlerList = new ArrayList();
              Map map = new HashMap();
              map.put("Username", "user1");
              map.put("Password", "pwd1");
              HandlerInfo info = new HandlerInfo();
              info.setHandlerClass(WSClientHandler .class);
              info.setHandlerConfig(map);
              handlerList.add(info);
              reg.setHandlerChain(portName,(List)handlerList);
              RemoteServiceResponse = port.callMe(name);
    My Handler Class:
    package com.test;
    import java.util.Map;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.handler.Handler;
    import javax.xml.rpc.handler.HandlerInfo;
    import javax.xml.rpc.handler.MessageContext;
    import javax.xml.rpc.handler.soap.SOAPMessageContext;
    import javax.xml.soap.Name;
    import javax.xml.soap.SOAPElement;
    import javax.xml.soap.SOAPEnvelope;
    import javax.xml.soap.SOAPException;
    import javax.xml.soap.SOAPHeader;
    import javax.xml.soap.SOAPHeaderElement;
    public class WSClientHandler implements Handler {
         private HandlerInfo handlerInfo;
         public WSClientAuthenticateHandler(){}
         public void init(HandlerInfo hi) {   
              System.out.println("Handler init");
              handlerInfo = hi;
         public void destroy() {
              System.out.println("Handler destroy method called");
              handlerInfo = null;
         public QName[] getHeaders() {
              System.out.println("Handler Header method called");
              try     {
                   Map map = handlerInfo.getHandlerConfig();
                   QName[] headers = handlerInfo.getHeaders();
                   System.out.println(" Config :"+map);
                   for(int i=0;i<headers.length;i++)     {
                        System.out.println(headers.getLocalPart()+" "+
                        headers[i].toString()+" "+headers[i].getNamespaceURI());
              }catch(Exception e)     {
                   e.printStackTrace();
              return handlerInfo.getHeaders();
         public boolean handleRequest(MessageContext mc) {   
              SOAPMessageContext smc = (SOAPMessageContext) mc;
              System.out.println("Calling handler class.....................");
              try     {
              SOAPEnvelope se =      smc.getMessage().getSOAPPart().getEnvelope();
              System.out.println("Calling handler class.....................");
         SOAPHeader soapHeader = se.getHeader();
         Name headerName = se.createName("Security","wsse","http://schemas.xmlsoap.org/ws/2002/07/secext");
         SOAPHeaderElement headerElement = soapHeader.addHeaderElement(headerName);
         SOAPElement element = headerElement.addChildElement(se.createName("UsernameToken", "wsse", "http://schemas.xmlsoap.org/ws/2002/07/secext"));
         element.addChildElement(se.createName("Username", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testuser");
         element.addChildElement(se.createName("Password", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testpwd");
         System.out.println("Calling handler class.....................");
                   System.out.println("** Request: \n "+se.toString()+"\n");
              }catch(SOAPException e)     {
                   e.printStackTrace();
              return true;
         /** * Specifies that the SOAP response message be logged to a
         * log file before the
         * * message is sent back to the client application
         * that invoked the Web service.
         public boolean handleResponse(MessageContext mc) {  
              System.out.println("Handler Response method called");
              SOAPMessageContext messageContext = (SOAPMessageContext) mc;
              System.out.println("** Response: \n"+messageContext.getMessage().toString()+"\n");
              return true;
         /** * Specifies that a message be logged to the log file if a SOAP fault is
         * * thrown by the Handler instance.
         public boolean handleFault(MessageContext mc) {   
              SOAPMessageContext messageContext = (SOAPMessageContext) mc;
              System.out.println("** Fault: \n"+messageContext.getMessage().toString()+"\n");
              return true;
    Please need help here.
    Thanks in Advance,
    pps

    I have tested static client calling using handler simple above service and found the issues.
    QName portName = new QName(namespace,
    *"RemoteServicePortType");*
    The above line code has created the issues,becuase in wsdl file ( given similar wsdl file).
    <?xml version="1.0"; encoding="UTF-8"?>
    <definitions name="HelloService"
    targetNamespace="http://www.ecerami.com/wsdl/HelloService.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://www.ecerami.com/wsdl/HelloService.wsdl"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <message name="SayHelloRequest">
    <part name="firstName" type="xsd:string"/>
    </message>
    <message name="SayHelloResponse">
    <part name="greeting" type="xsd:string"/>
    </message>
    <portType name="*RemoteServicePortType*">
    <operation name="sayHello">
    <input message="tns:SayHelloRequest"/>
    <output message="tns:SayHelloResponse"/>
    </operation>
    </portType>
    <binding name="Hello_Binding" type="tns:*RemoteServicePortType*">
    <soap:binding style="rpc"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="sayHello">
    <soap:operation soapAction="sayHello"/>
    <input>
    <soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    namespace="urn:examples:helloservice"
    use="encoded"/>
    </input>
    <output>
    <soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    namespace="urn:examples:helloservice"
    use="encoded"/>
    </output>
    </operation>
    </binding>
    <service name="Hello_Service">
    +<port binding="tns:Hello_Binding" name="*RemoteServicePortType1*">+
    +<soap:address+
    location="http://host1:8080/soap/servlet/rpcrouter"/>
    +</port>+
    +<port binding="tns:Hello_Binding" name="*RemoteServicePortType2*">+
    +<soap:address+
    location="http://host2:8080/soap/servlet/rpcrouter"/>
    +</port>+
    +<port binding="tns:Hello_Binding" name="*RemoteServicePortType3*">+
    +<soap:address+
    location="http://host3:8080/soap/servlet/rpcrouter"/>
    +</port>+
    +<port binding="tns:Hello_Binding" name="*RemoteServicePortType4*">+
    +<soap:address+
    location="http://host4:8080/soap/servlet/rpcrouter"/>
    +</port>+
    </service>
    </definitions>
    From the above WSDL, I have four port name (port binding="tns:Hello_Binding" name="*RemoteServicePortType1*) which is not matching with PortType (portType name="*RemoteServicePortType*")
    even i have iterated from getPorts() method and used to invoke the service.But handler was not calling when i invoke.
    Please guide me here how i specify correct portname which can call Handler class also.
    Thanks in advance,
    pps

  • Could not register a HeartbeatMonitorListener

    Hi!
              Saw a different posting on this subject and have exactly the same
              problem. I have 2 local servers, one WLS 7 server and the other is
              Weblogic 8. I want messages sent to the WLS7 queue accessible from the
              WLS 8 queue. WLS 7 runs on port 7001, and WLS 8 on 8001.
              JMS Config for WLS 7:
              ============================
              - JMS Config factory:
              Name: WLS 7 Connection Factory
              JNDI Name: rps.refapp.jms.jms_connfactory
              - JMS Queue:
              Name: WLS7
              JNDI Name: jms.wls7.q
              Foreign JMS Config for WLS 8:
              =============================
              - Foreign JMS Server:
              Name:     MyJMSServer
              JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
              JNDI Connection URL: t3://localhost:7001
              - Foreign JMSConnection Factroy:
              Name: WLS 7 Connection Factory
              Local JNDI Name: jms.wls7connfactory
              Remote JNDI Name: rps.refapp.jms.jms_connfactory
              User Name: system
              Password: weblogic
              - Foreign JMS Destinations:
              Name:     WLS7
              Local JNDI Name: jms.wls7_queue
              Remote JNDI Name: jms.wls7.q
              I have an MDB deployed on the WLS 8 server with no funtionality except
              sending the contents of a message to system.out. Here is the contents of
              the weblogic-ejb-jar:
              <weblogic-ejb-jar>
              <description><![CDATA[Generated by XDoclet]]></description>
              <weblogic-enterprise-bean>
              <ejb-name>MessageListener</ejb-name>
              <message-driven-descriptor>
              <pool>
              <max-beans-in-free-pool>1</max-beans-in-free-pool>
              <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
              </pool>
              <destination-jndi-name>jms.wls7_queue</destination-jndi-name>
              <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
              <jms-polling-interval-seconds>5</jms-polling-interval-seconds>
              </message-driven-descriptor>
              <reference-descriptor>
              </reference-descriptor>
              <jndi-name>MessageListener</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              And here is the stacktrace after deploying the bean:
              <2003-dec-15 kl 17:51 CET> <Notice> <WebLogicServer> <BEA-000327>
              <Starting WebLogic Admin Server "myserver" for domain "mydomain">
              <2003-dec-15 kl 17:52 CET> <Warning> <EJB> <BEA-010061> <The
              Message-Driven EJB: MessageListener is unable to connect to the JMS
              destination: jms.wls7_queue. The Error was:
              [EJB:010196]'weblogic.jms.common.JMSException: Error creating session'
              Linked exception = 'weblogic.jms.dispatcher.DispatcherException: Could
              not register a HeartbeatMonitorListener for
              [weblogic.jms.dispatcher.DispatcherImpl@1970ae0] for myserver'
              weblogic.jms.common.JMSException: Error creating session
              at
              weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:798)
              at
              weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1036)
              at weblogic.jms.frontend.FESession.invoke(FESession.java:2550)
              at
              weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:609)
              at
              weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:153)
              at
              weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1814)
              at
              weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1645)
              at
              weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1484)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1598)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1833)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSConnectionPoller.java:830)
              at
              weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:234)
              at
              weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1583)
              at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1411)
              at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:668)
              at
              weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2017)
              at
              weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2058)
              at
              weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2005)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3136)
              at
              weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1688)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:407)
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
              at
              weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
              at weblogic.Server.main(Server.java:32)
              Caused by: weblogic.jms.dispatcher.DispatcherException: Could not
              register a HeartbeatMonitorListener for
              [weblogic.jms.dispatcher.DispatcherImpl@1970ae0] for myserver
              at
              weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:309)
              at
              weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:356)
              at
              weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:796)
              ... 26 more
              Caused by:
              weblogic.rmi.extensions.server.HeartbeatMonitorUnavailableException:
              Could not register a HeartbeatMonitorListener for
              [weblogic.jms.dispatcher.DispatcherImpl@1970ae0]
              at
              weblogic.rmi.extensions.server.HeartbeatMonitor.addHeartbeatMonitorListener(HeartbeatMonitor.java:86)
              at
              weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:305)
              ... 28 more
              >
              Well, I'm out of ideas, so I hope someone can help me out. This is a
              fairly simple problem to duplicate. I can send more details as well.
              Thanks in advance,
              /Eje Thorarinsson
              

    Hi!
              Saw a different posting on this subject and have exactly the same
              problem. I have 2 local servers, one WLS 7 server and the other is
              Weblogic 8. I want messages sent to the WLS7 queue accessible from the
              WLS 8 queue. WLS 7 runs on port 7001, and WLS 8 on 8001.
              JMS Config for WLS 7:
              ============================
              - JMS Config factory:
              Name: WLS 7 Connection Factory
              JNDI Name: rps.refapp.jms.jms_connfactory
              - JMS Queue:
              Name: WLS7
              JNDI Name: jms.wls7.q
              Foreign JMS Config for WLS 8:
              =============================
              - Foreign JMS Server:
              Name:     MyJMSServer
              JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
              JNDI Connection URL: t3://localhost:7001
              - Foreign JMSConnection Factroy:
              Name: WLS 7 Connection Factory
              Local JNDI Name: jms.wls7connfactory
              Remote JNDI Name: rps.refapp.jms.jms_connfactory
              User Name: system
              Password: weblogic
              - Foreign JMS Destinations:
              Name:     WLS7
              Local JNDI Name: jms.wls7_queue
              Remote JNDI Name: jms.wls7.q
              I have an MDB deployed on the WLS 8 server with no funtionality except
              sending the contents of a message to system.out. Here is the contents of
              the weblogic-ejb-jar:
              <weblogic-ejb-jar>
              <description><![CDATA[Generated by XDoclet]]></description>
              <weblogic-enterprise-bean>
              <ejb-name>MessageListener</ejb-name>
              <message-driven-descriptor>
              <pool>
              <max-beans-in-free-pool>1</max-beans-in-free-pool>
              <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
              </pool>
              <destination-jndi-name>jms.wls7_queue</destination-jndi-name>
              <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
              <jms-polling-interval-seconds>5</jms-polling-interval-seconds>
              </message-driven-descriptor>
              <reference-descriptor>
              </reference-descriptor>
              <jndi-name>MessageListener</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              And here is the stacktrace after deploying the bean:
              <2003-dec-15 kl 17:51 CET> <Notice> <WebLogicServer> <BEA-000327>
              <Starting WebLogic Admin Server "myserver" for domain "mydomain">
              <2003-dec-15 kl 17:52 CET> <Warning> <EJB> <BEA-010061> <The
              Message-Driven EJB: MessageListener is unable to connect to the JMS
              destination: jms.wls7_queue. The Error was:
              [EJB:010196]'weblogic.jms.common.JMSException: Error creating session'
              Linked exception = 'weblogic.jms.dispatcher.DispatcherException: Could
              not register a HeartbeatMonitorListener for
              [weblogic.jms.dispatcher.DispatcherImpl@1970ae0] for myserver'
              weblogic.jms.common.JMSException: Error creating session
              at
              weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:798)
              at
              weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1036)
              at weblogic.jms.frontend.FESession.invoke(FESession.java:2550)
              at
              weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:609)
              at
              weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:153)
              at
              weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1814)
              at
              weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1645)
              at
              weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1484)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1598)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1833)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSConnectionPoller.java:830)
              at
              weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:234)
              at
              weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1583)
              at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1411)
              at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:668)
              at
              weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2017)
              at
              weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2058)
              at
              weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2005)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3136)
              at
              weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1688)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:407)
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
              at
              weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
              at weblogic.Server.main(Server.java:32)
              Caused by: weblogic.jms.dispatcher.DispatcherException: Could not
              register a HeartbeatMonitorListener for
              [weblogic.jms.dispatcher.DispatcherImpl@1970ae0] for myserver
              at
              weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:309)
              at
              weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:356)
              at
              weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:796)
              ... 26 more
              Caused by:
              weblogic.rmi.extensions.server.HeartbeatMonitorUnavailableException:
              Could not register a HeartbeatMonitorListener for
              [weblogic.jms.dispatcher.DispatcherImpl@1970ae0]
              at
              weblogic.rmi.extensions.server.HeartbeatMonitor.addHeartbeatMonitorListener(HeartbeatMonitor.java:86)
              at
              weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:305)
              ... 28 more
              >
              Well, I'm out of ideas, so I hope someone can help me out. This is a
              fairly simple problem to duplicate. I can send more details as well.
              Thanks in advance,
              /Eje Thorarinsson
              

  • Layer Comps To Files - Export error: Could not complete this operation. There are no user slices

    I have been using the Export Layer Comps To Files scrips that ships with Adobe Photoshop CS5 for a while and found it very useful, apart from the numbers it automatically adds as a prefix to the layercomp name.
    A friend pointed me in the direction of a altered version of this scrips which removes the numbers and only exports the layer comp name, gerat I thought. Not great! After using this successfully for a while the scrip started to throw up errors whenever I attempted to export. Either "No layer comps found" or "Adobe Save for Web & Devices Error: Could not complete this operation. There are no user slices." As I knew there were layercomps for the first error and knew that I had not created any slices for the second error I was pretty miffed. Fortunately I had the foresight to make a copy of the original script from the Photoshop presets library.
    I have since deleted the offending script out of my presets folder and copied the original script back in however the error still persists. I constantly receive Adobe Save for Web & Devices Error: Could not complete this operation. There are no user slices. I have searched the forums and around the net to try and find a solution for this problem but none seem to present themselves. I am perplex how this error can persist when the original script is now being used.
    If there's is anyone out there who can help me resolve this I'd be most grateful. As I say I've tried to resolve this myself and am pretty computer savvy but this one has defeated me
    Thanks in advance

    The problem seems to be already solved, but I'm commenting this for future reference.
    This has happened to me too and I think I know what causes it.
    It happens when you...
    1) Do "Save for Web" with the "All User Slices" selected in the dropdown menu "Slices".
    (This can only be done with a file that has a user slice)
    2) Then try to use the "Layer Comp to Files" script to a file that doesn't have any slices.
    To avoid this you need to once open a file that "has" a user slice and save with
    the "All Slices" option in the "Slices" menu and then go back to the file you want
    to run the script to.
    When you run the script, the saved "Slices" option from the previous export seems to
    be used and causes an error when there are no user slice.
    I also found a fix to the script to avoid this error to come out.
    This can be also applied to the fix to "remove the numbers" added to the head of the
    exported file names.
    The number removal script goes something like this...
    var fileNameBody = exportInfo.fileNamePrefix;
    if (fileNameBody != "") fileNameBody += "_";
    fileNameBody += compRef.name;
    this should replace the "Layer Comps to Files.jsx" lines 188-190.
    In addition to that, the script below needs to be added below line 818 and line 863.
    (This line numbers are those before any alterations to the "Layer Comps to Files.jsx" script)
    var idSWsl = charIDToTypeID( "SWsl" );
    var idSTsl = charIDToTypeID( "STsl" );
    var idSLAl = charIDToTypeID( "SLAl" );
    desc4.putEnumerated( idSWsl, idSTsl, idSLAl );
    The line right above where the above script should be inserted should read as the following...
    desc4.putPath( id44, new File( exportInfo.destination + "/" + fileNameBody + ".png") );
    Actually it can be added any where after the "desc4" variable is declared but I specified just
    to make it simple.
    This sets the "Save for Web" "Slices" settings to "All User Slices".

  • Errors:"Could not find Web Ser"- "Failed to Lunch E1 menu on HTML Engine"

    Hi all
    I am trying to install JD Edwards EnterpriseOne and I am using two different machines.
    First machine:
    Installed Enterprise and Database Server
    Second Machine:
    Installed Deployment Server.
    Installed Oracle Application Server.
    Installed Server Manager.
    Distributed the HTML Server.
    Registered the Oracle Application Server and HTML Server and both services are up and running.
    When I try to navigate in the Tools->EnterpriseOne Menu I have two errors:
    First error: "Could not find Web Server"
    -> followed by the second error: "Failed to launch E1 Menu on HTML Engine"
    Is there any configuration steps that I am missing?
    Please suggest anything to solve this issue.
    Thank you and best regards

    Hi,
    you can't start EnterpriseOne Menu from "tools".
    Just point you browser to the Distributed the HTML Server url.
    Regards.
    Bruno Condemi

  • Error while using spring multipart in Oracle Weblogic 10.3.6 - org.springframework.web.portlet.dispatcherportlet - could not complete request

    Hi there,
    We were using the spring multipart for the purpose of uploading a file into our application running on Oracle Weblogic Server 10.3.2 using spring framework.
    It was working fine until we upgraded our server to the version 10.3.6
    After the upgrade, we started getting the below error while we try to submit the form after selecting the file to be uploaded.
    2013-11-20 06:11:29,923 ERROR||[[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)']||[email protected]||org.springframework.web.portlet.DispatcherPortlet||Could not complete request
    javax.portlet.PortletException: Error occured during request processing: javax/portlet/ActionRequest
            at org.springframework.web.portlet.DispatcherPortlet.doActionService(DispatcherPortlet.java:668)[org.springframework.web.portlet-3.0.2.RELEASE.jar:3.0.2.RELEASE]
            at org.springframework.web.portlet.FrameworkPortlet.processRequest(FrameworkPortlet.java:519)[org.springframework.web.portlet-3.0.2.RELEASE.jar:3.0.2.RELEASE]
            at org.springframework.web.portlet.FrameworkPortlet.processAction(FrameworkPortlet.java:460)[org.springframework.web.portlet-3.0.2.RELEASE.jar:3.0.2.RELEASE]
            at com.bea.portlet.container.PortletStub.doAction(PortletStub.java:901)[portlet-container.jar:10.3.6 ]
            at com.bea.portlet.container.FilterChainGenerator.runFilterChain(FilterChainGenerator.java:96)[portlet-container.jar:10.3.6 ]
            at com.bea.portlet.container.PortletStub.processAction(PortletStub.java:314)[portlet-container.jar:10.3.6 ]
            at com.bea.portlet.container.AppContainer.invokeProcessAction(AppContainer.java:679)[portlet-container.jar:10.3.6 ]
            at com.bea.netuix.servlets.controls.content.JavaPortletContent.fireProcessAction(JavaPortletContent.java:209)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.servlets.controls.portlet.JavaPortlet.fireProcessAction(JavaPortlet.java:1299)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.servlets.controls.portlet.JavaPortlet.raiseChangeEvents(JavaPortlet.java:805)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.nf.ControlLifecycle$4.postVisitRoot(ControlLifecycle.java:316)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:341)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:399)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:465)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:291)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:219)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:275)[netuix_servlet.jar:10.3.6 ]
            at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:731)[netuix_servlet-full.jar:10.3.6 ]
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)[javax.servlet_1.0.0.0_2-5.jar:2.5]
            at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)[weblogic.jar:10.3.6.0]
            at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)[weblogic.jar:10.3.6.0]
            at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)[weblogic.jar:10.3.6.0]
            at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)[weblogic.jar:10.3.6.0]
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)[weblogic.jar:10.3.6.0]
            at com.bea.content.manager.servlets.ContentServletFilter.doFilter(ContentServletFilter.java:178)[content_servlet.jar:10.3.6 ]
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)[weblogic.jar:10.3.6.0]
            at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:336)[p13n_ejb.jar:10.3.6 ]
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)[weblogic.jar:10.3.6.0]
            at com.rogers.business.servlet.filter.GenericContentFilter.doFilter(GenericContentFilter.java:50)[GenericContentFilter.class:]
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)[weblogic.jar:10.3.6.0]
            at com.rogers.business.servlet.filter.SessionExpiryFilter.doFilter(SessionExpiryFilter.java:82)[SessionExpiryFilter.class:]
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)[weblogic.jar:10.3.6.0]
            at com.rogers.business.servlet.filter.ServletExceptionFilter.doFilter(ServletExceptionFilter.java:54)[ServletExceptionFilter.class:]
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)[weblogic.jar:10.3.6.0]
            at com.rogers.business.servlet.seo.SEOUrlFilter.doFilter(SEOUrlFilter.java:87)[SEOUrlFilter.class:]
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)[weblogic.jar:10.3.6.0]
            at com.rogers.business.servlet.filter.BusinessContextDetectionFilter.doFilter(BusinessContextDetectionFilter.java:75)[BusinessContextDetectionFilter.class:]
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)[weblogic.jar:10.3.6.0]
            at com.rogers.business.servlet.filter.LanguageProvinceSelectionFilter.doFilter(LanguageProvinceSelectionFilter.java:160)[LanguageProvinceSelectionFilter.class:]
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)[weblogic.jar:10.3.6.0]
            at com.bea.content.manager.servlets.ContentServletFilter.doFilter(ContentServletFilter.java:178)[content_servlet.jar:10.3.6 ]
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)[weblogic.jar:10.3.6.0]
            at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)[weblogic.jar:10.3.6.0]
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)[weblogic.jar:10.3.6.0]
            at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)[weblogic.jar:10.3.6.0]
            at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)[weblogic.jar:10.3.6.0]
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)[com.bea.core.weblogic.security.identity_1.2.0.0.jar:1.2.0.0]
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)[com.bea.core.weblogic.security.wls_1.0.0.0_6-2-0-0.jar:6.2.0.0]
            at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)[weblogic.jar:10.3.6.0]
            at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)[weblogic.jar:10.3.6.0]
            at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)[weblogic.jar:10.3.6.0]
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)[com.bea.core.weblogic.workmanager_1.11.0.0.jar:1.11.0.0]
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)[com.bea.core.weblogic.workmanager_1.11.0.0.jar:1.11.0.0]
    We are using "ActionMapping" to call the action method in our controller from the JSP form.
    Have anyone faced this error before?
    Any help would be much appreciated.
    Thanks,
    Lan

    Hi Lan,
    Did you get any resolution for the above issue ?
    If yes can you share it as we also ran into this.
    Regards
    Manu

  • Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\120 registry key.

    Dear Expert,
    I setup SharePoint for 3 tiers, WFE, APP + DB Server.
    I installed SQL 2014 reporting service Add-in on APP Server and already enable sql reporting service in DB Server. DB Server can do report server.
    I follow the step : https://msdn.microsoft.com/en-us/library/jj219068(v=sql.120).aspx  but I stuck in no.2, I cannot start the services, in picture below.
    I checked the SSRS provision is disabled not online
    Please help.

    Hi MasterBird,
    According to your description, when you register and start the Reporting Services SharePoint Service, the error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\120 registry key is thrown out.
    As this
    article say, if you use three-computer deployment, the first computer hosts an instance of a SharePoint product. The Reporting Services Add-in is installed on this computer. The second computer hosts SQL Server Reporting Services and the third computer
    hosts an instance of the Database Engine.
    Regarding the error message, it could cause by the Reporting Services – SharePoint feature and Reporting Services Add-in for SharePoint Products haven’t been installed. Please refer to articles:
    SSRS SharePoint 2013 Create Service Application error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key Error
    Installing SSRS 2012 in SharePoint Mode on SP2010
    If issue persists, please check the error detailed information in ULS logs, and check Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log to see if any error occurred during set up. For more information, please refer to this article:
    Troubleshoot a Reporting Services Installation.
    If you have any question, please feel free to ask.
    Best regards,
    Qiuyun Yu
    Qiuyun Yu
    TechNet Community Support

  • EAS - Error: "Could not connect Administration Server

    hello All,
    i am very new to EPM
    i have installed EPM 11.1.2.2 with web application deployed to single manage server
    OS : windows server 2008
    database : sql server
    when i try to connect EAS console it gives me error
    Could not connect Administration Server
    any idea?

    If it has been deployed to a single managed server on the default port then you will need to add the server in EAS console as servername:9000
    Cheers
    John
    http://john-goodwin.blogspot.com/

Maybe you are looking for