?HAL PrimeAlert agent components on SunMC 3.6.1

Looking to remove the PrimeAlert agent components from the SunMC systems, clients
and server. Looking through documentation found that there should be a HALuninstall script.
Looked on the systems and did not find the script. Could do a pkgrm but want to avoid causing
problems. Any suggestions? Thanks.
system HALmmarpt PrimeAlert Reporter (agent component)
system HALmmarrd RRDTool
system HALsmadir PrimeAlert DirectoryMonitor (agent component)
system HALsmafbr PrimeAlert FileBrowser (agent component)
system HALsmafil PrimeAlert FileSizeMonitor (agent component)
system HALsmakit PrimeAlert Agent Toolkit (Agent Component)
system HALsmalog PrimeAlert LogFileMonitor (agent component)
system HALsmaprc PrimeAlert ProcessMonitor (agent component)
system HALsmassa PrimeAlert SystemMonitor for Solaris (agent component)
system HALsmasub PrimeAlert Submodule Infrastructure (Agent Component)
system HALsmatop PrimeAlert Top10 (agent component)
system HALsmavvm PrimeAlert for Veritas Volume Manager (agent component)

wabbit wrote:
Looking to remove the PrimeAlert agent components from the SunMC systems, clients
and server. Looking through documentation found that there should be a HALuninstall script.
Looked on the systems and did not find the script. Do you have this file on that system?:
/var/opt/SUNWsymon/uninstall/HALUninstall.sh
If not, please contact [Halcyon Support|http://www.halcyoninc.com/support/index.php] and they can help you out.
Regards,
[email protected]
[http://www.HalcyonInc.com|http://www.HalcyonInc.com]
New !! : [http://forums.HalcyonInc.com|http://forums.HalcyonInc.com] !!

Similar Messages

  • "Could not start Agent" with SunMC 3.6.1 on Red Hat Enterprise release 4

    Hi everyone,
    I'm trying to install the Linux agent from the SunMC 3.6.1 installation dvd on a RedHat system (kernel 2.6). The installation seems to go fine, but while seting up the agent I recieve the following eror:
    /opt/SUNWsymon/base/sbin/xget: error while loading shared libraries: libxcfg.so.1.0: cannot open shared object file: No such file or directory
    /opt/SUNWsymon/base/sbin/xput: error while loading shared libraries: libxcfg.so.1.0: cannot open shared object file: No such file or directory
    Naturally, in the end you get the message "Could not start Agent"...
    Has anybody experienced this with a RedHat system or any other Linux system?
    Best Regards,
    Emerald

    Hi!
    I am trying to install SunMC 4.0 agent in a Red Hat Enterprise Linux AS release 4 (whith a SunMC server installed in a Solaris 10 platform).
    I had installed the agent in the Red Hat, but the agent did not start.
    I got this messages from the agent.log ( the same messages that Emerald)
    [00000000 0046 ]info May 14 10:19:25 agent Channel already exists: syslog......................
    [00000001 0048 ]info May 14 10:19:25 agent using ip mode for URL addressing....................
    [00000002 003b ]info May 14 10:19:25 agent enabling timed jobs.................................
    [00000003 004d ]info May 14 10:19:25 agent subagent registry successfully loaded...............
    [00000004 005a ]info May 14 10:19:25 agent loading trap actions: subagent-manager-trap-action..
    [00000005 0040 ]info May 14 10:19:25 agent startLegacySubagents: <>............................
    [00000006 003e ]info May 14 10:19:25 agent activating MIB objects..............................
    [00000007 0047 ]info May 14 10:19:25 agent *** shutting down subagents ***.....................
    [00000008 005d ]error May 14 10:19:25 agent stopemd: action command script em-daemon.sh not found.
    [00000009 007b ]error May 14 10:19:25 agent invalid dictionary entry: internal outBoundTrap in b
    ase-agent.x(221) at token '???'............................................................................
    [0000000a 0042 ]error May 14 10:19:25 agent *** aborting execution ***..........................
    [0000000b 0046 ]info May 14 10:20:29 agent Channel already exists: syslog......................
    [0000000c 0048 ]info May 14 10:20:29 agent using ip mode for URL addressing....................
    [0000000d 003b ]info May 14 10:20:29 agent enabling timed jobs.................................
    [0000000e 004d ]info May 14 10:20:29 agent subagent registry successfully loaded...............
    [0000000f 005a ]info May 14 10:20:29 agent loading trap actions: subagent-manager-trap-action..
    [00000010 0040 ]info May 14 10:20:29 agent startLegacySubagents: <>............................
    [00000011 003e ]info May 14 10:20:29 agent activating MIB objects..............................
    [00000012 0047 ]info May 14 10:20:29 agent *** shutting down subagents ***.....................
    [00000013 005d ]error May 14 10:20:29 agent stopemd: action command script em-daemon.sh not found
    Had anyone resolve this isue?? or had any ideas to resolve it??
    Thanks in advance.
    maza

  • Diagnostics and Agent Questions

    Hi
    We are currently installing the agents and need info onfollowing for
    our production installs: Version of Solution manager 7 sp19
    1) If i have a single server with 2 sap systems: ECC and GTS, which of
    this agents do I have to install for each system? Where can I find a
    table matrix that lists the agents/components and those details?
    Diagnostic Agent (abap/java)per system/app?
    sapccm4x (abap only), per sap system/app?
    sapccmsr (java only),per system/app?
    ccmsping (abap?),per system/app?
    SAPOSCOL (abap/java)per system/app?
    Wily agent (java?) per system/app?
    2) If I have ECC prod system 1 ci+db + 2 app servers (in separate
    machines), which of the above agents to have still have to install for
    the app servers?
    sapccm4x (abap only), per system?
    sapccmsr (java only),per system?
    ccmsping (abap?),per system?
    SAPOSCOL (abap/java)per system?
    wily agent (java) per system

    Hi,
    1) 1 Diagnostic Agent/SAP system : SAP Note :1365123
           CCMS Agents : 1 agent per system.
           CCMSPing for each system(standalone ABAP/JAVA).
    2) Refer to same SAP note as Above for Diagnostic Agent.
    Do revert for any queries pls.
    Thanks,
    Jagan

  • Execution timed out error when running opcagt command on linux server with agent 11.12.009 installed

    Hi,
    Can anyone help me in the below issue.
    we have a Linux server with agent version 11.12.009 installed on it. when I try running opcragt command on it through are management server it gives the output that all agent components are running.
    but when I check the agent status or version through opcagt command on it it gives below error:
    ERROR:   (depl-86) Unable to execute command 'opcagt' on node
                       (depl-176) Message returned from host           
    (xpl-117) Timeout occurred while waiting for data.
    Below are the error lines that I got from system.txt file of the server:
    0: ERR: Fri Dec 19 09:09:38 2014: ovconfd (3708/140429034952480): (conf-180) Could not create messenger for configuration server 'ovconfd' and register its methods with the messenger object.
    1: ERR: Fri Dec 19 09:09:38 2014: ovconfd (3708/140429034952480): (xpl-89) write(11)[012C5430] failed.
    2: ERR: Fri Dec 19 09:09:38 2014: ovconfd (3708/140429034952480): (RTL-28) No space left on device
    Could anyone please let me know what can be the issue in this.
    Thanks,
    Akansha

    ORA-00600: internal error code, arguments: [kzxcInitLoadLocal-7], [942],
    [ORA-00942: table or view does not exist
    ORA-01403: no data found
    ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 252
    ORA-06512: at line 36
    ORA-01403: no data foundWhat does this query return?
    SQL>  SELECT HOST, ACL
    FROM DBA_NETWORK_ACLS;Please see (Redefining a Network Access Control List Fails with ORA-1403 [ID 854083.1]).
    Thanks,
    Hussein

  • Agent configuration mass duplication

    Does anyone know if there is a way to set up just one agent host, configure it exactly how you want it with modules, alarms, etc. and then duplicate that same config across many agents?

    Does anyone know if there is a way to set up just one
    agent host, configure it exactly how you want it with
    modules, alarms, etc. and then duplicate that same
    config across many agents?In SunMC 3.0 you can template systems as you describe using MCP (Module Configuration Propagation) Parcels. This functionality is part of the Premier package. If you don't have this package installed there are other ways to do the same thing manually. Open your Console and click:
    Tools -> Group Operations...
    File -> New -> MCP Parcel...
    ...then follow these instructions:
    http://docs.sun.com/source/806-5942/grouping2.html#1001641
    If you are part of the SunMC 3.5 beta, this functionality has been relabelled a "Configurations Task" instead of "MCP Parcel".
    Regards,
    Aronek
    Standard disclaimer: I am an employee of Halcyon (www.HalcyonInc.com)

  • Configure sunMC 3.5 U 1 to forward traps to 3rd party NMS

    Hi,
    Basically I am trying to set trap forwarding to a NNM on the network from sunMC 3.5 Update 1.
    I have followed all the directions in sunMC snmp FAQ and other threads on this forum but I am not able to set the trap destinations.
    I have added topology object and set the community as user name. When I try to perform a snmpset operation the error I get is as follows:
    $ ./snmpset -h sparc -p 162 -c user1 1.3.6.1.4.1.42.2.12.2.1.4.1.0 "OctetString" "{10.1.1.131}"
    Request Id: 0
    Error: noSuchName
    Index: 1
    Count: 1
    Name: 1.3.6.1.4.1.42.2.12.2.1.4.1.0
    Kind: OctetString
    Value: "{10.1.1.131}"
    I had exported the mib for above OIDs from the sunMC agent in interactive mode.. and after loading it on NNM machine and performing same set operation I get the same (noSuchName) error.
    I also came across command es-trapdest which allows one to add multiple trap destinations from sunMC agent (and not sunMC server). However even using this method I am unable to receive any traps from agents.
    Any help here is appreciated.
    Other thread having same question is http://forum.sun.com/thread.jspa?threadID=15625&tstart=0
    Thanks...
    Nikhil.

    Hi Nikhil!
    Basically I am trying to set trap forwarding to a
    a NNM on the network from sunMC 3.5 Update 1.
    I have followed all the directions in sunMC snmp FAQ
    and other threads on this forum but I am not able to
    set the trap destinations.<snip>
    Other thread having same question is
    http://forum.sun.com/thread.jspa?threadID=15625&tstart
    =0Have you reviewed the options in the other thread? (i.e. Halcyon SNMP integration or HP integration packages). Both are off-the-shelf and if you can understand SunMC SNMP infrastructure you certainly wouldn't have trouble configuring either. If you've looked at both packages, what parts made you decide not to use them? Note: I work for Halcyon.
    Building your own custom integration with direct traps may be difficult: the generic snmp faq doens't have all the info you need to do so (i.e. how to get NNM to go backwards to an Agent to request the details of an event like "Warning /op is 95% full" or "Critical: Power Supply 2 is Offline"). I'm not even sure how I'd go about it, and I've been using SunMC for years :)
    Regards,
    Mike
    ([email protected])

  • Configuration Manager Client Agent Backwards Compatibility - Remote Control

    Hello all,
    I'm not seeing this anywhere so I'll ask it here.  Once I complete the R2 upgrade from SP1 and the clients begin to upgrade using the Automatic Client Upgrade option there will be a number of clients upgraded to R2 and a number still at SP1.  Do
    the client agent components on those that are still at SP1 continue to function?  In particular I'm wondering about Remote Control.  My thought is the answer is yes.  Is there backwards compatibility until all client agents are upgraded?
    Thanks!

    Yes, there is.
    Torsten Meringer | http://www.mssccmfaq.de

  • Manually Install Patch Agent??

    We recently purchased Zenworks Patch Management. However, right before
    purchasing ZCM Patch Mgmt, we upgraded to ZCM 11. The ZCM 11 Agent
    components for patch management automatically installed to ZCM 11 clients,
    but not to version 10 clients. My guess is that it might have something to
    do with the fact that the MSIs for 10.3.1 are now renamed as "superceded"
    MSIs.
    I had a friend build me an "unconfigured" ZCM agent package from his 10.3.1
    system (he has ZCM Patch Management), and that successfully installs on a
    freshly imaged machine and Zenworks Patch Management seems to be working.
    However, that doesn't help me with the rest of my 10.3.1 machines that I
    don't wish to reimage right now.
    If you're asking: Why don't I upgrade my clients to the ZCM 11 Agent? I'll
    tell you my answer: IT'S WAY TOO SLOW!! Until they iron out a few issues,
    we're going to hang with the 10.3.1 agent.
    So, my question is: Is there anyway to take the MSIs that are renamed as
    "superceded" and manually install them to a workstation to get ZCM Patch
    Management working on my existing 10.3.1 clients? I tried to simply install
    the MSIs, but it doesn't seem to show up as an installed option on the ZCM
    Agent properties page.
    Thanks in advance!

    Ryan,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://forums.novell.com/

  • SMC 4.0 db-start failed

    Dear All ,
    I try install smc 4.0 on another sun box ,the reason for test CCR problem from on t2000 box ,I use same file which use for install smc on t2000 , but on step es-setup i got the problem (db-start failed).Here the log installation :
    Initiating setup for Sun Management Center Agent Component.
    This part of the setup process does the Sun Management Center Agent Component setup.
    Started /opt/SUNWsymon/lib/sbin/sm_setup_agent.sh at Thu Nov 8 20:16:52 BNT 2007.
    Running on SunOS sun240 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V240.
    Copying snmpd.conf file into /var/opt/SUNWsymon/cfg
    Server component also installed locally.
    Using this machine as the Sun Management Center server.
    ---------------------------- WARNING ---------------------------
    It appears that agent.snmpPort 161 is already in use.
    Sun Management Center 4.0 agent may not be able to run due to this conflict.
    There are two ways to correct this conflict:
    1. Reconfigure the port that Sun Management Center 4.0 uses.
    2. Stop the process that is using the port.
    Press RETURN to force default port.
    Enter port you would like to use [ 1100 to 65535 ]: 1161
    Updating /var/opt/SUNWsymon/cfg/domain-config.x with new port number.
    Generating agent security keys.
    PKCS11 Utilities package(SUNWcsl) was found.
    Encrypted SNMP Communication is supported.
    Setup of Agent component is successful.
    Starting Sun Management Center database setup...
    verifyDatabaseDown: instance is not executing
    Database consistency information missing.
    Configuring database initialization parameter file
    Stopping metadata component
    Successfully disabled service sunmc-metadata
    Stopping cfgserver component
    Successfully disabled service sunmc-cfgserver
    Stopping topology component
    Successfully disabled service sunmc-topology
    Stopping event component
    Successfully disabled service sunmc-event
    Stopping grouping service
    Successfully disabled service sunmc-grouping
    Stopping trap component
    Successfully disabled service sunmc-trap
    Stopping java server
    Successfully disabled service sunmc-javaserver
    Stopping webserver
    Successfully disabled service sunmc-webserver
    Stopping agent component
    Successfully disabled service sunmc-agent
    Stopping platform component
    Successfully disabled service sunmc-platform
    verifyDatabaseDown: instance is not executing
    Failed to enable service sunmc-database
    Database setup failed : db-start failed
    Updating registry...
    As database is not setup, Marking server setup as failed in Registry.
    None of the base layers are setup.
    No Addon is setup.
    Following Addons are not yet setup: Advanced System Monitoring,ELP Config-Reader Monitoring,Desktop,Service Availability Manager,Sun Fire Entry-Level Midrange System,Performance Reporting Manager,Solaris Container Manager,System Reliability Manager,Workgroup Server
    Could not finish requested task.
    I am already uninstall(use uninstall script ) and reinstall back , but the result is same , Does any one know how to solve this problem ?
    Regards
    hadi

    Greetings,
    I've not been able to resolve the topology issues, the recommended fixes have not resolved my issues. Upon un-installaing and re-installing multiple times I'm still not able to get the topology component to initialize correctly. The Management Center does display in the Applications listing in the Java Web Console (3.0.2) however clicking on it and displaying the main page for the Management Center 4.0 displays just a few items in the left nav, and none of the 'Discover Systems' requests make it in the queue or work at all. None of the other Management modules are displayed either. The web start console refuses to connect to the server as well, replying with a 'Server communication error, the server version may be incompatible' error.
    I've noticed quite a bit of sql errors in the install, I've not seen anything in the release notes or forums regarding this issue either. Any help on this would be greatly appreciated! SMA and snmpdx are both disabled as well as dmi services.
    The server is x86 Dell 2950, Entire install of Solaris 10 U3 11/06. Agent, Server, and Console components are installed and setup.
    */etc/project:*
    system:0::::
    user.root:1::::
    noproject:2::::
    default:3::::project.max-shm-memory=(priv,5368708912,deny)
    group.staff:10::::
    from */var/adm/messages:*
    Dec 19 12:19:21 dvall topology[963]: [ID 840589 daemon.alert] syslog Dec 19 12:19:21 topology parsing error in file://localhost/topology-license-d.x;flags=ro(13):
    Dec 19 12:19:21 dvall topology[963]: [ID 259113 daemon.alert] syslog Dec 19 12:19:21 topology *** aborting execution ***
    install log:
    Started ./es-inst at Wed Dec 19 11:50:19 PST 2007.
    Running on SunOS dvall 5.10 Generic_125101-07 i86pc i386 i86pc.
    This script installs Sun (TM) Sun Management Center 4.0
    Installation files source directory: /root/src/SunMC/disk1/image/SunOS/i386
    Copying required XML APIs from /root/src/SunMC/disk1/sbin/bin/i386-sun-solaris10 to /var/run/tmp/SunMCInstall/XML/APIs
    Enter the directory in which you want to install: [ /opt ] /opt/SunMC/
    Installation destination directory: /opt/SunMC
    Select the Sun Management Center 4.0 components to install:
    3 component(s) are available for your selection:
    Do you want to install the Server component (y|n|q) y
    Note: The Agent component will be installed automatically.
    Do you want to install the Console component (y|n|q) y
    Looking for valid JDK.
    Found incomplete installation of : "1.6.0_03-b05"
    SYMON_JAVAHOME is set to: /usr/java
    JDK version is: "1.6.0_03-b05"
    JDK check OK.
    Looking for Tomcat Webserver.
    Webserver check OK.
    You must agree to the above license agreement to proceed with installation.
    Do you agree (y|n|q) y
    Sun Management Center 4.0 can be installed in the following languages:
    Traditional Chinese
    Simplified Chinese
    French
    Japanese
    Korean
    English is installed by default.
    Are other languages required (y|n|q) n
    Reading Add-On products from image. Please wait...
    This can take approximately 3 minutes to complete.
    Found: Sun Management Center Integration for Unicenter TNG
    Found: Advanced System Monitoring
    Found: System Reliability Manager
    Found: Generic X86/X64 Config Reader
    Found: Solaris Container Manager
    Found: Service Availability Manager
    Found: Performance Reporting Manager
    Checking for applicable products. Please wait...
    This can take approximately 2 minutes to complete.
    Unable to find package directory for SUNWeshsm
    Component script found: check-remote-install.sh
    Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check-remote-install.sh
    Return value: 1
    Component script found: check-remote-install.sh
    Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check-remote-install.sh
    Return value: 1
    Component script found: check_TNG_Server.sh
    check if TNG Server is installed.
    Cannot install the Unicenter TNG addon Server component. CA-TNG is not installed, you should install CA-TNG first.
    Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check_TNG_Server.sh
    Return value: 2
    Script returned 2. Skipping this component.
    Component script found: gca-check.sh
    Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/X86ConfigReader/Solaris_10/Basic//gca-check.sh
    Return value: 1
    The Sun Management Center 4.0 Production environment will be installed.
    The following Add-On Products are applicable for installation.
    Advanced System Monitoring
    Service Availability Manager
    Performance Reporting Manager
    Solaris Container Manager
    System Reliability Manager
    Sun Management Center Integration for Unicenter TNG
    Generic X86/X64 Config Reader
    Do you want to select all the products (y|n|q) n
    Select the products you want to install:
    Advanced System Monitoring (y|n|q) y
    Service Availability Manager (y|n|q) y
    Performance Reporting Manager (y|n|q) y
    Solaris Container Manager (y|n|q) y
    System Reliability Manager (y|n|q) y
    Sun Management Center Integration for Unicenter TNG (y|n|q) n
    Generic X86/X64 Config Reader (y|n|q) y
    The following Add-On Products will be installed:
    Advanced System Monitoring
    Service Availability Manager
    Performance Reporting Manager
    Solaris Container Manager
    System Reliability Manager
    Generic X86/X64 Config Reader
    Do you want to proceed (y|n|q) y
    The following Add-On products are covered under license agreement:
    You must agree to the above license agreement to proceed with installation.
    Do you agree (y|n|q) y
    Disk Space Checking....
    Installing the components...
    Installing... PRODUCT.PE COMPONENT.AGENT
    Processing package instance <SUNWescom> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Common Components(i386) 4.0,REV=2.10.2007.10.23
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    Installing Sun Management Center Common Components as <SUNWescom>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    2426 blocks
    ## Executing postinstall script.
    Installation of <SUNWescom> was successful.
    Processing package instance <SUNWenesi> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center script localization messages(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    1 package pathname is already properly installed.
    Installing Sun Management Center script localization messages as <SUNWenesi>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    683 blocks
    Installation of <SUNWenesi> was successful.
    Processing package instance <SUNWesagt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Agent(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center Agent as <SUNWesagt>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    24750 blocks
    ## Executing postinstall script.
    Installation of <SUNWesagt> was successful.
    Processing package instance <SUNWesmib> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Mib Instance Module(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    4 package pathnames are already properly installed.
    Installing Sun Management Center Mib Instance Module as <SUNWesmib>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    281 blocks
    Installation of <SUNWesmib> was successful.
    Processing package instance <SUNWesken> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Kernel Reader Module(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    5 package pathnames are already properly installed.
    Installing Sun Management Center Kernel Reader Module as <SUNWesken>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    399 blocks
    Installation of <SUNWesken> was successful.
    Processing package instance <SUNWesmod> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Agent Modules(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    9 package pathnames are already properly installed.
    Installing Sun Management Center Agent Modules as <SUNWesmod>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    235 blocks
    Installation of <SUNWesmod> was successful.
    Processing package instance <SUNWesae> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Agent System Files(i386) 4.0,REV=2.10.2007.10.15
    Using </> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    9 package pathnames are already properly installed.
    Installing Sun Management Center Agent System Files as <SUNWesae>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    28 blocks
    ## Executing postinstall script.
    Installation of <SUNWesae> was successful.
    Processing package instance <SUNWesaem> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Event Module for Agent(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    9 package pathnames are already properly installed.
    Installing Sun Management Center Event Module for Agent as <SUNWesaem>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    186 blocks
    Installation of <SUNWesaem> was successful.
    Processing package instance <SUNWesgui> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center GUI Installation(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    7 package pathnames are already properly installed.
    Installing Sun Management Center GUI Installation as <SUNWesgui>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    6250 blocks
    Installation of <SUNWesgui> was successful.
    Processing package instance <SUNWsuagt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Dynamic Agent Update Agent Components(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    6 package pathnames are already properly installed.
    Installing Sun Management Center Dynamic Agent Update Agent Components as <SUNWsuagt>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    152 blocks
    Installation of <SUNWsuagt> was successful.
    Processing package instance <SUNWesval> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Validation Tool Components(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    4 package pathnames are already properly installed.
    Installing Sun Management Center Validation Tool Components as <SUNWesval>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    220 blocks
    Installation of <SUNWesval> was successful.
    Processing package instance <SUNWesaxp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Java API for XML Processing (JAXP) v1.1.3(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Java API for XML Processing (JAXP) v1.1.3 as <SUNWesaxp>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    2362 blocks
    Installation of <SUNWesaxp> was successful.
    Processing package instance <SUNWesmcp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Module Configuration Propagation(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    8 package pathnames are already properly installed.
    Installing Sun Management Center Module Configuration Propagation as <SUNWesmcp>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    249 blocks
    Installation of <SUNWesmcp> was successful.
    Processing package instance <SUNWeslac> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Local Access(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center Local Access as <SUNWeslac>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    14 blocks
    Installation of <SUNWeslac> was successful.
    Processing package instance <SUNWesafm> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center FMA Service Module for Agent(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    5 package pathnames are already properly installed.
    Installing Sun Management Center FMA Service Module for Agent as <SUNWesafm>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    92 blocks
    Installation of <SUNWesafm> was successful.
    Package SUNWservicetagr is already installed on this system.
    Validating the Registry entry.
    Package SUNWservicetagu is already installed on this system.
    Validating the Registry entry.
    Package SUNWstosreg is already installed on this system.
    Validating the Registry entry.
    Installing... PRODUCT.PE COMPONENT.CONSOLE
    Package SUNWescom is already installed on this system.
    Validating the Registry entry.
    Package SUNWenesi is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWescon> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Console(i386) 4.0,REV=2.9.2007.10.16
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    4 package pathnames are already properly installed.
    Installing Sun Management Center Console as <SUNWescon>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    6638 blocks
    Installation of <SUNWescon> was successful.
    Processing package instance <SUNWesjp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Additional Components(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Additional Components as <SUNWesjp>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    5819 blocks
    Installation of <SUNWesjp> was successful.
    Package SUNWesaxp is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesclt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Client API(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Client API as <SUNWesclt>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    1609 blocks
    Installation of <SUNWesclt> was successful.
    Processing package instance <SUNWesjrm> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Client API support classes(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Client API support classes as <SUNWesjrm>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    663 blocks
    Installation of <SUNWesjrm> was successful.
    Processing package instance <SUNWenesf> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Console properties(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Console properties as <SUNWenesf>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    557 blocks
    ## Executing postinstall script.
    Installation of <SUNWenesf> was successful.
    Package SUNWesgui is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesasc> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Advanced Services Console(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Advanced Services Console as <SUNWesasc>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    156 blocks
    Installation of <SUNWesasc> was successful.
    Processing package instance <SUNWescix> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Import/Export(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Import/Export as <SUNWescix>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    156 blocks
    Installation of <SUNWescix> was successful.
    Processing package instance <SUNWsucon> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Dynamic Agent Update Console Components(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Dynamic Agent Update Console Components as <SUNWsucon>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    27 blocks
    Installation of <SUNWsucon> was successful.
    Processing package instance <SUNWescli> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Command Line Interface(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    5 package pathnames are already properly installed.
    Installing Sun Management Center Command Line Interface as <SUNWescli>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    862 blocks
    Installation of <SUNWescli> was successful.
    Processing package instance <SUNWesclb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Command Line Interface For BatchMode(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    4 package pathnames are already properly installed.
    Installing Sun Management Center Command Line Interface For BatchMode as <SUNWesclb>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    155 blocks
    Installation of <SUNWesclb> was successful.
    Package SUNWesval is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesmc> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center MCP Console(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center MCP Console as <SUNWesmc>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    200 blocks
    Installation of <SUNWesmc> was successful.
    Processing package instance <SUNWescdv> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Console Dataview(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center Console Dataview as <SUNWescdv>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    354 blocks
    Installation of <SUNWescdv> was successful.
    Installing... PRODUCT.PE COMPONENT.SERVER
    Package SUNWescom is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesbui> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Web Console(sparc) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center Web Console as <SUNWesbui>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    7789 blocks
    Installation of <SUNWesbui> was successful.
    Processing package instance <SUNWesbuh> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Help(sparc) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Help as <SUNWesbuh>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    498 blocks
    Installation of <SUNWesbuh> was successful.
    Package SUNWenesi is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesdb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Database(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management Center Database as <SUNWesdb>
    ## Executing preinstall script.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    Group smcdbg created
    User smcdbu created
    ## Installing part 1 of 1.
    /opt/SunMC/SUNWsymon/base <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/base/bin <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/base/bin/i386-sun-solaris2.10 <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/base/lib <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/base/lib/i386-sun-solaris2.10 <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/lib/sbin <conflicting pathname not installed>
    /opt/SunMC/SUNWsymon/sbin <conflicting pathname not installed>
    928 blocks
    Installation of <SUNWesdb> was successful.
    Package SUNWesagt is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWessrv> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Server(i386) 4.0,REV=2.9.2007.10.16
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    12 package pathnames are already properly installed.
    Installing Sun Management Center Server as <SUNWessrv>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    10640 blocks
    [ verifying class <preserve> ]
    Installation of <SUNWessrv> was successful.
    Processing package instance <SUNWessa> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Server/Agent(i386) 4.0,REV=2.10.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    10 package pathnames are already properly installed.
    Installing Sun Management Center Server/Agent as <SUNWessa>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    2218 blocks
    Installation of <SUNWessa> was successful.
    Package SUNWesjp is already installed on this system.
    Validating the Registry entry.
    Package SUNWesaxp is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesse> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
    Sun Management Center Server System Files(i386) 4.0,REV=2.10.2007.10.15
    Using </> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    5 package pathnames are already properly installed.
    Installing Sun Management Center Server System Files as <SUNWesse>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    36 blocks
    ## Executing postinstall script.
    Installation of <SUNWesse> was successful.
    Package SUNWesclt is already installed on this system.
    Validating the Registry entry.
    Package SUNWesjrm is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWmeta> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Metadata Agent(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    3 package pathnames are already properly installed.
    Installing Sun Management Center Metadata Agent as <SUNWmeta>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    38 blocks
    Installation of <SUNWmeta> was successful.
    Package SUNWenesf is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesmdr> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center MDR for Basic Pack(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    4 package pathnames are already properly installed.
    Installing Sun Management Center MDR for Basic Pack as <SUNWesmdr>
    ## Installing part 1 of 1.
    Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    246 blocks
    Installation of <SUNWesmdr> was successful.
    Package SUNWesgui is already installed on this system.
    Validating the Registry entry.
    Processing package instance <SUNWesweb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
    Sun Management Center Web Console(i386) 4.0,REV=2.9.2007.10.15
    Using </opt/SunMC> as the package base directory.
    ## Processing package information.
    ## Processing system information.
    2 package pathnames are already properly installed.
    Installing Sun Management C

  • 11.1.2.2  workspace and sharedservices error

    I installed 11.1.2.2 in my laptop....but iam getting following error for workspace and sharedservices.
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    please help how to resolve it

    Found the following in MIDDLEWARE_HOME/user_projects/epmsystem1/diagnostics/logs/validation/validationTool-stdout.txt
    ALL  ) HTTP Server checks failed!!!!!!!!!!!!!!!!!.......
    ( Feb 3, 2014 9:39:40 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:40 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:41 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:41 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:41 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:41 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:41 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:41 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:41 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:41 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:42 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:42 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:42 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:42 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:42 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:42 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:42 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:42 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:43 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:43 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:43 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:43 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:43 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:43 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:43 PM ) Configuration tasks state test successfully completed.
    ( Feb 3, 2014 9:39:43 PM )  - passed: Validating that configuration tasks have been completed
    ( Feb 3, 2014 9:39:44 PM ) DB Connectivity test for repository successfully completed.
    ( Feb 3, 2014 9:39:44 PM )  - passed: Checking connection to database jdbc:oracle:thin:@localhost:1521:orcl
    ( Feb 3, 2014 9:39:44 PM ) DB Connectivity test for repository successfully completed.
    ( Feb 3, 2014 9:39:44 PM )  - passed: Checking connection to database jdbc:oracle:thin:@localhost:1521:orcl
    ( Feb 3, 2014 9:39:44 PM ) DB Connectivity test for repository successfully completed.
    ( Feb 3, 2014 9:39:44 PM )  - passed: Checking connection to database jdbc:oracle:thin:@localhost:1521:orcl
    ( Feb 3, 2014 9:39:44 PM ) DB Connectivity test for repository successfully completed.
    ( Feb 3, 2014 9:39:44 PM )  - passed: Checking connection to database jdbc:oracle:thin:@localhost:1521:orcl
    ( Feb 3, 2014 9:39:45 PM ) DB Connectivity test for repository successfully completed.
    ( Feb 3, 2014 9:39:45 PM )  - passed: Checking connection to database jdbc:oracle:thin:@localhost:1521:orcl
    ( Feb 3, 2014 9:39:45 PM ) DB Connectivity test for repository successfully completed.
    ( Feb 3, 2014 9:39:45 PM )  - passed: Checking connection to database jdbc:oracle:thin:@localhost:1521:orcl
    ( Feb 3, 2014 9:39:45 PM ) DB Connectivity test for repository successfully completed.
    ( Feb 3, 2014 9:39:45 PM )  - passed: Checking connection to database jdbc:oracle:thin:@localhost:1521:orcl
    ( Feb 3, 2014 9:39:46 PM ) DB Connectivity test for repository successfully completed.
    ( Feb 3, 2014 9:39:46 PM )  - passed: Checking connection to database jdbc:oracle:thin:@localhost:1521:orcl
    ( Feb 3, 2014 9:39:50 PM ) Web Applications check failed.
    ( Feb 3, 2014 9:39:50 PM )  - failed: Availability of Web application context http://EPMSrvr:6550/aif/faces/setup/Main.jspx
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:50 PM )  - failed: Availability of Web application context http://EPMSrvr:6550/oracle-epm-erpi-webservices/RuleService
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:50 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/aif/faces/setup/Main.jspx
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:50 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/oracle-epm-erpi-webservices/RuleService
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:55 PM ) Web Applications check failed.
    ( Feb 3, 2014 9:39:55 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/easconsole/console.html
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:55 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/aps/APS
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:55 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/essbase-webservices/AdminService
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:55 PM )  - failed: Availability of Web application context http://EPMSrvr:13080/aps/APS
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:55 PM )  - failed: Availability of Web application context http://EPMSrvr:13080/essbase-webservices/AdminService
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:57 PM ) Web Applications check failed.
    ( Feb 3, 2014 9:39:57 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/awb/conf/AwbConfig.xml
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:57 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/DataSync
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:59 PM ) Web Applications check failed.
    ( Feb 3, 2014 9:39:59 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/calcmgr/index.htm
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:39:59 PM )  - failed: Availability of Web application context http://EPMSrvr:8500/calcmgr/index.htm
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:04 PM ) Web Applications check failed.
    ( Feb 3, 2014 9:40:04 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/easconsole/console.html
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:04 PM )  - failed: Availability of Web application context http://EPMSrvr:10080/easconsole/console.html
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:04 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/aps/APS
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:04 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/essbase-webservices/AdminService
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:06 PM ) Web Applications check failed.
    ( Feb 3, 2014 9:40:06 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/interop
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:06 PM )  - failed: Availability of Web application context http://EPMSrvr:28080/interop
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:10 PM ) Web Applications check failed.
    ( Feb 3, 2014 9:40:10 PM )  - failed: Availability of Web application context http://EPMSrvr:7363/oracle-epm-fm-webservices/ApplicationService
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:10 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/oracle-epm-fm-webservices/ApplicationService
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:10 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/hfmadf/faces/hfm.jspx
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:10 PM )  - failed: Availability of Web application context http://EPMSrvr:7363/hfmadf/faces/hfm.jspx
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:11 PM ) Web Applications check failed.
    ( Feb 3, 2014 9:40:13 PM ) Web Applications check failed.
    ( Feb 3, 2014 9:40:13 PM )  - failed: Availability of Web application context http://EPMSrvr:28080/workspace/status
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:13 PM )  - failed: Availability of Web application context http://EPMSrvr:9000/workspace/status
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM ) HTTP Server check failed.
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/interop
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/workspace/status
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/awb/conf/AwbConfig.xml
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/easconsole/console.html
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/calcmgr/index.htm
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/DataSync
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/oracle-epm-fm-webservices/ApplicationService
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/hfmadf/faces/hfm.jspx
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/hfmofficeprovider/HFMOfficeProvider.aspx
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/HyperionFDM
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/hfmlcmservice/LCMWS.asmx
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/hfmapplicationservice/Application.asmx
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/hfm/default.asp
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/hyperion-bpma-server/Applications.asmx
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/aif/faces/setup/Main.jspx
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/oracle-epm-erpi-webservices/RuleService
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/raframework/index.jsp
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/aps/APS
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:34 PM )  - failed: Checking availability of HTTP context http://EPMSrvr:9000/essbase-webservices/AdminService
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:36 PM ) External Providers check successfully completed.
    ( Feb 3, 2014 9:40:36 PM )  - passed: Check Native Directory external authentication provider configuration
    ( Feb 3, 2014 9:40:37 PM ) External Providers check successfully completed.
    ( Feb 3, 2014 9:40:37 PM )  - passed: Check Native Directory external authentication provider configuration
    ( Feb 3, 2014 9:40:37 PM ) External Providers check successfully completed.
    ( Feb 3, 2014 9:40:37 PM )  - passed: Check Native Directory external authentication provider configuration
    ( Feb 3, 2014 9:40:37 PM ) External Providers check successfully completed.
    ( Feb 3, 2014 9:40:37 PM )  - passed: Check Native Directory external authentication provider configuration
    ( Feb 3, 2014 9:40:37 PM ) External Providers check successfully completed.
    ( Feb 3, 2014 9:40:37 PM )  - passed: Check Native Directory external authentication provider configuration
    ( Feb 3, 2014 9:40:38 PM ) External Providers check successfully completed.
    ( Feb 3, 2014 9:40:38 PM )  - passed: Check Native Directory external authentication provider configuration
    ( Feb 3, 2014 9:40:38 PM ) External Providers check successfully completed.
    ( Feb 3, 2014 9:40:38 PM )  - passed: Check Native Directory external authentication provider configuration
    ( Feb 3, 2014 9:40:38 PM ) External Providers check successfully completed.
    ( Feb 3, 2014 9:40:38 PM )  - passed: Check Native Directory external authentication provider configuration
    ( Feb 3, 2014 9:40:38 PM ) External Providers check successfully completed.
    ( Feb 3, 2014 9:40:38 PM )  - passed: Check Native Directory external authentication provider configuration
    ( Feb 3, 2014 9:40:39 PM ) External Providers check successfully completed.
    ( Feb 3, 2014 9:40:39 PM )  - passed: Check Native Directory external authentication provider configuration
    ( Feb 3, 2014 9:40:41 PM ) Login check failed.
    ( Feb 3, 2014 9:40:41 PM )  - failed: Checking availability of login http://EPMSrvr:28080/interop/logon
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:41 PM )  - failed: Checking availability of login http://EPMSrvr:28080/interop/logon
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:43 PM ) Login check failed.
    ( Feb 3, 2014 9:40:43 PM )  - failed: Checking availability of login http://EPMSrvr:28080/workspace/status
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:43 PM )  - failed: Checking availability of login http://EPMSrvr:28080/workspace/status
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:40:50 PM ) Missed registry links check successfully completed.
    ( Feb 3, 2014 9:40:50 PM )  - passed: Checking that all components in the registry have a link to host
    ( Feb 3, 2014 9:40:50 PM ) Datasource entries existence successfully completed.
    ( Feb 3, 2014 9:40:50 PM )  - passed: Checking if datasource property exists in the registry
    ( Feb 3, 2014 9:40:50 PM )  - passed: Checking if datasource property exists in the registry
    ( Feb 3, 2014 9:40:50 PM ) Datasource entries existence failed.
    ( Feb 3, 2014 9:40:50 PM ) Datasource entries existence failed.
    ( Feb 3, 2014 9:40:51 PM ) Datasource entries existence successfully completed.
    ( Feb 3, 2014 9:40:51 PM )  - passed: Checking if datasource property exists in the registry
    ( Feb 3, 2014 9:40:51 PM )  - passed: Checking if datasource property exists in the registry
    ( Feb 3, 2014 9:40:51 PM ) Datasource entries existence failed.
    ( Feb 3, 2014 9:40:51 PM ) Datasource entries existence failed.
    ( Feb 3, 2014 9:40:51 PM ) Datasource entries existence failed.
    ( Feb 3, 2014 9:40:52 PM ) Datasource entries existence failed.
    ( Feb 3, 2014 9:40:52 PM ) Datasource entries existence failed.
    ( Feb 3, 2014 9:40:52 PM ) Web Server Registry check successfully completed.
    ( Feb 3, 2014 9:40:52 PM )  - passed: Checking if Web Server linked to the all Web Applications
    ( Feb 3, 2014 9:40:57 PM ) Shared library targeting test successfully completed.
    ( Feb 3, 2014 9:40:57 PM )  - passed: Check if all shared libraries are targeted for application "ErpIntegrator0".
    ( Feb 3, 2014 9:40:58 PM ) Shared library targeting test successfully completed.
    ( Feb 3, 2014 9:40:58 PM )  - passed: Check if all shared libraries are targeted for application "AnalyticProviderServices0".
    ( Feb 3, 2014 9:40:58 PM ) Shared library targeting test failed.
    ( Feb 3, 2014 9:40:58 PM ) Shared library targeting test successfully completed.
    ( Feb 3, 2014 9:40:58 PM )  - passed: Check if all shared libraries are targeted for application "CalcMgr0".
    ( Feb 3, 2014 9:40:59 PM ) Shared library targeting test successfully completed.
    ( Feb 3, 2014 9:40:59 PM )  - passed: Check if all shared libraries are targeted for application "EssbaseAdminServices0".
    ( Feb 3, 2014 9:40:59 PM ) Shared library targeting test successfully completed.
    ( Feb 3, 2014 9:40:59 PM )  - passed: Check if all shared libraries are targeted for application "FoundationServices0".
    ( Feb 3, 2014 9:40:59 PM ) Shared library targeting test successfully completed.
    ( Feb 3, 2014 9:40:59 PM )  - passed: Check if all shared libraries are targeted for application "HFMWeb0".
    ( Feb 3, 2014 9:40:59 PM )  - passed: Check if all shared libraries are targeted for application "HFMWeb0".
    ( Feb 3, 2014 9:41:00 PM ) Shared library targeting test failed.
    ( Feb 3, 2014 9:41:00 PM ) Shared library targeting test successfully completed.
    ( Feb 3, 2014 9:41:00 PM )  - passed: Check if all shared libraries are targeted for application "FoundationServices0".
    ( Feb 3, 2014 9:41:08 PM ) Checking if registry database compy with taxonomy. successfully completed.
    ( Feb 3, 2014 9:41:08 PM )  - passed: All components comply with registry taxonomy.
    ( Feb 3, 2014 9:41:08 PM ) System path variable length test successfully completed.
    ( Feb 3, 2014 9:41:08 PM )  - passed: Checking whether system path variable length exceeds 2,000
    ( Feb 3, 2014 9:41:08 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:08 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:08 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:08 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:09 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:09 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:09 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:09 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:09 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:09 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:10 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:10 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:10 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:10 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:10 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:10 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:10 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:10 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:10 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:10 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:11 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:11 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:11 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:11 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:11 PM ) Product registry component test successfully completed.
    ( Feb 3, 2014 9:41:11 PM )  - passed: Checking if product has only one product node in registry.
    ( Feb 3, 2014 9:41:12 PM ) Check system-jazn-data.xml file for HIT entries successfully completed.
    ( Feb 3, 2014 9:41:12 PM )  - passed: All HIT entries are present in system-jazn-data.xml
    ( Feb 3, 2014 9:41:12 PM ) EPMA DimensionServer Server Configuration successfully completed.
    ( Feb 3, 2014 9:41:12 PM )  - passed: Validating EPMA Dimension Server hyperion-bpma-server startup... Successful...
    ( Feb 3, 2014 9:41:16 PM ) Check EPMA services individually failed.
    ( Feb 3, 2014 9:41:16 PM )  - failed: Validating whether jobmanager service is available.
        Error:com.hyperion.cis.utils.BadResponseCodeException: Bad response code: 500
    COMP ID = oracle.EPMOHPS
    Hyperion Provider Services - Release 11.1.2.2.100.2138
    Copyright (c) 1991, 2011 Oracle and / or its affiliates. All rights reserved.
    connection mode : EMBEDDED
    essbase.properties: essbase.properties
    java System properties -DESS_ES_HOME: null
    ( Feb 3, 2014 9:41:21 PM ) Essbase server check failed.
    ( Feb 3, 2014 9:41:21 PM )  - failed: Validating Essbase Server connection to EPMSrvr
        Error:Cannot connect to olap service. Cannot connect to Essbase Server at "EPMSrvr:1423". Network error [10061]: Failed to connect to [EPMSrvr:1423]
    ( Feb 3, 2014 9:41:26 PM ) Essbase server check using MaxL failed.
    ( Feb 3, 2014 9:41:26 PM )  - failed: Validating Essbase Server startup using MaxL command
        Error:EPMVLD-01010: Cannot connect to Essbase Server using MaxL.
    ( Feb 3, 2014 9:41:28 PM ) Essbase Studio Server failed.
    ( Feb 3, 2014 9:41:28 PM )  - failed: Validating Essbase Studio Server connection
        Error:Network communication with the server failed. Check your network connection and try again.
    ( Feb 3, 2014 9:41:28 PM ) Financial Management Application Server Configuration successfully completed.
    ( Feb 3, 2014 9:41:28 PM )  - passed: Validating Financial Management Server registration Successful...
    ( Feb 3, 2014 9:41:31 PM ) Financial Management Service Validation failed.
    ( Feb 3, 2014 9:41:31 PM )  - failed: Verify that the Financial Management service is working.
        Error:EPMVLD-01024: The Financial Management service check failed: ERROR: Unable to CreateApplicationCAS
    ( Feb 3, 2014 9:41:31 PM ) Financial Management Web Server successfully completed.
    ( Feb 3, 2014 9:41:31 PM )  - passed: Validating Financial Management Web application connection Successful...
    ( Feb 3, 2014 9:41:32 PM ) SmartView Provider successfully completed.
    ( Feb 3, 2014 9:41:32 PM )  - passed: Validating Financial Management SmartView Provider connection Successful...
    ( Feb 3, 2014 9:41:32 PM ) LCM Provider successfully completed.
    ( Feb 3, 2014 9:41:32 PM )  - passed: Validating Financial Management LCM Provider connection Successful...
    ( Feb 3, 2014 9:41:49 PM ) Module login test failed.
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Shared Services with URL http://EPMSrvr:28080/workspace/index.jsp?module=interop.interop
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Performance Management Architect with URL http://EPMSrvr:28080/workspace/index.jsp?module=awb.awb
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Essbase Administration Services with URL http://EPMSrvr:28080/workspace/index.jsp?module=eas.eas
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Calculation Manager with URL http://EPMSrvr:28080/workspace/index.jsp?module=calcmgr.calcmgr
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Performance Management Architect Data Synchronizer with URL http://EPMSrvr:28080/workspace/index.jsp?module=DataSync.DataSync
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Financial Management Web Services with URL http://EPMSrvr:28080/workspace/index.jsp?module=oracle-epm-fm-webservices.oracle-epm-fm-webservices
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Financial Management ADF Web Application with URL http://EPMSrvr:28080/workspace/index.jsp?module=hfmadf.hfmadf
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Financial Management Smart View with URL http://EPMSrvr:28080/workspace/index.jsp?module=hfmofficeprovider.hfmofficeprovider
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for FDM with URL http://EPMSrvr:28080/workspace/index.jsp?module=HyperionFDM.HyperionFDM
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Financial Management LCM Service with URL http://EPMSrvr:28080/workspace/index.jsp?module=hfmlcmservice.hfmlcmservice
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Financial Management ASP Web Services with URL http://EPMSrvr:28080/workspace/index.jsp?module=hfmapplicationservice.hfmapplicationservice
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Financial Management with URL http://EPMSrvr:28080/workspace/index.jsp?module=hfm.hfm
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Performance Management Architect Dimension Server with URL http://EPMSrvr:28080/workspace/index.jsp?module=hyperion-bpma-server.hyperion-bpma-server
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for ERP Integrator with URL http://EPMSrvr:28080/workspace/index.jsp?module=aif.aif
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Reporting and Analysis with URL http://EPMSrvr:28080/workspace/index.jsp?module=raframework.raframework
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:49 PM )  - failed: Module test for Provider Services with URL http://EPMSrvr:28080/workspace/index.jsp?module=aps.aps
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:41:50 PM ) Web Server link test failed.
    ( Feb 3, 2014 9:42:08 PM ) EnumerateDimensions failed.
    ( Feb 3, 2014 9:42:08 PM )  - failed: Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_29/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.dimeditor.EnumDimensions
        Error:EPMVLD-01011: Result java.net.ConnectException; Error message:  Connection refused: connect
    ( Feb 3, 2014 9:42:26 PM ) EnumerateApplications failed.
    ( Feb 3, 2014 9:42:26 PM )  - failed: Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_29/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.repository.EnumApplications
        Error:EPMVLD-01011: Result java.net.ConnectException; Error message:  Connection refused: connect
    ( Feb 3, 2014 9:42:44 PM ) EnumerateDataSynchronizations failed.
    ( Feb 3, 2014 9:42:44 PM )  - failed: Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_29/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.repository.EnumDataSyncs
        Error:EPMVLD-01011: Result java.net.ConnectException; Error message:  Connection refused: connect
    ( Feb 3, 2014 9:43:03 PM ) DimensionEditorLoadAdf failed.
    ( Feb 3, 2014 9:43:03 PM )  - failed: Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_29/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.dimeditor.DimEditorLoadAdf
        Error:EPMVLD-01011: Result java.net.ConnectException; Error message:  Connection refused: connect
    ( Feb 3, 2014 9:43:21 PM ) ApplicationManagerLoadAdf failed.
    ( Feb 3, 2014 9:43:21 PM )  - failed: Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_29/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.appmanager.AppMgrLoadAdf
        Error:EPMVLD-01011: Result java.net.ConnectException; Error message:  Connection refused: connect
    ( Feb 3, 2014 9:43:22 PM ) Check if the Reporting and Analysis Setup (RA_SETUP) component exists. successfully completed.
    ( Feb 3, 2014 9:43:22 PM )  - passed: Found: 1.
    ( Feb 3, 2014 9:43:22 PM ) Check if all required RAF properties exist under the Reporting and Analysis Setup component. successfully completed.
    ( Feb 3, 2014 9:43:22 PM )  - passed: All required properties exist.
    ( Feb 3, 2014 9:43:23 PM ) Check if the Agent Module (AGENT_MODULE) components exist. successfully completed.
    ( Feb 3, 2014 9:43:23 PM )  - passed: Found: 1.
    ( Feb 3, 2014 9:43:23 PM ) Check if the Reporting and Analysis Service (RA_SERVICE) components exist. successfully completed.
    ( Feb 3, 2014 9:43:23 PM )  - passed: Found: 17.
    ( Feb 3, 2014 9:43:23 PM ) Check if the Agent (AGENT) components exist. successfully completed.
    ( Feb 3, 2014 9:43:23 PM )  - passed: Found: 1. Hosts for the components: EPMSrvr.
    ( Feb 3, 2014 9:43:24 PM ) Check if the RAF Logical Web App (LOGICAL_WEB_APP) component exists. successfully completed.
    ( Feb 3, 2014 9:43:24 PM )  - passed: Found: 1.
    ( Feb 3, 2014 9:43:24 PM ) Check if the RAF Web App (RA_FRAMEWORK_WEB_APP) components exist. successfully completed.
    ( Feb 3, 2014 9:43:24 PM )  - passed: Found: 2. Hosts for the components: EPMSrvr, EPMSrvr.
    ( Feb 3, 2014 9:43:25 PM ) Check consistency of the Service Agent sets between Registry and V8_SERVICEAGENT. successfully completed.
    ( Feb 3, 2014 9:43:25 PM )  - passed: Data in Registry and database are consistent.
    ( Feb 3, 2014 9:43:26 PM ) Check consistency of the Service Agent properties between Registry and database tables (V8_SERVICEAGENT, V8_SA_PROPS). successfully completed.
    ( Feb 3, 2014 9:43:26 PM )  - passed: Data in Registry and database are consistent.
    ( Feb 3, 2014 9:43:26 PM ) Check if all required RAF properties exist under the RAF Logical Web App component. successfully completed.
    ( Feb 3, 2014 9:43:26 PM )  - passed: All required properties exist.
    ( Feb 3, 2014 9:43:27 PM ) Check if all required Workspace configuration files exist under the RAF Logical Web App component. successfully completed.
    ( Feb 3, 2014 9:43:27 PM )  - passed: All required files exist.
    ( Feb 3, 2014 9:43:28 PM ) Check if Agents are available. failed.
    ( Feb 3, 2014 9:43:28 PM )  - failed: No available Agents.
        Error:No available Agents.
    ( Feb 3, 2014 9:43:30 PM ) Check if RAF Services are available. failed.
    ( Feb 3, 2014 9:43:30 PM )  - failed: No available RAF Services.
        Error:No available RAF Services.
    ( Feb 3, 2014 9:43:31 PM ) Check if Repository data folder exists. successfully completed.
    ( Feb 3, 2014 9:43:31 PM )  - passed: Data file locations are valid.
    ( Feb 3, 2014 9:43:33 PM ) Check if Job Factory data folder exists. successfully completed.
    ( Feb 3, 2014 9:43:33 PM )  - passed: Data file locations are valid.
    ( Feb 3, 2014 9:43:34 PM ) Check if Service Broker data folder exists. successfully completed.
    ( Feb 3, 2014 9:43:34 PM )  - passed: Data file locations are valid.
    ( Feb 3, 2014 9:43:36 PM ) Check if Event Server data folder exists. successfully completed.
    ( Feb 3, 2014 9:43:36 PM )  - passed: Data file locations are valid.
    ( Feb 3, 2014 9:43:36 PM ) Check if every Agent is associated with some Agent Module(s). successfully completed.
    ( Feb 3, 2014 9:43:36 PM )  - passed: Every Agent is associated with some Agent Module(s).
    ( Feb 3, 2014 9:43:37 PM ) Check if every Reporting and Analysis Service is associated with some Agent Module. successfully completed.
    ( Feb 3, 2014 9:43:37 PM )  - passed: Every Reporting and Analysis Service is associated with some Agent Module.
    ( Feb 3, 2014 9:43:38 PM ) Check if every Agent Module is associated with some Agent. successfully completed.
    ( Feb 3, 2014 9:43:38 PM )  - passed: Every Agent Module is associated with some Agent.
    ( Feb 3, 2014 9:43:38 PM ) Check if every Agent Module (except IR Log) is associated with some Reporting and Analysis Service(s). successfully completed.
    ( Feb 3, 2014 9:43:38 PM )  - passed: Every Agent Module (except IR Log) is associated with some Reporting and Analysis Service(s).
    ( Feb 3, 2014 9:43:38 PM ) Check if Agent Modules and corresponding Agents belong to the same host. successfully completed.
    ( Feb 3, 2014 9:43:38 PM )  - passed: Agent Modules and corresponding Agents belong to the same host.
    ( Feb 3, 2014 9:43:42 PM ) Check if Reporting and Analysis Services and corresponding Agent Modules belong to the same host. successfully completed.
    ( Feb 3, 2014 9:43:42 PM )  - passed: Reporting and Analysis Services and corresponding Agent Modules belong to the same host.
    ( Feb 3, 2014 9:43:43 PM ) CSS Status Check failed.
    ( Feb 3, 2014 9:43:43 PM )  - failed: Validating that CSS has been initialized
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:43:44 PM ) CES Status Check failed.
    ( Feb 3, 2014 9:43:44 PM )  - failed: Validating that CES has been initialized
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:43:46 PM ) Audit Status Check failed.
    ( Feb 3, 2014 9:43:46 PM )  - failed: Validating that Audit has been initialized
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:43:47 PM ) LCM Status Check failed.
    ( Feb 3, 2014 9:43:47 PM )  - failed: Validating that LCM has been initialized
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:43:48 PM ) HUB Status Check failed.
    ( Feb 3, 2014 9:43:48 PM )  - failed: Validating that HUB has been initialized
        Error:java.net.ConnectException: Connection refused: connect
    ( Feb 3, 2014 9:43:50 PM ) Registry Status Check failed.
    ( Feb 3, 2014 9:43:50 PM )  - failed: Validating that Registry has been initialized
        Error:java.net.ConnectException: Connection refused: connect
    Zipping logs...

  • Oracle epm 11.1.2.2 http error

    I installed (personal installation) and configured 11.1.2.2. Installation was successful. Configuration only partly successful as most of the errors point to http error and unable log on to workspace. It brings up a java.net error.
    Can you help please?

    ( Apr 4, 2013 5:12:40 PM ) Configuration tasks state test successfully completed.
    ( Apr 4, 2013 5:12:40 PM )  - passed: Validating that configuration tasks have been completed
    ( Apr 4, 2013 5:12:40 PM ) DB Connectivity test for repository successfully completed.
    ( Apr 4, 2013 5:12:40 PM )  - passed: Checking connection to database jdbc:oracle:thin:@RATNAP01:1521:FUSION
    ( Apr 4, 2013 5:12:43 PM ) Web Applications check failed.
    ( Apr 4, 2013 5:12:43 PM )  - failed: Availability of Web application context http://RATNAP01:9000/aif/faces/setup/Main.jspx
        Error:com.hyperion.cis.utils.BadResponseCodeException: Bad response code with GET method: 404
    ( Apr 4, 2013 5:12:43 PM )  - failed: Availability of Web application context http://RATNAP01:9000/oracle-epm-erpi-webservices/RuleService
        Error:com.hyperion.cis.utils.BadResponseCodeException: Bad response code with GET method: 404
    ( Apr 4, 2013 5:12:49 PM ) External Providers check successfully completed.
    ( Apr 4, 2013 5:12:49 PM )  - passed: Check Native Directory external authentication provider configuration
    ( Apr 4, 2013 5:12:53 PM ) Login check failed.
    ( Apr 4, 2013 5:12:53 PM )  - failed: Checking availability of login http://RATNAP01:9000/interop/logon
        Error:com.hyperion.cis.utils.BadResponseCodeException: Bad response code: 404
    ( Apr 4, 2013 5:12:58 PM ) Missed registry links check successfully completed.
    ( Apr 4, 2013 5:12:58 PM )  - passed: Checking that all components in the registry have a link to host
    ( Apr 4, 2013 5:12:58 PM ) Datasource entries existence successfully completed.
    ( Apr 4, 2013 5:12:58 PM )  - passed: Checking if datasource property exists in the registry
    ( Apr 4, 2013 5:12:58 PM ) Datasource entries existence failed.
    ( Apr 4, 2013 5:12:59 PM ) Datasource entries existence successfully completed.
    ( Apr 4, 2013 5:12:59 PM )  - passed: Checking if datasource property exists in the registry
    ( Apr 4, 2013 5:13:00 PM ) Datasource entries existence failed.
    ( Apr 4, 2013 5:13:02 PM ) Web Server Registry check successfully completed.
    ( Apr 4, 2013 5:13:02 PM )  - passed: Checking if Web Server linked to the all Web Applications
    ( Apr 4, 2013 5:13:02 PM ) Shared library targeting test failed.
    ( Apr 4, 2013 5:13:13 PM ) Checking if registry database compy with taxonomy. successfully completed.
    ( Apr 4, 2013 5:13:13 PM )  - passed: All components comply with registry taxonomy.
    ( Apr 4, 2013 5:13:13 PM ) System path variable length test successfully completed.
    ( Apr 4, 2013 5:13:13 PM )  - passed: Checking whether system path variable length exceeds 2,000
    ( Apr 4, 2013 5:13:13 PM ) CSS Status Check failed.
    ( Apr 4, 2013 5:13:13 PM )  - failed: Validating that CSS has been initialized
        Error:java.io.FileNotFoundException: http://RATNAP01:9000/interop/status?component=CSS
    ( Apr 4, 2013 5:13:14 PM ) CES Status Check failed.
    ( Apr 4, 2013 5:13:14 PM )  - failed: Validating that CES has been initialized
        Error:java.io.FileNotFoundException: http://RATNAP01:9000/interop/status?component=CES
    ( Apr 4, 2013 5:13:14 PM ) Audit Status Check failed.
    ( Apr 4, 2013 5:13:14 PM )  - failed: Validating that Audit has been initialized
        Error:java.io.FileNotFoundException: http://RATNAP01:9000/interop/status?component=AUDIT
    ( Apr 4, 2013 5:13:14 PM ) LCM Status Check failed.
    ( Apr 4, 2013 5:13:14 PM )  - failed: Validating that LCM has been initialized
        Error:java.io.FileNotFoundException: http://RATNAP01:9000/interop/status?component=LCM
    ( Apr 4, 2013 5:13:15 PM ) HUB Status Check failed.
    ( Apr 4, 2013 5:13:15 PM )  - failed: Validating that HUB has been initialized
        Error:java.io.FileNotFoundException: http://RATNAP01:9000/interop/status?component=HUB
    ( Apr 4, 2013 5:13:15 PM ) Registry Status Check failed.
    ( Apr 4, 2013 5:13:15 PM )  - failed: Validating that Registry has been initialized
        Error:java.io.FileNotFoundException: http://RATNAP01:9000/interop/status?component=REGISTRY
    ( Apr 4, 2013 5:13:15 PM ) Product registry component test successfully completed.
    ( Apr 4, 2013 5:13:15 PM )  - passed: Checking if product has only one product node in registry.
    ( Apr 4, 2013 5:13:18 PM ) Product registry component test failed.
    ( Apr 4, 2013 5:13:25 PM ) EPMA DimensionServer Server Configuration successfully completed.
    ( Apr 4, 2013 5:13:25 PM )  - passed: Validating EPMA Dimension Server hyperion-bpma-server startup... Successful...
    ( Apr 4, 2013 5:13:34 PM ) Check EPMA services individually failed.
    ( Apr 4, 2013 5:13:34 PM )  - failed: Validating whether jobmanager service is available.
        Error:com.hyperion.cis.utils.BadResponseCodeException: Bad response code: 500
    ( Apr 4, 2013 5:13:35 PM ) Essbase Studio Server failed.
    ( Apr 4, 2013 5:13:35 PM )  - failed: Validating Essbase Studio Server connection
        Error:api.CPException.networkError
    ( Apr 4, 2013 5:13:40 PM ) Financial Management Web Service access test successfully completed.
    ( Apr 4, 2013 5:13:40 PM )  - passed: Checking accessibility of Web services on http://RATNAP01:80/HSFWebServices/HSFWebService.asmx.
    ( Apr 4, 2013 5:13:40 PM ) Check if the Interactive Reporting Product (INTERACTIVE_REPORTING_PRODUCT) component exists. successfully completed.
    ( Apr 4, 2013 5:13:40 PM )  - passed: Found: 1.
    ( Apr 4, 2013 5:13:41 PM ) Check if IR BI Services are available. successfully completed.
    ( Apr 4, 2013 5:13:41 PM )  - passed: All IR BI Services are available: IRBI_AGENT_MODULE (Agent on ratnap01).
    ( Apr 4, 2013 5:13:41 PM ) Check if IR Job Services are available. successfully completed.
    ( Apr 4, 2013 5:13:41 PM )  - passed: All IR Job Services are available: IRJOB_AGENT_MODULE (Agent on ratnap01).
    ( Apr 4, 2013 5:13:41 PM ) Check if IR DAS Services are available. successfully completed.
    ( Apr 4, 2013 5:13:41 PM )  - passed: All IR DAS Services are available: IRDAS_AGENT_MODULE (Agent on ratnap01).
    ( Apr 4, 2013 5:13:41 PM ) Check if IR Log Services are available. successfully completed.
    ( Apr 4, 2013 5:13:41 PM )  - passed: All IR Log Services are available: IRLOG_AGENT_MODULE (Agent on ratnap01).
    ( Apr 4, 2013 5:13:42 PM ) Check if the Reporting and Analysis Setup (RA_SETUP) component exists. successfully completed.
    ( Apr 4, 2013 5:13:42 PM )  - passed: Found: 1.
    ( Apr 4, 2013 5:13:42 PM ) Check if all required RAF properties exist under the Reporting and Analysis Setup component. successfully completed.
    ( Apr 4, 2013 5:13:42 PM )  - passed: All required properties exist.
    ( Apr 4, 2013 5:13:42 PM ) Check if the Agent Module (AGENT_MODULE) components exist. successfully completed.
    ( Apr 4, 2013 5:13:42 PM )  - passed: Found: 5.
    ( Apr 4, 2013 5:13:43 PM ) Check if the Reporting and Analysis Service (RA_SERVICE) components exist. successfully completed.
    ( Apr 4, 2013 5:13:43 PM )  - passed: Found: 20.
    ( Apr 4, 2013 5:13:43 PM ) Check if the Agent (AGENT) components exist. successfully completed.
    ( Apr 4, 2013 5:13:43 PM )  - passed: Found: 1. Hosts for the components: RATNAP01.
    ( Apr 4, 2013 5:13:43 PM ) Check if the RAF Logical Web App (LOGICAL_WEB_APP) component exists. successfully completed.
    ( Apr 4, 2013 5:13:43 PM )  - passed: Found: 1.
    ( Apr 4, 2013 5:13:43 PM ) Check if the RAF Web App (RA_FRAMEWORK_WEB_APP) components exist. successfully completed.
    ( Apr 4, 2013 5:13:43 PM )  - passed: Found: 1. Hosts for the components: RATNAP01.
    ( Apr 4, 2013 5:13:44 PM ) Check consistency of the Service Agent sets between Registry and V8_SERVICEAGENT. successfully completed.
    ( Apr 4, 2013 5:13:44 PM )  - passed: Data in Registry and database are consistent.
    ( Apr 4, 2013 5:13:45 PM ) Check consistency of the Service Agent properties between Registry and database tables (V8_SERVICEAGENT, V8_SA_PROPS). successfully completed.
    ( Apr 4, 2013 5:13:45 PM )  - passed: Data in Registry and database are consistent.
    ( Apr 4, 2013 5:13:45 PM ) Check if all required RAF properties exist under the RAF Logical Web App component. successfully completed.
    ( Apr 4, 2013 5:13:45 PM )  - passed: All required properties exist.
    ( Apr 4, 2013 5:13:45 PM ) Check if all required Workspace configuration files exist under the RAF Logical Web App component. successfully completed.
    ( Apr 4, 2013 5:13:45 PM )  - passed: All required files exist.
    ( Apr 4, 2013 5:13:46 PM ) Check if Agents are available. successfully completed.
    ( Apr 4, 2013 5:13:46 PM )  - passed: All Agents are available: Agent on ratnap01.
    ( Apr 4, 2013 5:13:46 PM ) Check if RAF Services are available. successfully completed.
    ( Apr 4, 2013 5:13:46 PM )  - passed: All RAF Services are available: RAF_AGENT_MODULE (Agent on ratnap01).
    ( Apr 4, 2013 5:13:47 PM ) Check if Repository data folder exists. successfully completed.
    ( Apr 4, 2013 5:13:47 PM )  - passed: Data file locations are valid.
    ( Apr 4, 2013 5:13:48 PM ) Check if Job Factory data folder exists. successfully completed.
    ( Apr 4, 2013 5:13:48 PM )  - passed: Data file locations are valid.
    ( Apr 4, 2013 5:13:49 PM ) Check if Service Broker data folder exists. successfully completed.
    ( Apr 4, 2013 5:13:49 PM )  - passed: Data file locations are valid.
    ( Apr 4, 2013 5:13:50 PM ) Check if Event Server data folder exists. successfully completed.
    ( Apr 4, 2013 5:13:50 PM )  - passed: Data file locations are valid.
    ( Apr 4, 2013 5:13:50 PM ) Check if every Agent is associated with some Agent Module(s). successfully completed.
    ( Apr 4, 2013 5:13:50 PM )  - passed: Every Agent is associated with some Agent Module(s).
    ( Apr 4, 2013 5:13:51 PM ) Check if every Reporting and Analysis Service is associated with some Agent Module. successfully completed.
    ( Apr 4, 2013 5:13:51 PM )  - passed: Every Reporting and Analysis Service is associated with some Agent Module.
    ( Apr 4, 2013 5:13:52 PM ) Check if every Agent Module is associated with some Agent. successfully completed.
    ( Apr 4, 2013 5:13:52 PM )  - passed: Every Agent Module is associated with some Agent.
    ( Apr 4, 2013 5:13:52 PM ) Check if every Agent Module (except IR Log) is associated with some Reporting and Analysis Service(s). successfully completed.
    ( Apr 4, 2013 5:13:52 PM )  - passed: Every Agent Module (except IR Log) is associated with some Reporting and Analysis Service(s).
    ( Apr 4, 2013 5:13:53 PM ) Check if Agent Modules and corresponding Agents belong to the same host. successfully completed.
    ( Apr 4, 2013 5:13:53 PM )  - passed: Agent Modules and corresponding Agents belong to the same host.
    ( Apr 4, 2013 5:13:56 PM ) Check if Reporting and Analysis Services and corresponding Agent Modules belong to the same host. successfully completed.
    ( Apr 4, 2013 5:13:56 PM )  - passed: Reporting and Analysis Services and corresponding Agent Modules belong to the same host.
    ( Apr 4, 2013 5:13:57 PM ) Check the possibility to login on Web Analysis Server. failed.
    ( Apr 4, 2013 5:13:57 PM )  - failed: An error occurred while running the check.
        Error:An error occurred while running the check.
    ( Apr 4, 2013 5:13:57 PM ) Check connectivity between Web Analysis Server and Essbase Server. failed.
    ( Apr 4, 2013 5:13:57 PM )  - failed: An error occurred while running the check.
        Error:An error occurred while running the check.
    ( Apr 4, 2013 5:13:58 PM ) Check connectivity between Web Analysis Server and Financial Management Server. failed.
    ( Apr 4, 2013 5:13:58 PM )  - failed: An error occurred while running the check.
        Error:An error occurred while running the check.
    ( Apr 4, 2013 5:14:20 PM ) External repository access test successfully completed.
    ( Apr 4, 2013 5:14:20 PM )  - passed: Launch external checker with next command: C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\launchChecker.bat FetchCategory ****** localhost 6800 /Sample Content
    ( Apr 4, 2013 5:14:36 PM ) External login test for IR successfully completed.
    ( Apr 4, 2013 5:14:36 PM )  - passed: Launch external checker with next command: C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\launchChecker.bat PingBQService ****** localhost 6800
    ( Apr 4, 2013 5:14:36 PM ) Financial Management Application Server Configuration successfully completed.
    ( Apr 4, 2013 5:14:36 PM )  - passed: Validating Financial Management Server registration Successful...
    ( Apr 4, 2013 5:14:50 PM ) Financial Management Service Validation failed.
    ( Apr 4, 2013 5:14:50 PM )  - failed: Verify that the Financial Management service is working.
        Error:EPMVLD-01024: The Financial Management service check failed: ERROR: Unable to CreateApplicationCAS
    ( Apr 4, 2013 5:14:52 PM ) Financial Management Web Server successfully completed.
    ( Apr 4, 2013 5:14:52 PM )  - passed: Validating Financial Management Web application connection Successful...
    ( Apr 4, 2013 5:14:54 PM ) SmartView Provider successfully completed.
    ( Apr 4, 2013 5:14:54 PM )  - passed: Validating Financial Management SmartView Provider connection Successful...
    ( Apr 4, 2013 5:14:57 PM ) LCM Provider successfully completed.
    ( Apr 4, 2013 5:14:57 PM )  - passed: Validating Financial Management LCM Provider connection Successful...
    ( Apr 4, 2013 5:15:16 PM ) Essbase Java API checker failed.
    ( Apr 4, 2013 5:15:16 PM )  - failed: Launch external checker with next command: C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\launchEssbaseJavaAPI.bat EssbaseJAPIConnect ****** RATNAP01:1423 Embedded
        Error:EPMVLD-01011: Result 1; Error message: Message was not included in output, check logs for details.
    ( Apr 4, 2013 5:15:16 PM ) Check system-jazn-data.xml file for HIT entries successfully completed.
    ( Apr 4, 2013 5:15:16 PM )  - passed: All HIT entries are present in system-jazn-data.xml
    COMP ID = oracle.EPMOHPS
    Hyperion Provider Services - Release 11.1.2.2.100.2167
    Copyright (c) 1991, 2012 Oracle and / or its affiliates. All rights reserved.
    connection mode : EMBEDDED
    essbase.properties: essbase.properties
    java System properties -DESS_ES_HOME: null
    ( Apr 4, 2013 5:15:29 PM ) Essbase server check failed.
    ( Apr 4, 2013 5:15:29 PM )  - failed: Validating Essbase Server connection to RATNAP01
        Error:Cannot connect to olap service. Cannot connect to Essbase Server at "RATNAP01:1423". Network error [10061]: Failed to connect to [RATNAP01:1423]
    ( Apr 4, 2013 5:15:37 PM ) Essbase server check using MaxL failed.
    ( Apr 4, 2013 5:15:37 PM )  - failed: Validating Essbase Server startup using MaxL command
        Error:EPMVLD-01010: Cannot connect to Essbase Server using MaxL.
    ( Apr 4, 2013 5:15:38 PM ) Module login test failed.
    ( Apr 4, 2013 5:15:38 PM )  - failed: Module test for Performance Management Architect with URL http://RATNAP01:9000/workspace/index.jsp?module=awb.awb
        Error:com.hyperion.cis.utils.BadResponseCodeException: Bad response code with POST method: 404
    ( Apr 4, 2013 5:15:38 PM ) Web Server link test failed.
    ( Apr 4, 2013 5:15:48 PM ) EnumerateDimensions failed.
    ( Apr 4, 2013 5:15:48 PM )  - failed: Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_29/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.dimeditor.EnumDimensions
        Error:EnumDimensions failed on initialization. Please check all registry information is valid and that HSS is running.
    ( Apr 4, 2013 5:15:59 PM ) EnumerateApplications failed.
    ( Apr 4, 2013 5:15:59 PM )  - failed: Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_29/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.repository.EnumApplications
        Error:EnumApplications failed on initialization. Please check all registry information is valid and that HSS is running.
    ( Apr 4, 2013 5:16:09 PM ) EnumerateDataSynchronizations failed.
    ( Apr 4, 2013 5:16:09 PM )  - failed: Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_29/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.repository.EnumDataSyncs
        Error:EnumDataSyncs failed on initialization. Please check all registry information is valid and that HSS is running.
    ( Apr 4, 2013 5:16:20 PM ) DimensionEditorLoadAdf failed.
    ( Apr 4, 2013 5:16:20 PM )  - failed: Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_29/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.dimeditor.DimEditorLoadAdf
        Error:DimEditorLoadAdf failed on initialization. Please check all registry information is valid and that HSS is running.
    ( Apr 4, 2013 5:16:29 PM ) ApplicationManagerLoadAdf failed.
    ( Apr 4, 2013 5:16:29 PM )  - failed: Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_29/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.appmanager.AppMgrLoadAdf
        Error:AppMgrLoadAdf failed on initialization. Please check all registry information is valid and that HSS is running.

  • Hyperion Reporting and Analysis

    Hello Gurus,
    So I installed Hyperion (11.1.2.2) foundation services(all componants), essbase(all componants), planning (all componants. well, it was only one componant), Reporting and Analysis framework (web application, services and common libraries. i installed only these two because hyperion planning depends on them), financial management ADM driver (chosen by default when i want to install hyperion reporting and analysis). i installed them and configured them all togather. I'm using a Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production on Windows 2008 SP2 32bits.
    Configuration of Reporting and Analysis framework failed, and that caused several problems when i ran the EPM system Diagnosis. this is what i got. Note: I'm gonna list only the errors/warnings in anything other than reporting and Analysis. as for reporting and analysis, i'm gonna list everything. sorry it's so long....
    Hyperion Foundation
    FAILED HTTP: HTTP Checking availability of HTTP context http://DC-HYPERIONT01:19000/raframework/index.jsp
    Error: com.hyperion.cis.utils.BadResponseCodeException: Bad response code with GET method: 404
    Recommended Action: Check that the application is started
    0 seconds
    EPM System Registry
    FAILED REG: Registry Next issues are present:
    LOGICAL_WEB_APP (id: fa67b59381bd8c85S4cc267951398ff60006S73df):
    "webAppType" property missed
    "context" property missed
    "port" property missed
    "SSL_Port" property missed
    "isSSL" property missed
    "host" property missed
    "" child missed
    RA_FRAMEWORK (id: fa67b59381bd8c85S4cc267951398ff60006S7bc8):
    "applicationId" property missed
    "RA_PRODUCT" parent missed
    RA_FRAMEWORK (id: fa67b59381bd8c85S4cc267951398ff60006S74c6):
    "applicationId" property missed
    "DATABASE_CONN" child missed
    Error: Checker execution failed.
    Recommended Action: Refer to the validation logs for exception details.
    Financial Reporting
    FAILED REG: Datasource Checking if datasource property exists in the registry
    Error: ORA-00942: table or view does not exist
    Recommended Action: Refer to the validation logs for exception details.
    0 seconds
    Reporting and Analysis
    FAILED CFG: Configuration Validating that configuration tasks have been completed
    Error: EPMVLD-01004: The following configuration tasks have not been completed:
    FrameworkServicesConfiguration: Configuration Failed
    Recommended Action: Attempt to configure referenced tasks
    0 seconds
    PASSED DB: Database Connectivity Checking connection to database jdbc:oracle:thin:@dc-hypdbt01.nuqulgroup.loc:1521:hybdb
    0 seconds
    PASSED SVR: Essbase Java API Launch external checker with next command: D:\install03092012\user_projects\epmsystem1\config\validation\11.1.2.0\launchEssbaseJavaAPI.bat EssbaseJAPIConnect ****** DC-HYPERIONT01:1423 Embedded
    5 seconds
    PASSED EXT: External Authentication Check Native Directory external authentication provider configuration
    0 seconds
    PASSED REG: Configuration Checking if product has only one product node in registry.
    0 seconds
    PASSED RA: Reporting and Analysis Check if Reporting and Analysis Services and corresponding Agent Modules belong to the same host.
    Reporting and Analysis Services and corresponding Agent Modules belong to the same host.
    0 seconds
    FAILED RA: Reporting and Analysis Check if all required RAF properties exist under the RAF Logical Web App component.
    Error: Some required properties are not found in the RAF Logical Web App component: WebClient.SmartPages.DefaultSmartPage.PreconfiguredCategories, WebClient.SmartPages.ColorScheme.ColorScheme1.BackgroundColor, WebClient.Applications.DAServlet.OpenNewWindow, WebClient.UserInterface.Localization.localLanguageCode, WebClient.SmartPages.ColorScheme.ColorScheme2.HeaderColor, WebClient.Cache.Objects.HeadlinesPageTTL, WebClient.SmartPages.ColorScheme.ColorScheme0.FooterColor, WebClient.Internal.Cookies.EncryptCookies, WebClient.UserInterface.PortalColor.MainFrame.General.ColorMainWizard, WebClient.SmartPages.ColorScheme.ColorScheme0.HeadingColor, WebClient.UserInterface.Localization.localCountryCode, WebClient.Cache.Domain.DomainInfoTTL, WebClient.SmartPages.ColorScheme.ColorScheme3.BCMessagesColor, WebClient.SmartPages.ColorScheme.ColorScheme2.BackgroundColor, WebClient.SmartPages.ColorScheme.ColorScheme1.Name, RCPDirectoryURL2, WebClient.Cache.Objects.CategoryCacheSize, WebClient.UserInterface.JobOutput.MIMETypeToDisplayForSQRProgramOutput, WebClient.Cache.Objects.TaskListingTTL, WebClient.Cache.Objects.CategoryTTL, SmartViewContext, WebClient.Internal.Transfer.PassDCByStream, WebClient.SmartPages.ColorScheme.ColorScheme2.FooterColor, WebClient.SmartPages.ColorScheme.ColorScheme2.LinkColor, WebClient.SmartPages.ColorScheme.ColorScheme1.BCMessagesColor, WebClient.SmartPages.ColorScheme.ColorScheme0.HeaderColor, OfficeAddinSupport, WebClient.SmartPages.ColorScheme.ColorScheme0.BackgroundColor, WebClient.SmartPages.ColorScheme.ColorScheme1.HeaderColor, WebClient.Applications.iHTML.PollingTimeSec, WebClient.SmartPages.ColorScheme.ColorScheme3.LeftColor, WebClient.Cache.Objects.CacheModifyTTL, WebClient.SmartPages.ColorScheme.ColorScheme1.LeftColor, WebClient.Cache.Objects.CacheListTTL, WebClient.UserInterface.Subscription.ShowSubscriptions, WebClient.SmartPages.ColorScheme.ColorScheme2.LeftColor, WebClient.Diagnostics.Log.Configuration, WebClient.UserInterface.JobOutput.ShowHTMLOutputForSQRPrograms, WebClient.UserInterface.Localization.ShowTimeOrder, WebClient.Applications.DAServlet.DASResponseTimeout, WebClient.Applications.DAServlet.PollingTimeSec, WebClient.UserInterface.Localization.localVariant, WebClient.SmartPages.ColorScheme.ColorScheme0.LinkColor, WebClient.UserInterface.SmartCut.ShowAsLink, WebClient.SmartPages.ColorScheme.ColorScheme3.BackgroundColor, WebClient.UserInterface.JobOutput.ShowSPFOutputForSQRPrograms, WebClient.SmartPages.ColorScheme.ColorScheme3.FontColor, WebClient.SmartPages.ColorScheme.ColorScheme3.LinkColor, WebClient.SmartPages.General.MaxNumberOfInitializedFromPublished, WebClient.Internal.Upload.MaxFileSize, WebClient.SmartPages.ColorScheme.ColorScheme2.RightColor, WebClient.SmartPages.ColorScheme.ColorScheme3.HeadingColor, WebClient.SmartPages.ColorScheme.ColorScheme1.LinkColor, WebClient.SmartPages.ColorScheme.ColorScheme1.HeadingColor, WebClient.SmartPages.ColorScheme.ColorScheme2.HeadingColor, WebClient.UserInterface.Localization.ShowDateOrder, WebClient.Cache.Objects.BrowseQueryTTL, RelatedContentProtocol, WebClient.Cache.Objects.PublishedSmartPagesQueryTTL, WebClient.CorporateWorkspage.Folder, WebClient.UserInterface.PortalColor.MainFrame.General.ColorMainFrame, WebClient.SmartPages.Publish.Location, WebClient.SmartPages.General.MaxNumberOfSmartPages, WebClient.SmartPages.ColorScheme.ColorScheme2.Name, WebClient.SmartPages.ColorScheme.ColorScheme3.Name, WebClient.SmartPages.DefaultSmartPage.DefaultColorScheme, WebClient.Cache.Objects.CacheListSize, WebClient.UserInterface.Configuration.EnableMSReportsIntegration, WebClient.SmartPages.ColorScheme.ColorScheme2.FontColor, WebClient.SmartPages.ColorScheme.ColorScheme2.BCMessagesColor, WebClient.SmartPages.ColorScheme.ColorScheme0.RightColor, WebClient.Internal.Temp.Location, WebClient.SmartPages.ColorScheme.ColorScheme0.BCMessagesColor, WebClient.Applications.iHTML.BQServiceResponseTimeout, RAFVersion, customSmartcutUrl, WebClient.UserInterface.PortalColor.MainFrame.Title.ColorMainTitleUnderline, WebClient.SmartPages.ColorScheme.ColorScheme1.FontColor, WebClient.Applications.iHTML.DiskCachePollingPeriod, WebClient.UserInterface.PortalColor.MainFrame.General.ColorMainWizardBorder, WebClient.Cache.Objects.JobTTL, WebClient.SmartPages.General.ShowHeadings, WebClient.SmartPages.ColorScheme.ColorScheme3.FooterColor, WebClient.Applications.DAServlet.ZAC, Folder0, WebClient.SmartPages.ColorScheme.ColorScheme3.RightColor, WebClient.Cache.Notifications.NotificationQueryTTL, WebClient.Internal.Cookies.KeepCookiesBetweenBrowserSessions, WebClient.SmartPages.DefaultSmartPage.ShowBookmarks, WebClient.SmartPages.DefaultSmartPage.PreconfiguredEmbeddedObjects, WebClient.Cache.Browse.JobOutputSummaryListing, WebClient.SmartPages.DefaultSmartPage.ShowExceptionsDashboard, WebClient.SmartPages.ColorScheme.ColorScheme0.Name, WebClient.UserInterface.PortalColor.MainFrame.Text.ColorMainLinkFont, WebClient.SmartPages.ColorScheme.ColorScheme3.HeaderColor, WebClient.Internal.Redirect.RedirectPolicy, WebClient.SmartPages.ColorScheme.ColorScheme0.LeftColor, WebClient.SmartPages.ColorScheme.ColorScheme1.RightColor, WebClient.UserInterface.PortalColor.MainFrame.Text.ColorMainFont, WebClient.SmartPages.ColorScheme.ColorScheme1.FooterColor, WebClient.UserInterface.Localization.Show24HourTime, WebClient.SmartPages.ColorScheme.ColorScheme0.FontColor.
    Recommended Action: Ensure that you ran the config tool and configured the RAF Web App component.
    0 seconds
    FAILED RA: Reporting and Analysis Check if the Agent (AGENT) components exist.
    Error: Components not found.
    Recommended Action: Ensure that you ran the config tool and configured the Reporting and Analysis Service component.
    0 seconds
    WARNING RA: Reporting and Analysis Checker execution failed.
    Check if RAF Services are available.
    No RAF Services (Agent Module) components found in Registry.
    0 seconds
    PASSED RA: Reporting and Analysis Check if Job Factory data folder exists.
    Data file locations are valid.
    0 seconds
    PASSED RA: Reporting and Analysis Check if every Agent Module is associated with some Agent.
    Every Agent Module is associated with some Agent.
    0 seconds
    FAILED RA: Reporting and Analysis Check if the Reporting and Analysis Setup (RA_SETUP) component exists.
    Error: Components not found.
    Recommended Action: Ensure that you ran the config tool and configured the Reporting and Analysis component.
    0 seconds
    PASSED RA: Reporting and Analysis Check if the RAF Web App (RA_FRAMEWORK_WEB_APP) components exist.
    Found: 1. Hosts for the components: DC-HYPERIONT01.
    0 seconds
    FAILED RA: Reporting and Analysis Check consistency of the Service Agent sets between Registry and V8_SERVICEAGENT.
    Error: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    Recommended Action: Ensure that you ran the config tool and configured the Reporting and Analysis Service component.
    0 seconds
    FAILED RA: Reporting and Analysis Check consistency of the Service Agent properties between Registry and database tables (V8_SERVICEAGENT, V8_SA_PROPS).
    Error: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    Recommended Action: Ensure that you ran the config tool and configured the Reporting and Analysis Service component.
    0 seconds
    PASSED RA: Reporting and Analysis Check if Agent Modules and corresponding Agents belong to the same host.
    Agent Modules and corresponding Agents belong to the same host.
    0 seconds
    WARNING RA: Reporting and Analysis Checker execution failed.
    Check if all required RAF properties exist under the Reporting and Analysis Setup component.
    The Reporting and Analysis Setup component is not found.
    0 seconds
    PASSED RA: Reporting and Analysis Check if every Agent Module (except IR Log) is associated with some Reporting and Analysis Service(s).
    Every Agent Module (except IR Log) is associated with some Reporting and Analysis Service(s).
    0 seconds
    PASSED RA: Reporting and Analysis Check if Service Broker data folder exists.
    Data file locations are valid.
    0 seconds
    FAILED RA: Reporting and Analysis Check if the Reporting and Analysis Service (RA_SERVICE) components exist.
    Error: Components not found.
    Recommended Action: Ensure that you ran the config tool and configured the Reporting and Analysis Service component.
    0 seconds
    FAILED RA: Reporting and Analysis Check if the Agent Module (AGENT_MODULE) components exist.
    Error: Components not found.
    Recommended Action: Ensure that you ran the config tool and configured the Reporting and Analysis Service component.
    0 seconds
    PASSED RA: Reporting and Analysis Check if all required Workspace configuration files exist under the RAF Logical Web App component.
    All required files exist.
    0 seconds
    WARNING RA: Reporting and Analysis Checker execution failed.
    Check if Agents are available.
    No Agent components found in Registry.
    0 seconds
    PASSED RA: Reporting and Analysis Check if every Reporting and Analysis Service is associated with some Agent Module.
    Every Reporting and Analysis Service is associated with some Agent Module.
    0 seconds
    PASSED RA: Reporting and Analysis Check if Event Server data folder exists.
    Data file locations are valid.
    0 seconds
    PASSED RA: Reporting and Analysis Check if every Agent is associated with some Agent Module(s).
    Every Agent is associated with some Agent Module(s).
    0 seconds
    PASSED RA: Reporting and Analysis Check if the RAF Logical Web App (LOGICAL_WEB_APP) component exists.
    Found: 1.
    0 seconds
    PASSED RA: Reporting and Analysis Check if Repository data folder exists.
    Data file locations are valid.
    0 seconds
    FAILED WA: Essbase connectivity Check connectivity between Web Analysis Server and Essbase Server.
    Error: An error occurred while running the check.
    Recommended Action: Ensure that: 1) Essbase Server is configured properly and started; 2) Web Analysis Web Application is configured and started.
    0 seconds
    FAILED WA: HFM connectivity Check connectivity between Web Analysis Server and Financial Management Server.
    Error: An error occurred while running the check.
    Recommended Action: Ensure that: 1) Financial Management Server is configured properly and started; 2) Web Analysis Web Application is configured and started.
    0 seconds
    FAILED WA: Login Check the possibility to login on Web Analysis Server.
    Error: An error occurred while running the check.
    Recommended Action: Ensure that Web Analysis Web Application is configured and started.
    0 seconds
    PASSED WEB: Web Application Availability of Web application context http://DC-HYPERIONT01:9000/WebAnalysis
    0 seconds
    Many Many thanks in advance,
    Zain

    Hello Krishna,
    yes, looks like i didn't have moduke 7 downloaded. however after i did and installed it, i still got the following errors that seemed to do with connectivity to RAFRAMEWORK and it's database. I am going to list errors in all modules, except for Reporting and Analysis, i'm going to post everythign else.
    Hyperion Foundation
    FAILED HTTP: HTTP Checking availability of HTTP context http://DC-HYPERIONT01:19000/raframework/index.jsp
    Error: com.hyperion.cis.utils.BadResponseCodeException: Bad response code with GET method: 404
    Recommended Action: Check that the application is started
    0 seconds
    EPM System Registry
    FAILED REG: Registry Next issues are present:
    LOGICAL_WEB_APP (id: fa67b59381bd8c85S4cc267951398ff60006S73df):
    "webAppType" property missed
    "context" property missed
    "port" property missed
    "SSL_Port" property missed
    "isSSL" property missed
    "host" property missed
    "" child missed
    RA_FRAMEWORK (id: fa67b59381bd8c85S4cc267951398ff60006S74c6):
    "applicationId" property missed
    "DATABASE_CONN" child missed
    Error: Checker execution failed.
    Recommended Action: Refer to the validation logs for exception details.
    Financial Reporting
    FAILED REG: Datasource Checking if datasource property exists in the registry
    Error: Datasource property raframeworkDatasource not found.
    Recommended Action: Fix failure manually with epmsys_registry tool.
    0 seconds
    FAILED REG: Datasource Checking if datasource property exists in the registry
    Error: Datasource JNDI property raframeworkDatasourceJNDI not found.
    Recommended Action: Fix failure manually with epmsys_registry tool.
    0 seconds
    Reporting and Analysis
    PASSED CFG: Configuration Validating that configuration tasks have been completed
    0 seconds
    PASSED DB: Database Connectivity Checking connection to database jdbc:oracle:thin:@dc-hypdbt01.nuqulgroup.loc:1521:hybdb
    0 seconds
    PASSED SVR: Essbase Java API Launch external checker with next command: D:\install03092012\user_projects\epmsystem1\config\validation\11.1.2.0\launchEssbaseJavaAPI.bat EssbaseJAPIConnect ****** DC-HYPERIONT01:1423 Embedded
    6 seconds
    PASSED EXT: External Authentication Check Native Directory external authentication provider configuration
    0 seconds
    PASSED REG: Configuration Checking if product has only one product node in registry.
    0 seconds
    PASSED RA: Reporting and Analysis Check if the RAF Web App (RA_FRAMEWORK_WEB_APP) components exist.
    Found: 1. Hosts for the components: DC-HYPERIONT01.
    0 seconds
    PASSED RA: Reporting and Analysis Check if every Agent Module (except IR Log) is associated with some Reporting and Analysis Service(s).
    Every Agent Module (except IR Log) is associated with some Reporting and Analysis Service(s).
    0 seconds
    PASSED RA: Reporting and Analysis Check if IR BI Services are available.
    All IR BI Services are available: IRBI_AGENT_MODULE (Agent on dc-hyperiont01).
    0 seconds
    PASSED RA: Reporting and Analysis Check if the Reporting and Analysis Service (RA_SERVICE) components exist.
    Found: 37.
    0 seconds
    PASSED RA: Reporting and Analysis Check if the Agent (AGENT) components exist.
    Found: 1. Hosts for the components: DC-HYPERIONT01.
    0 seconds
    FAILED RA: Reporting and Analysis Check consistency of the Service Agent properties between Registry and database tables (V8_SERVICEAGENT, V8_SA_PROPS).
    Error: There is inconsistency between Registry and V8_SERVICEAGENT for the following items: JF1, SB1, RM1, ES1.
    Recommended Action: Ensure that you ran the config tool and configured the Reporting and Analysis Service component.
    0 seconds
    PASSED RA: Reporting and Analysis Check if Service Broker data folder exists.
    Data file locations are valid.
    1 seconds
    PASSED RA: Reporting and Analysis Check if the Agent Module (AGENT_MODULE) components exist.
    Found: 6.
    0 seconds
    PASSED RA: Reporting and Analysis Check if Repository data folder exists.
    Data file locations are valid.
    1 seconds
    PASSED RA: Reporting and Analysis Check if IR Job Services are available.
    All IR Job Services are available: IRJOB_AGENT_MODULE (Agent on dc-hyperiont01).
    0 seconds
    PASSED RA: Reporting and Analysis Check if Reporting and Analysis Services and corresponding Agent Modules belong to the same host.
    Reporting and Analysis Services and corresponding Agent Modules belong to the same host.
    3 seconds
    PASSED RA: Reporting and Analysis Check if RAF Services are available.
    All RAF Services are available: RAF_AGENT_MODULE (Agent on dc-hyperiont01), RAF_AGENT_MODULE (Agent on dc-hyperiont01).
    0 seconds
    PASSED RA: Reporting and Analysis Check if IR Log Services are available.
    All IR Log Services are available: IRLOG_AGENT_MODULE (Agent on dc-hyperiont01).
    0 seconds
    PASSED RA: Reporting and Analysis Check if all required Workspace configuration files exist under the RAF Logical Web App component.
    All required files exist.
    0 seconds
    PASSED RA: Reporting and Analysis Check if every Reporting and Analysis Service is associated with some Agent Module.
    Every Reporting and Analysis Service is associated with some Agent Module.
    1 seconds
    PASSED RA: Reporting and Analysis Check consistency of the Service Agent sets between Registry and V8_SERVICEAGENT.
    Data in Registry and database are consistent.
    0 seconds
    PASSED RA: Reporting and Analysis Check if every Agent is associated with some Agent Module(s).
    Every Agent is associated with some Agent Module(s).
    0 seconds
    PASSED RA: Reporting and Analysis Check if every Agent Module is associated with some Agent.
    Every Agent Module is associated with some Agent.
    0 seconds
    FAILED RA: Reporting and Analysis Check if all required RAF properties exist under the RAF Logical Web App component.
    Error: Some required properties are not found in the RAF Logical Web App component: WebClient.SmartPages.DefaultSmartPage.PreconfiguredCategories, WebClient.SmartPages.ColorScheme.ColorScheme1.BackgroundColor, WebClient.Applications.DAServlet.OpenNewWindow, WebClient.UserInterface.Localization.localLanguageCode, WebClient.SmartPages.ColorScheme.ColorScheme2.HeaderColor, WebClient.Cache.Objects.HeadlinesPageTTL, WebClient.SmartPages.ColorScheme.ColorScheme0.FooterColor, WebClient.Internal.Cookies.EncryptCookies, WebClient.UserInterface.PortalColor.MainFrame.General.ColorMainWizard, WebClient.SmartPages.ColorScheme.ColorScheme0.HeadingColor, WebClient.UserInterface.Localization.localCountryCode, WebClient.Cache.Domain.DomainInfoTTL, WebClient.SmartPages.ColorScheme.ColorScheme3.BCMessagesColor, WebClient.SmartPages.ColorScheme.ColorScheme2.BackgroundColor, WebClient.SmartPages.ColorScheme.ColorScheme1.Name, RCPDirectoryURL2, WebClient.Cache.Objects.CategoryCacheSize, WebClient.UserInterface.JobOutput.MIMETypeToDisplayForSQRProgramOutput, WebClient.Cache.Objects.TaskListingTTL, WebClient.Cache.Objects.CategoryTTL, SmartViewContext, WebClient.Internal.Transfer.PassDCByStream, WebClient.SmartPages.ColorScheme.ColorScheme2.FooterColor, WebClient.SmartPages.ColorScheme.ColorScheme2.LinkColor, WebClient.SmartPages.ColorScheme.ColorScheme1.BCMessagesColor, WebClient.SmartPages.ColorScheme.ColorScheme0.HeaderColor, OfficeAddinSupport, WebClient.SmartPages.ColorScheme.ColorScheme0.BackgroundColor, WebClient.SmartPages.ColorScheme.ColorScheme1.HeaderColor, WebClient.Applications.iHTML.PollingTimeSec, WebClient.SmartPages.ColorScheme.ColorScheme3.LeftColor, WebClient.Cache.Objects.CacheModifyTTL, WebClient.SmartPages.ColorScheme.ColorScheme1.LeftColor, WebClient.Cache.Objects.CacheListTTL, WebClient.UserInterface.Subscription.ShowSubscriptions, WebClient.SmartPages.ColorScheme.ColorScheme2.LeftColor, WebClient.Diagnostics.Log.Configuration, WebClient.UserInterface.JobOutput.ShowHTMLOutputForSQRPrograms, WebClient.UserInterface.Localization.ShowTimeOrder, WebClient.Applications.DAServlet.DASResponseTimeout, WebClient.Applications.DAServlet.PollingTimeSec, WebClient.UserInterface.Localization.localVariant, WebClient.SmartPages.ColorScheme.ColorScheme0.LinkColor, WebClient.UserInterface.SmartCut.ShowAsLink, WebClient.SmartPages.ColorScheme.ColorScheme3.BackgroundColor, WebClient.UserInterface.JobOutput.ShowSPFOutputForSQRPrograms, WebClient.SmartPages.ColorScheme.ColorScheme3.FontColor, WebClient.SmartPages.ColorScheme.ColorScheme3.LinkColor, WebClient.SmartPages.General.MaxNumberOfInitializedFromPublished, WebClient.Internal.Upload.MaxFileSize, WebClient.SmartPages.ColorScheme.ColorScheme2.RightColor, WebClient.SmartPages.ColorScheme.ColorScheme3.HeadingColor, WebClient.SmartPages.ColorScheme.ColorScheme1.LinkColor, WebClient.SmartPages.ColorScheme.ColorScheme1.HeadingColor, WebClient.SmartPages.ColorScheme.ColorScheme2.HeadingColor, WebClient.UserInterface.Localization.ShowDateOrder, WebClient.Cache.Objects.BrowseQueryTTL, RelatedContentProtocol, WebClient.Cache.Objects.PublishedSmartPagesQueryTTL, WebClient.CorporateWorkspage.Folder, WebClient.UserInterface.PortalColor.MainFrame.General.ColorMainFrame, WebClient.SmartPages.Publish.Location, WebClient.SmartPages.General.MaxNumberOfSmartPages, WebClient.SmartPages.ColorScheme.ColorScheme2.Name, WebClient.SmartPages.ColorScheme.ColorScheme3.Name, WebClient.SmartPages.DefaultSmartPage.DefaultColorScheme, WebClient.Cache.Objects.CacheListSize, WebClient.UserInterface.Configuration.EnableMSReportsIntegration, WebClient.SmartPages.ColorScheme.ColorScheme2.FontColor, WebClient.SmartPages.ColorScheme.ColorScheme2.BCMessagesColor, WebClient.SmartPages.ColorScheme.ColorScheme0.RightColor, WebClient.Internal.Temp.Location, WebClient.SmartPages.ColorScheme.ColorScheme0.BCMessagesColor, WebClient.Applications.iHTML.BQServiceResponseTimeout, RAFVersion, customSmartcutUrl, WebClient.UserInterface.PortalColor.MainFrame.Title.ColorMainTitleUnderline, WebClient.SmartPages.ColorScheme.ColorScheme1.FontColor, WebClient.Applications.iHTML.DiskCachePollingPeriod, WebClient.UserInterface.PortalColor.MainFrame.General.ColorMainWizardBorder, WebClient.Cache.Objects.JobTTL, WebClient.SmartPages.General.ShowHeadings, WebClient.SmartPages.ColorScheme.ColorScheme3.FooterColor, WebClient.Applications.DAServlet.ZAC, Folder0, WebClient.SmartPages.ColorScheme.ColorScheme3.RightColor, WebClient.Cache.Notifications.NotificationQueryTTL, WebClient.Internal.Cookies.KeepCookiesBetweenBrowserSessions, WebClient.SmartPages.DefaultSmartPage.ShowBookmarks, WebClient.SmartPages.DefaultSmartPage.PreconfiguredEmbeddedObjects, WebClient.Cache.Browse.JobOutputSummaryListing, WebClient.SmartPages.DefaultSmartPage.ShowExceptionsDashboard, WebClient.SmartPages.ColorScheme.ColorScheme0.Name, WebClient.UserInterface.PortalColor.MainFrame.Text.ColorMainLinkFont, WebClient.SmartPages.ColorScheme.ColorScheme3.HeaderColor, WebClient.Internal.Redirect.RedirectPolicy, WebClient.SmartPages.ColorScheme.ColorScheme0.LeftColor, WebClient.SmartPages.ColorScheme.ColorScheme1.RightColor, WebClient.UserInterface.PortalColor.MainFrame.Text.ColorMainFont, WebClient.SmartPages.ColorScheme.ColorScheme1.FooterColor, WebClient.UserInterface.Localization.Show24HourTime, WebClient.SmartPages.ColorScheme.ColorScheme0.FontColor.
    Recommended Action: Ensure that you ran the config tool and configured the RAF Web App component.
    0 seconds
    PASSED RA: Reporting and Analysis Check if Job Factory data folder exists.
    Data file locations are valid.
    1 seconds
    PASSED RA: Reporting and Analysis Check if IR DAS Services are available.
    All IR DAS Services are available: IRDAS_AGENT_MODULE (Agent on dc-hyperiont01).
    0 seconds
    PASSED RA: Reporting and Analysis Check if Event Server data folder exists.
    Data file locations are valid.
    1 seconds
    PASSED RA: Reporting and Analysis Check if the Interactive Reporting Product (INTERACTIVE_REPORTING_PRODUCT) component exists.
    Found: 1.
    0 seconds
    FAILED RA: Reporting and Analysis Check if the Reporting and Analysis Setup (RA_SETUP) component exists.
    Error: Found: 2, which is more than 1. This indicates some problem.
    Recommended Action: Ensure that you ran the config tool and configured the Reporting and Analysis component.
    0 seconds
    PASSED RA: Reporting and Analysis Check if all required RAF properties exist under the Reporting and Analysis Setup component.
    All required properties exist.
    0 seconds
    PASSED RA: Reporting and Analysis Check if the RAF Logical Web App (LOGICAL_WEB_APP) component exists.
    Found: 1.
    0 seconds
    PASSED RA: Reporting and Analysis Check if Agent Modules and corresponding Agents belong to the same host.
    Agent Modules and corresponding Agents belong to the same host.
    0 seconds
    PASSED RA: Reporting and Analysis Check if Agents are available.
    All Agents are available: Agent on dc-hyperiont01.
    0 seconds
    PASSED SDKC: SDK checker Launch external checker with next command: D:\install03092012\user_projects\epmsystem1\config\validation\11.1.2.0\launchChecker.bat PingBQService ****** localhost 6800
    11 seconds
    PASSED SDKC: SDK checker Launch external checker with next command: D:\install03092012\user_projects\epmsystem1\config\validation\11.1.2.0\launchChecker.bat FetchCategory ****** localhost 6800 /Sample Content
    16 seconds
    FAILED WA: Essbase connectivity Check connectivity between Web Analysis Server and Essbase Server.
    Error: An error occurred while running the check.
    Recommended Action: Ensure that: 1) Essbase Server is configured properly and started; 2) Web Analysis Web Application is configured and started.
    0 seconds
    FAILED WA: HFM connectivity Check connectivity between Web Analysis Server and Financial Management Server.
    Error: An error occurred while running the check.
    Recommended Action: Ensure that: 1) Financial Management Server is configured properly and started; 2) Web Analysis Web Application is configured and started.
    0 seconds
    FAILED WA: Login Check the possibility to login on Web Analysis Server.
    Error: An error occurred while running the check.
    Recommended Action: Ensure that Web Analysis Web Application is configured and started.
    1 seconds
    PASSED WEB: Web Application Availability of Web application context http://DC-HYPERIONT01:9000/WebAnalysis
    0 seconds
    Many many thanks in advance,
    Zain

  • Error: starting satellite services

    Hi all,
    When I install Ops Center on Linux CentOS 5.10 for management Sun Oracle Server. I have issue with last step of installation script ". I have error messsage below :
                                                   Ops Center Enterprise Controller Installer
                                                         (version 11.1.0.1536 on Linux)
    1. Check for installation prerequisites.                                                                                    [Completed]
    2. Check that required RPM packages are present.                                                                            [Completed]
    3. Configure file systems.                                                                                                  [Completed]
    4. Install Agent components.                                                                                                [Completed]
    5. Create Deployable Proxy Bundles.                                                                                         [Completed]
    6. Add users.                                                                                                               [Completed]
    7. Install prerequisite packages.                                                                                           [Completed]
    8. Install application packages.                                                                                            [Completed]
    9. Run postinstall tasks.                                                                                                   [Completed]
    10. Install IPMI tool.                                                                                                       [Completed]
    11. Initialize database.                                                                                                     [Completed]
    12. Install Service container components.                                                                                    [Completed]
    13. Install Core Channel components.                                                                                         [Completed]
    14. Install Proxy Core components.                                                                                           [Completed]
    15. Install Enterprise Controller components.                                                                                [Completed]
    16. Install Update Connection - Enterprise.                                                                                  [Completed]
    17. Install Ops Center BUI components.                                                                                       [Completed]
    18. Install OS provisioning components.                                                                                      [Completed]
    19. Initialize and start services.                                                                                       [Not Completed]
    Failed Step:  Initialize and start services.
    The following is a portion of the installer
    log which may indicate the cause of the error.
    If this does not indicate the cause of the
    error, you will need to view the full log
    file. More information on how to do that is
    available below.
    INFO: Converting satellite SMF manifest file (/opt/sun/xvmoc/lib/svc/satellite-ajaxterm-svc.xml)
    INFO: Converting satellite SMF manifest file (/opt/sun/xvmoc/lib/svc/proxy-base-svc.xml)
    INFO: Converting satellite SMF manifest file (/opt/sun/xvmoc/lib/svc/satellite-xvmoc-svc.xml)
    INFO: Converting satellite SMF manifest file (/opt/sun/xvmoc/lib/svc/proxy-xvmoc-svc.xml)
    INFO: starting new satellite SMF services
    Can't exec "/opt/sun/xvmoc/bin/satadm": No such file or directory at /root/xvmoc_full_bundle/Linux_i686/Product//installer/Modules/util.pm line 1619.
    Use of uninitialized value in concatenation (.) or string at /root/xvmoc_full_bundle/Linux_i686/Product//installer/Modules/util.pm line 1631.
    Error: starting satellite services
    Command: /opt/sun/xvmoc/bin/satadm start -v -w
    Exit code: 72057594037927935
    Signal: 255
    Output:
    Please fix the problem and then try this step again.
    For a full log of the failed install see the file: /var/tmp/installer.log.21123.
    t. Try this step again (correct the failure before proceeding)
    x. Exit
    Enter selection: (t/x)
    How do I fix this issue, thanks for any help!
    Regards,.

    Hi
    Go to deploy service in visual administrator and start your application.
    instance--serverservices--
    deploy.
    Or
    In visual administrator
    instance--serverservices--
    web service container and start the application.
    Reward points if useful

  • Templates/ovf upload

    Hi,
        How to upload templates/ovf files into vFabric Data Director "Base DB templates" .

    The vFDD distribution includes .ova/tar files for the actual Data Director appliance and for 4 different Base VMs.
    You deploy the Base VMs you want into the system resource pool you create.  (The system resource pool will be used in the creation of the system resource bundle in DD)
    The four templates are:
    1) vpostgres 9.0  includes SUSE OS, vpostgres9.0 install and DD Agent components
    2) vpostgres 9.1  includes SUSE OS, vpostgres9.1 install and DD Agent components
    3) SUSE VM to be used for Oracle Install.   Includes SUSE OS, DD Agent components and an install script to do a silent Oracle install from your Oracle binaries
    4) Blank VM for use with RHEL/Oracle.  Includes VM configured with correct vmdks and Nics.  ISO with cfg to repack RHEL with needed kernel parameters and disk layout.  Install script to do a silent Oracle install from your Oracle Binaries.  The process is to use the cfg files to repack your RHEL binaries, do the OS install into this VM and then run the silent install for Oracle.   This process is necessary because we cannot ship RHEL or Oracle with our distribution.  The next release will simplify this by making it a UI driven process.

  • Can't acknowledge alarms on some clients

    With certain clients, it appears there is full functionality (load/unload modules, monitor, etc.) with the exception of acknowledging alarms. When an attempt is made to acknowledge an alarm, the error message is "...No response from agent."
    Any help is greatly appreciated!
    J. Holly

    Keep in mind when you click on the that alarm tab to are not talking to the agent, but the SunMC backend at the servber layer. Most of the time this issue is fixed by placing the server in the agent's host file and the agent in the server's host file and using files before nis on both....console as well.

Maybe you are looking for