Error with Server repository Mobile utility WSH

Similar Questions

• Getting error when installing repository creation utility (RCU).

  Hello
  
  During the installation of the remote control, I was getting the Error Invalid Username/password on the database connection details screen when I give a Userid sys. on the database connection details screen, I tried to login with the user sys but failed so I used the user of the system, and it connects.
  Then on screen components, I was getting the error below.
  
  UCR-6083: impossible - check requirement prerequisites for the selected item: ORAESS
  Refer to the journal of the RCUS to /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for more details.
  Try to connect as a user not SYSDBA. User must have SYSDBA privileges to properly load the schema of the ESS.
  
  RCU - 6092:Component validation selection failed. Please refer to connect to /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for more details.
  
  I don't know why I am unable to connect with the sys user, I give the password. Now, I changed the password but still can't connect sys.
  Please see the link below.
  
  http://download.Oracle.com/docs/CD/E12839_01/ doc.1111 /e14259/rcu_screens.htm
  
  Please suggest something.
  
  -The log file error-
  
  2009-12-22 16:46:06.904 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: hostname: cicl - 11 g
  2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: OSINFO: i386 2.6.18 - 164.6.1.el5 Linux
  2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: JREINFO: 1.6.0_14/u01/app/oracle/rcuHome/jdk/jre
  2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: username: oracle
  2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: USERDIR: / u01/app/oracle/rcuHome/bin
  2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: user country: U.S.
  2009-12-22 16:46:06.912 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: the user's language: en
  2009-12-22 16:46:06.913 NOTIFICATION rcu: oracle.sysman.assistants.common.util.LoggingManager::initialize: Java class path: /u01/app/oracle/rcuHome/jlib/rcu.jar:/u01/app/oracle/rcuHome/jlib/share.jar:/u01/app/oracle/rcuHome/jlib/help-share.jar:/u01/app/oracle/rcuHome/jlib/ohj.jar:/u01/app/oracle/rcuHome/jlib/orai18n-mapping.jar:/u01/app/oracle/rcuHome/lib/xmlparserv2.jar:/u01/app/oracle/rcuHome/jdbc/lib/ojdbc5.jar:/u01/app/oracle/rcuHome/jdbc/lib/ojdbc14.jar:/u01/app/oracle/rcuHome/jlib/jewt4.jar:/u01/app/oracle/rcuHome/jlib/ojdl.jar:/u01/app/oracle/rcuHome/modules/oracle.odl_11.1.1/ojdl.jar:/u01/ app/oracle/rcuHome/jlib/SchemaVersion.jar:/u01/app/oracle/rcuHome/jlib/wlsqlserver.jar:/u01/app/oracle/rcuHome/jlib/wlbase.jar:/u01/app/oracle/rcuHome/jlib/wlutil.jar:/u01/app/oracle/rcuHome/jlib/com.bea.core.weblogic.workmanager_1.6.0.0.jar:/u01/app/oracle/rcuHome/jlib/com.bea.core.weblogic.workmanager_1.7.0.0.jar:/u01/app/oracle/rcuHome/jlib/wldb2.jar:/u01/app/oracle/rcuHome/jlib/help-share.jar:/u01/app/oracle/rcuHome/jlib/ohj.jar:/u01/app/oracle/rcuHome/jlib/oracle_ice.jar:/u01/app/oracle/rcuHome/jlib/rcuhelp.jar:/u01/app/oracle/rcuHome/jlib/rcuhelppages.jar:/u01/app/oracle/rcuHome/ assistants/opca/jlib/opca.jar:/u01/app/oracle/rcuHome/portal/jlib/ptlshare.jar:/u01/app/oracle/rcuHome/jlib/ldapjclnt11.jar:/u01/app/oracle/rcuHome/jlib/commons-collections-3.1.jar:/u01/app/oracle/rcuHome/jlib/commons-dbcp-1.2.1.jar:/u01/app/oracle/rcuHome/jlib/commons-logging.jar:/u01/app/oracle/rcuHome/jlib/commons-pool-1.2.jar:/u01/app/oracle/rcuHome/jlib/quartz-1.6.0.jar:/u01/app/oracle/rcuHome/jlib/jta.jar:/u01/app/oracle/rcuHome/jlib/xml.jar:/u01/app/oracle/rcuHome/jlib/iam-platform-utils.jar:/u01/app/oracle/rcuHome/jlib/iam-platform-authz-service.jar:/u01/app/oracle/rcuHome/jlib/iam-features-identity.zip:/u01/app/oracle/ rcuHome/jlib/iam-features-configservice.zip:/u01/app/oracle/rcuHome/jlib/jps-api.jar:/u01/app/oracle/rcuHome/jlib/jps-common.jar:/u01/app/oracle/rcuHome/jlib/jps-ee.jar:/u01/app/oracle/rcuHome/jlib/jps-internal.jar:/u01/app/oracle/rcuHome/jlib/jps-manifest.jar:/u01/app/oracle/rcuHome/jlib/MicroSM.jar:/u01/app/oracle/rcuHome/jlib/javax.persistence_1.0.0.0_1-0-2.jar:/u01/app/oracle/rcuHome/jlib/org.eclipse.persistence_1.0.0.0_1-1-0.jar:/u01/app/oracle/rcuHome/jlib/identitystore.jar:/u01/app/oracle/rcuHome/jlib/jps-unsupported-api.jar:/u01/app/oracle/rcuHome/jlib/pd-internal.jar
  2009-12-22 16:46:06.913 NOTIFICATION rcu : oracle.sysman.assistants.common.util.LoggingManager::initialize : chemin de la bibliothèque Java : /u01/app/oracle/rcuHome/jdk/jre/lib/i386/client : / u01/app/oracle/rcuHome/jdk/jre/lib/i386 : / u01/app/oracle/rcuHome/jdk/jre /... /lib/i386:/u01/app/oracle/rcuHome/lib32:/u01/app/oracle/rcuHome/network/lib32:/u01/app/oracle/rcuHome/lib:/u01/app/oracle/rcuHome/network/lib:/u01/app/oracle/product/11.2.0/network/lib:/u01/app/oracle/product/11.2.0/jdbc/lib:/u01/app/oracle/product/11.2.0/lib:/usr/lib:/ usr/local/lib: / usr/java/packages/lib/i386: / lib: / usr/lib
  2009-12-22 16:46:06.913 NOTIFICATION rcu: oracle.sysman.assistants.rcu.Rcu::execute: launch RCU.
  2009-12-22 16:46:06.916 NOTIFICATION rcu: oracle.sysman.assistants.rcu.Rcu::execute: InteractiveRCUModel of creation
  2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager: < init >: basic URL: file:///u01/app/oracle/rcuHome/rcu/config/
  2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager: < init >: ComponentInfo xml location: /u01/app/oracle/rcuHome/rcu/config/ComponentInfo.xml
  2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager: < init >: xml storage location: /u01/app/oracle/rcuHome/rcu/config/Storage.xml
  2009-12-22 16:46:07.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager: < init >: DTD Validation: true
  2009-12-22 16:46:07.891 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.RCUCommandLineParser::process: processing command line...
  2009-12-22 16:46:39.363 NOTIFICATION rcu: oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine::connect: the connection to the database: user: System, role: Normal, connectString: (description = (address = (host = cicl - 11 g)(protocol=tcp) (port = 1521)) (connect_data = (service_name = DEV11G) (server = dedicated)))
  2009-12-22 16:46:40.515 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: execution of task: initialization of metadata repository configuration
  2009-12-22 16:46:40.515 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = INIT_META_DATA
  2009-12-22 16:46:40.704 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: AS_COMMON
  2009-12-22 16:46:40.707 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: MDS
  2009-12-22 16:46:40.713 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: MDS
  2009-12-22 16:46:40.714 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: MDS
  2009-12-22 16:46:40.716 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: IAU
  2009-12-22 16:46:40.720 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: ORAESS
  2009-12-22 16:46:40.721 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: IDM
  2009-12-22 16:46:40.721 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: OID
  2009-12-22 16:46:40.723 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: OIF
  2009-12-22 16:46:40.732 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: OWLCS
  2009-12-22 16:46:40.733 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: ORASDPXDMS
  2009-12-22 16:46:40.735 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: ORASDPSDS
  2009-12-22 16:46:40.759 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: ORASDPLS
  2009-12-22 16:46:40.760 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: SOA
  2009-12-22 16:46:40.761 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: SOAINFRA
  2009-12-22 16:46:40.762 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: SOAINFRA
  2009-12-22 16:46:40.762 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: SOAINFRA
  2009-12-22 16:46:40.763 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: BAM
  2009-12-22 16:46:40.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: ORASDPM
  2009-12-22 16:46:40.768 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: ORASDPM
  2009-12-22 16:46:40.769 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: ORASDPM
  2009-12-22 16:46:40.770 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: WEBCENTER_SUITE
  2009-12-22 16:46:40.771 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: WEBCENTER
  2009-12-22 16:46:40.771 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: WEBCENTER
  2009-12-22 16:46:40.772 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: WEBCENTER
  2009-12-22 16:46:40.774 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: PORTLET
  2009-12-22 16:46:40.776 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: PORTLET
  2009-12-22 16:46:40.777 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: PORTLET
  2009-12-22 16:46:40.778 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: CONTENTSERVER
  2009-12-22 16:46:40.778 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: CONTENTSERVER
  2009-12-22 16:46:40.779 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: CONTENTSERVER
  2009-12-22 16:46:40.783 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: DISCUSSIONS
  2009-12-22 16:46:40.784 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: DISCUSSIONS
  2009-12-22 16:46:40.785 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: DISCUSSIONS
  2009-12-22 16:46:40.786 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: DISCUSSIONS_CRAWLER
  2009-12-22 16:46:40.791 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: DISCUSSIONS_CRAWLER
  2009-12-22 16:46:40.794 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: WIKI
  2009-12-22 16:46:40.795 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: WIKI
  2009-12-22 16:46:40.795 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: WIKI
  2009-12-22 16:46:40.796 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently Parsing component: PORTAL_BI
  2009-12-22 16:46:40.797 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: PORTAL
  2009-12-22 16:46:40.800 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.ComponentInfoHandler::startElement: Curently component analysis: DISCOVERER
  2009-12-22 16:46:40.821 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseXmlData: XML Document: /u01/app/oracle/rcuHome/rcu/config/ComponentInfo.xml is valid
  2009-12-22 16:46:40.835 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: MDS
  2009-12-22 16:46:40.843 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//mds/mds.xml is valid
  2009-12-22 16:46:40.852 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: IAU
  2009-12-22 16:46:40.857 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/iau/iau.xml is valid
  2009-12-22 16:46:40.864 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: ORAESS
  2009-12-22 16:46:40.876 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//ess/ess.xml is valid
  2009-12-22 16:46:40.883 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: OID
  2009-12-22 16:46:40.886 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//oid/oid.xml is valid
  2009-12-22 16:46:40.891 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: OIF
  2009-12-22 16:46:40.898 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//oif/oif.xml is valid
  2009-12-22 16:46:40.904 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: ORASDPXDMS
  2009-12-22 16:46:40.907 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commspresence/commspresence.xml is valid
  2009-12-22 16:46:40.915 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: ORASDPSDS
  2009-12-22 16:46:40.932 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commssds/commssds.xml is valid
  2009-12-22 16:46:40.938 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: ORASDPLS
  2009-12-22 16:46:40.939 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//commsls/commsls.xml is valid
  2009-12-22 16:46:40.945 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: SOAINFRA
  2009-12-22 16:46:40.950 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//soainfra/soainfra.xml is valid
  2009-12-22 16:46:40.955 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: BAM
  2009-12-22 16:46:40.958 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//bam/bam.xml is valid
  2009-12-22 16:46:40.963 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: ORASDPM
  2009-12-22 16:46:40.975 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//sdpm/sdpm.xml is valid
  2009-12-22 16:46:40.981 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: WEBCENTER
  2009-12-22 16:46:40.991 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//webcenter/webcenter.xml is valid
  2009-12-22 16:46:40.998 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: PORTLET
  2009-12-22 16:46:41.006 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//portlet/portlet.xml is valid
  2009-12-22 16:46:41.011 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: CONTENTSERVER
  2009-12-22 16:46:41.021 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/contentserver/contentserver.xml is valid
  2009-12-22 16:46:41.024 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: DISCUSSIONS
  2009-12-22 16:46:41.030 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//jive/jive.xml is valid
  2009-12-22 16:46:41.040 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: DISCUSSIONS_CRAWLER
  2009-12-22 16:46:41.048 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//jive-crawler/jive-crawler.xml is valid
  2009-12-22 16:46:41.052 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: WIKI
  2009-12-22 16:46:41.056 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration//wiki/wiki.xml is valid
  2009-12-22 16:46:41.063 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: PORTAL
  2009-12-22 16:46:41.065 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/portal/portal.xml is valid
  2009-12-22 16:46:41.070 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.handlers.RepositoryConfigHandler::startElement: Curently analysis repository Config data component: DISCOVERER
  2009-12-22 16:46:41.073 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseRepositoryConfigData: XML Document: /u01/app/oracle/rcuHome/rcu/integration/dc/discoverer.xml is valid
  2009-12-22 16:46:41.108 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.xmldata.RepositoryConfigManager::parseStorageData: XML Document: /u01/app/oracle/rcuHome/rcu/config/Storage.xml is valid
  2009-12-22 16:46:41.452 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: turnaround time for initialization of configuration metadata repository: 937 milliseconds
  2009-12-22 16:46:41.464 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: execution of task: get the properties of the specified database
  2009-12-22 16:46:41.464 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = PREREQ_QUERY_DATABASE
  2009-12-22 16:46:41.498 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: lead time to get the properties of the specified database: 34 milliseconds
  2009-12-22 16:46:41.514 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: execution of task: obligation of verification for the specified database
  2009-12-22 16:46:41.514 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = PREREQ_GLOBAL_CHECK
  2009-12-22 16:46:41.557 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: lead time for the requirement of verification for the specified database: 43 milliseconds
  2009-12-22 16:46:41.572 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: task execution: run before create operations
  2009-12-22 16:46:41.573 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.CustomCompManager::getActionList: CustomCompManager.getActionList: CUSTOM_COMP_PRELOAD_SETUP
  2009-12-22 16:46:41.579 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.AbstractCompTask::execute: ValidationRule result was false. Jump action: oracle.ias.version.SchemaVersionUtil:utilCreateRegistryAndCopyData
  2009-12-22 16:46:41.582 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.AbstractCompTask::execute: ValidationRule result was false. Jump action: oracle.ias.version.SchemaVersionUtil:utilCreateRegistryTable
  2009-12-22 16:46:41.582 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: lead time to run before the operations of creation: 9 milliseconds
  2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: execution of task: Metadata Services
  2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = MDS
  2009-12-22 16:46:55.687 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: from prereq check component
  2009-12-22 16:46:55.722 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: turnaround time for metadata Services: 35 milliseconds
  2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: execution of task: Services of Audit
  2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = IAU
  2009-12-22 16:46:55.727 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: from prereq check component
  2009-12-22 16:46:55.761 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: lead time for the Services of Audit: 34 milliseconds
  2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: tasks: business Scheduler Service
  2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: Prereq taskId = ORAESS
  2009-12-22 16:46:55.766 NOTIFICATION rcu: oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator::executePrereqTask: from prereq check component
  2009-12-22 16:46:55.773 rcu ERROR: oracle.sysman.assistants.rcu.backend.task.PrereqTask::execute: Prereq evaluation failed
  oracle.sysman.assistants.rcu.backend.validation.PrereqException: UCR-6083: impossible - check requirement prerequisites for the selected item: ORAESS
  Refer to the journal of the RCUS to /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for more details.
  at oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator.executePrereqTask(PrereqEvaluator.java:642)
  at oracle.sysman.assistants.rcu.backend.task.PrereqTask.execute(PrereqTask.java:68)
  at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:303)
  at java.lang.Thread.run(Thread.java:619)
  
  2009-12-22 16:46:55.773 rcu ERROR: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: UCR failed
  oracle.sysman.assistants.common.task.TaskExecutionException: UCR-6083: impossible - check requirement prerequisites for the selected item: ORAESS
  Refer to the journal of the RCUS to /u01/app/oracle/logdir.2009-12-22_16-46/rcu.log for more details.
  Try to connect as a user not SYSDBA. User must have SYSDBA privileges to properly load the schema of the ESS.
  
  at oracle.sysman.assistants.rcu.backend.task.PrereqTask.execute(PrereqTask.java:76)
  at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:303)
  at java.lang.Thread.run(Thread.java:619)
  
  Published by: yousufpaya on December 22, 2009 19:31

  Hi yousuf;

  Please follow below and see its useful for your question:
  http://soadev.blogspot.com/2009_07_01_archive.html ( part: error in the running database repository creation Utility (RCU) using Oracle XE )

  Check also:
  http://forums.tangosol.com/forums/thread.jspa?threadID=930952&TSTART=60 (post Joaanas)

  Respect of
  HELIOS

• Error checking DELL Repository Manager signature

  Members of the Forum-

  I get an error with Dell Repository Manager 1.4.104 trying to create my first deposit.  I choose Create-> New name the repository and then select repository Dell Online (ftp.dell.com) as my source repository.  When I click Next, I get the following error: "error loading repository.  Check digital signature to 'ftp://ftp.dell.com/catalog/Catalog.cab' error' ideas about what causes this error?  I can access the FTP site from the computer that I use the repository Manager, so I'm pretty sure that it isn't a problem with the network.

  Thank you

  James

  I must apologize for the problems you are having. Not excuses, but we had the "perfect storm" internally with some elements and its been interesting to say the least. I promise you, we are working on this literally around the clock for this to be resolved. I was hoping I could get the steps you follow for this to fail, end to end so I can reproduce here. As I type this, I'm importing the catalog 9Gig together to see where issues can be always appearing.

  I couldn't make you, who clears the cache of your Certificate Revocation list? You must close all applications before running the command.  from a command prompt run as Administrator: certutil - urlcache * delete

  Then repeat the import/export. I tried to import only single file as part of a bundle, he correctly imported and exported to the SUU directory correctly. I did it on my system and a newly installed system, and it worked perfectly.

• my windows server keeps flashing upward with errors with security

  my windows server keeps flashing upward with errors with security

  I suggest that you reinstall the operating system as there is a Setup error.

• Error offline - we are sorry, but there was a communication error with the server. Please try again and if the problem persists, contact Adobe Techincal Suport...  (INVALID_QUERY: XMLList object)?

  After a number of years of service, my Adobe Premiere CS4 gives me the following error message:

  Error offline - we are sorry, but there was a communication error with the server. Please try again and if the problem persists, contact Adobe Technical Support...  (INVALID_QUERY: XMLList object).

  I use this software on an old Dell desktop computer to two year with many members and drive.  It is a stand-alone application, not connected to a server.

  Anyone have any ideas on how to solve this problem?

  I think it has to do with the central resource is no longer supported.  Everything works OK if you ignore the message?

• communication error with the server. callback failed for the data entry page

  Hello
  
  We have recently applied the corrective update EMP on EMP 11.1.2.0 111.2.1.
  We have following the architecture,
  
  database server: sql server 2005
  Server Foundation (OS = windows server 2008): HSS, EPMA, Manager Calc, EAS, EIS, provider's server, planning
  Essbase Server (OS = windows server 2008): essbase
  
  After you apply the patching EMP 11.1.2.1, we apply after Electrodes for IE 9 compactibility i.e EMP 11.1.2.1.600 patches
  
  1. patch 14119724 (Workspace)
  2 14142678 patch (Shared services)
  3 patch 14224664 (EPMA)
  4 patch 14464109 (planning)
  
  After you apply above patches, all users get error when opening planning web form through the workspace of all client computer.
  
  "* error communication with the server. callback failed for the data entry page. "
  
  
  
  
  When restore us only planning patch 14464109 , issue of "communication error with the server. callback failed for the data entry page "get resolved for all users, but failed for a single user IE"user xyz" "
  
  the user xyz have OS = windows 7 and IE 8
  user xyz can take foundation server RDP can open any form of planning successfully in vain get when doing the basic machine.
  
  I have following question:
  1. Why do we get error "error communicating with the server. callback failed for the data entry page"after you apply the fixes to IE9
  
  2. after cancellation all patches or planning one patch, why the user xyz always get the error but not other users
  
  
  Thanks in advance
  
  Published by: 922755 on June 7, 2013 16:08

  It might be useful to have a read of the following doc Oracle Support - "error:"error Communication with the server. " "Callback failed for the data entry page" when you open a Web form of planning with the members of the Type of text [ID 1392689.1].

  And then this question should be resolved en.600

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• vCenter 4.1/ESXi 4.1 material status "Communication error with the server.

  I am slot that a brand new installation of vCenter with two new installs of ESXi 4.1 connected on it. I use on Dell PowerEdge 2950 s ESXi servers. I tired the customized version of Dell and vmware ESXi vanilla version. My host vCenter is Windows 2008 R2.

  In vCenter, the two server ESXi, any version of ESXi, I run, I get "Communication error with the server" error when I click the tab hardware state. No data appears in the hardware status tab.

  Only suggestion of Dell has been updated with firmware/BIOS on the server level. I did and it did not help.

  Anyone has any suggestions or ideas what would cause this?

  I had exactly the same problem what is to have everyone on this thread.  I finally called VMware support.  It is certainly a problem with Tomcat.  Apparently, during my initial installation of tomcat server vCenter (on a Win2k8R2 vanilla Server / unreleased) na not create a database file.  The vCenter Server uninstalled eventuall tech and went through the Setup again.  For some reason any Tomcat created db it's good the second time.  After installation, it takes about 5 minutes for the db should be created.

  On Windows 2k8R2 it is located here: C:\Program Files\VMware\Infrastructure\tomcat\lib\xhiveConfig\data

  The name of the comic is VcCache-by default-0. XhiveDatabase.DB

  My server didn't have one at all.  The relocation has created, at the beginning it is 0KB in size.  After 5 minutes, it grows up to 25, 600KB.

  Everything in my vCenter works now correctly.  I'm on 4.1.320137

  I hope this helps.

  Dave

• "27049 internal error" when you use recovery with Equium A60-692 utility

  TOSHIBA SATELLITE A60 - 692

  I'm trying to fix a friends laptop. The laptop computer wouldnâ? t start, would go to the blue screen just before the came WinXP loading screen then will re-start. I used a USB 2.5 HDD enclosure "to copy important files on my laptop and then formatted the drive of my laptop. I put the HARD drive in the Toshiba and have used the CD of restoration via an advanced option. on exactly 9mins 50sec time on the recovery process, an error message appears (27049 internal error). After that, it goes to a screen of style BACK with a little more information. Essentially by specifying that the error is "cannot read FILE_BITMAP MFT entry.

  I cleaned the CD
  I swapped the CD drive with my laptop
  Quick formatting it formatted, it is full
  Used the basic option where it does itself and it ERRORS with - not enough space on the partition - there is no partition! or if there's empty sound

  What can I do?

  Hello

  I think that the HARD drive is broken, because if you receive an error message with words like "MFT" (meaning MasterFileTable) then you can expect that the HDD has serious problems.
  OK, easy to talk to it s fast without knowing the machine and so on, but I know a similar error and I can give you the advice to probe hard disk errors.
  You can do this with the help of the "ultimate boot cd" which is a very interesting tool when you need information about your computer or you want to just check if everything works well.
  Here´s the link to the downloadable CD image that should be on a CD:

  http://www.ultimatebootcd.com/

  Hope you can solve this problem...

  Welcome them

• Is "Repository creation utility" a mandatory for SOA Suite

  Hi all
  
  I am new to Oracle 11g Weblogic application server. I worked on the Oracle 10 g application server. I am very interested to BPEL and planning to learn BPEL and SOA concepts in.
  
  I have 11.1.1.0.1 Jdeveloper, Oracle Weblogic server 10.3.2, database Oracle 10.2.0.3 for windows vista installed on my laptop.
  
  Now, I downloaded SOA Suite 11.1.1.2.0 and JDeveloper SOA Composite editor. But in the list of additional software required for SOA Suite, we need to * "repository creation utility."
  
  Can someone give me the link for documentation of what is it and why is it necessary?
  
  I worked in BPEL in Oracle 10 g and there was no such additional deposit creation utility. I'm quite novice in this technology and planning only to learn that basic concepts of the BPEL (Basic is very widespread word here. I mean using adapters, working with the web services BPEL etc.).
  
  For this kind of basics and running SOA Suite is the repository creation utility, a mandatory requirement?
  If so, can I install utility of creating repository with my version of the database of * 10.2.0.3 * (because I read that the repository creation utility works with 10.2.0.4 or higher)?
  If not, how can I get the Group of hotfixes to upgrade my 10.2.0.4 Database 10.2.0.3.
  
  Thank you and best regards,
  Pavan.

  1--> Yes, it is mandatory to run 'Remote control' to install/upgrade using FMW/SOA Suite 11 g.
  2--> you don't need to install the regional coordination unit, it can be downloaded in zip file, and once you unpack this last, it can be run directly.
  3--> "What it is"--> to a higher level, that it's a bunch of scripts required to create storage space related to the SOA/BPEL processes. As you know that BPEL process are with States of the process and their States, etc. must be stored in a database.
  4--> even in Oracle 10g, there used repository, but it got installed by default and the tables created in the database of default olite.

  http://www.Oracle.com/technology/software/products/middleware/htdocs/111110_fmw.html

  Cheers!

• error of Server.app DNS-Service reading settings

  Hello!

  Under MacOs X with more than 5.2 10.11.6 I realize a problem when I try to click on the DNS service. I get a message like

  "error reading settings...". »

  The DNS service seems to work but I get none of my poster DNS configurations...

  A server restart does not solve the problem.

  No idea what I can do?

  Thank you

  Peter.

  P.S.: "sudo serveradmin settings dns" gives no answer

  The first line of my first assignment should be:

  Under MacOs X with server 5.2 10.11.6 I realized a problem when I try to click on the DNS service.

  Sorry!

• My emails are not sent and I get an error message - error 550 server windows live mail error ID 0x800ccc79.

  My emails are not sent and I get an error message - error 550 server windows live mail error ID 0x800ccc79.

  Your help would be greatly appreciated

  Thank you

  original title: network

  Hello GerryBenjamin,

  The best place to ask your question of Windows Live is inside Windows Live help forums. Experts specialize in all things, Windows Live, and would be delighted to help you with your questions. Please choose a product below to be redirected to the appropriate community:

  Windows Live Mail

  Windows Live Hotmail

  Windows Live Messenger

  Looking for a different product to Windows Live? Visit the home page Windows Live Help for the complete list of Windows Live forums to www.windowslivehelp.com.

• Cannot install McAfee on Windows XP. Errors with "Event Viewer".

  Hello, I am writing on behalf of a client.

  The customer has been in touch with the people of McAfee support for four days and they are still not able to install the antivirus program due to errors with Event Viewer. The people of McAfee asked the customer to reach the MS Support since then, as they say is a Windows problem.

  The event viewer contains errors in the Service Control Manager,

  DCOM, NetDDE.

  That's my problem, put support in for me.  Some fo include errors in the event viewer:

  DCOM got error "the service did not to start or control request in a timely fashion." try to start WSearch service with arguments "" to start the server:

  {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}

  Details Product: Windows operating system ID: 7000 Source: Service Control Manager Version: 5.2 Symbolic name: EVENT_SERVICE_START_FAILED Message: The %1 service failed to start due to the following error: %2     Explanation (SCM, Service Control Manager) could not start the service specified, probably because the service is not configured correctly.     User action Do one or all of the following conditions: Check the error information displayed in the message. Check that the service password has not expired. Verify that the service is in the right place. Check that the service is not infected with a virus. To view the WIN32_EXIT_CODE as SCM error when you try to start the program, at the command prompt, type application of SC name of the service The displayed information can help you troubleshoot the possible causes of the error. If the WIN32_EXIT_CODE is zero, SCM did not attempt to start the service because the error was detected first.         Version: 5.0 Symbolic name: EVENT_SERVICE_START_FAILED Message: The %1 service failed to start due to the following error: 2%.     Explanation (SCM, Service Control Manager) could not start the service specified, probably because the service is not configured correctly.     User action Do one or all of the following conditions:

  • Check the error information displayed in the message.
  • Check that the service password has not expired.
  • Verify that the service is in the right place.
  • Check that the service is not infected with a virus.
  • To view the WIN32_EXIT_CODE as SCM error when you try to start the program, at the command prompt, type
  
  application of SC name of the service
  The displayed information can help you troubleshoot the possible causes of the error.

  If the WIN32_EXIT_CODE is zero, SCM did not attempt to start the service because the error was detected first.

  There is currently no article for this specific error Microsoft Knowledge Base or an event message. For more information on other technical support options, you can use to find answers online, see http://support.microsoft.com/default.aspx.

  ++++++++++++++++++

  Details Product: Windows operating system ID: 206 Source: NetDDE Version: 5.0 Component: System event log Message: Listen failed: %1     Explanation The computer expected data from another computer, but not the not received. The other computer does not send, or the thread on this computer that listens to the data has encountered an error.

  There is currently no article for this specific error Microsoft Knowledge Base or an event message. For more information on other technical support options, you can use to find answers online, see http://support.microsoft.com/default.aspx.

• Disney app will not work on 5510 printer. Error connection server error message:-95

  New 5510 printer. All the apps work except Disney. Tried several times. Able to selected photo, preview and select # copies, but after hitting OK error message: "server connection error:-95.. There was a problem connecting to the server. Press Retry to reconnect or OK to change. "Does not work. Help, I want Disney app to work.

  If this is the only app that does not work on your printer and after uninstallation and reinstallation of the application, it still does not work, the problem lies in the app and its manufacturer. The fact the other apps are working shows the issue is not with the printer or apps function. I could wait a few days and see if it starts working again, but at this point, there is nothing else to solve problems too long that other applications work properly.

• error del server: 3204 ID error windos live 0x8DE20003

  error del server: 3204 IDerrore windos live 0x8DE20003

  Hello

  Unfortunately the answers is a site of support of peers supported and has no real influence
  with Windows Live.

  Check with Windows Live Support and Forums

  Windows Live Mail Forums
  http://www.windowslivehelp.com/forums.aspx?ProductID=15

  Windows Live Solutions
  http://www.windowslivehelp.com/solutions.aspx?ProductID=15

  Windows Live Solution Center
  http://www.windowslivehelp.com/

  Error message "your account has been locked" when trying to connect
  http://windowslivehelp.com/thread.aspx?ThreadId=77be7d82-a0e9-49c7-b46d-040ec654a9e2

  Compromised account - unauthorized account access
  http://windowslivehelp.com/solution.aspx?SolutionID=6ea0c7b3-1473-4176-b03f-145b951dcb41

  I hope this helps and happy holidays!

  Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle="" -="" mark="" twain="" said="" it="">

• Error message about Lightroom mobile (which I have not or use)

  Hello

  I bought the version regular stand-alone Lightroom and use it without any cloud thing. Suddenly, I get an error message that says "mobile trial Lightroom has expired. I do not use it, the "feature" is suspended (cannot be disabled), but the annoying error message is still displayed.

  How to completely remove this message?

  I am running the latest version of Lightroom.

  Hello

  In the upper left corner of the main window close the model name, there should be a drop down menu that has "sync with LR Mobile" as the first option. From there, you should be able to disable it.

  Thank you