Cloud Control "Backend WLS or EM application seems to be down."

Question

Greetings. Attempting to use this tool on a Windos system for a POC. When I attempt to start CC I get the message posted above. Everything I'm reading leads me to believe I need to try and attempt OMS, which I have done, and the output is posted below. Can someone please advise on where I should go from here?
Thanks!
C:\Oracle\middleware\oms\BIN>emctl start oms
Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
   Oracle Enterprise Manager 10g Database Control commands:
        emctl start | stop dbconsole
        emctl status | secure | setpasswd dbconsole
        emctl config dbconsole -heap_size <size_value> -max_perm_size <size_valu
e>
       emctl status agent
       emctl status agent -secure [-omsurl <http://<oms-hostname>:<oms-unsecure-
port>/em/*>]
       emctl getversion
       emctl reload | upload | clearstate | getversion agent
       emctl reload agent dynamicproperties [<Target_name>:<Target_Type>]....
       emctl config agent <options>
       emctl config agent updateTZ
       emctl config agent getTZ
       emctl resetTZ agent
       emctl config agent credentials [<Target_name>[:<Target_Type>]]
       emctl gensudoprops
       emctl clearsudoprops
Blackout Usage :
       emctl start blackout <Blackoutname> [-nodeLevel] [<Target_name>[:<Target_
Type>]].... [-d <Duration>]
       emctl stop blackout <Blackoutname>
       emctl status blackout [<Target_name>[:<Target_Type>]]....
The following are valid options for blackouts
<Target_name:Target_type> defaults to local node target if not specified.
If -nodeLevel is specified after <Blackoutname>,the blackout will be applied to
all targets and any target list that follows will be ignored.
Duration is specified in [days] hh:mm
        emctl getemhome
        emctl ilint
Em Key Commands Usage :
emctl config emkey -emkeyfile <emkey.ora path> [-force] [-sysman_pwd <sysman pas
sword>]
emctl config emkey -emkey [-emkeyfile <emkey.ora path>] [-force] [-sysman_pwd <s
ysman password>]
emctl config emkey -repos [-emkeyfile <emkey.ora path>] [-force] [-sysman_pwd <s
ysman password>]
emctl config emkey -remove_from_repos [-sysman_pwd <sysman password>]
emctl config emkey -copy_to_repos [-sysman_pwd <sysman password>]
emctl status emkey [-sysman_pwd <sysman password>]
Secure DBConsole Usage :
emctl secure dbconsole -sysman_pwd <sysman password> [-passwd_file <abs file loc
>]
        [-host <slb hostname>] [-sid <service name>] [-reset] [-secure_port <sec
ure_port>]
        [-root_dc <root_dc>] [-root_country <root_country>] [-root_state <root_s
tate>] [-root_loc <root_loc>]
        [-root_org <root_org>] [-root_unit <root_unit>] [-root_email <root_email
>]
        [-wallet <wallet loc>] [-wallet_pwd <wallet pwd>] [-trust_certs_loc <cer
ts loc>]
emctl secure status dbconsole
Register Targettype Usage :
emctl register oms targettype [-o <Output filename>] <XML filename> <rep user> <
rep passwd> <rep host> <rep port> <rep sid> OR
emctl register oms targettype [-o <Output filename>] <XML filename> <rep user> <
rep passwd> <rep connect descriptor>
C:\Oracle\middleware\oms\BIN>

Answer 1

Hi Chris,
The error "Backend WLS or EM application seems to be down." is typically seen if we have problem with resource at repos DB or OMS side
Do the following
1. Re-start the repository database and verify that a connection can be made to the 'sysman' schema in the database via the listener.
2. Re-start the OMS:
set ORACLE_HOME=C:\Oracle\middleware\oms\
set PATH=%PATH%;C:\Oracle\middleware\oms\bin
cd <OMS_HOME>\bin
emctl stop oms -all
emctl start oms
Regards,
Rahul