Java client returns the following Application Error: Unable to launch the application. ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.undert...Java client returns the following Application Error: Unable to launch the application. ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.undertow.listener.default: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.default: Address already in use: bind /0.0.0.0:80
Applies to OnCommand Insight (OCI) 7.3.x Issue After entering LDAP based credentials in the login page, user sees the message "Invalid username or password" and cannot access OCI thereafter as shown b...Applies to OnCommand Insight (OCI) 7.3.x Issue After entering LDAP based credentials in the login page, user sees the message "Invalid username or password" and cannot access OCI thereafter as shown below.
Applies to OnCommand Insight's Data WareHouse 7.x (DWH) Cognos Report Engine (Packaged with DWH download) Description This article describes the procedure to be followed to import Cognos Reports.
This article explains how to view the hardware serial number in EMC Elastic Cloud Search (ECS). There is a difference between the License Serial number and the Hardware Serial number. OnCommand Insigh...This article explains how to view the hardware serial number in EMC Elastic Cloud Search (ECS). There is a difference between the License Serial number and the Hardware Serial number. OnCommand Insight (OCI) always displays the License Serial Number of ECS. In EMC ECS, we have the following information: SWID = License serial number ECS uses the SWID as the identifier on how storage nodes are identified. The SWID is also visible in OCI as the serial number; this is the License serial number.
After Saturday September 21st 2019 OnCommand Insight's web interface is returning the following message or HTTP 404 ERROR: This issue can be identified by checking the OCI logs folder and the server.l...After Saturday September 21st 2019 OnCommand Insight's web interface is returning the following message or HTTP 404 ERROR: This issue can be identified by checking the OCI logs folder and the server.log file: In the server.log file, the following error is displayed (though it may have a different hour and timezone): This file, if failed, will be named "oci.war.failed" and is located in the following directory:
Applies to OnCommand Insight (OCI) end user is running a supported Java Runtime Environment (JRE) on a supported Operating System. - Version independent Issue OCI client consistently fails to start an...Applies to OnCommand Insight (OCI) end user is running a supported Java Runtime Environment (JRE) on a supported Operating System. - Version independent Issue OCI client consistently fails to start and reports logging error messages similar to the following: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
Applies to OnCommand Insight Description This KB article describes how to perform the following actions related to OnCommand Insight AutoSupports: How to enable OnCommand Insight (OCI) Autosupports (A...Applies to OnCommand Insight Description This KB article describes how to perform the following actions related to OnCommand Insight AutoSupports: How to enable OnCommand Insight (OCI) Autosupports (ASUP). How to Include or Exclude "Logs" and/or "Performance Data" from OnCommand Insight (OCI) AutoSupports (ASUP). How to change the AutoSupport send Protocol to: HTTP Email How to modify AutoSupport size limitations for email. Note: An AutoSupport is also sometimes referred to as "Phone Home".
Applies to OnCommand Insight (OCI) ElasticSearch Description High-level information about Elasticsearch service and then we talk about best practice to keep the service running and healthy. - OCI serv...Applies to OnCommand Insight (OCI) ElasticSearch Description High-level information about Elasticsearch service and then we talk about best practice to keep the service running and healthy. - OCI server start using ElasticSearch service from 7.3.0 and it replaces Cassandra - ElasticSearch hold the performance data for Oncommand Insight and uses port 9200 and 9310 - OCI web UI will not come up if ElasticSearch is not running
Applies to OnCommand Insight's Data Warehouse (DWH) OnCommand Insight (OCI) Issue Post upgrading OnCommand Insight (OCI) servers, users run a build of the Data Warehouse (DWH). The build fails during ...Applies to OnCommand Insight's Data Warehouse (DWH) OnCommand Insight (OCI) Issue Post upgrading OnCommand Insight (OCI) servers, users run a build of the Data Warehouse (DWH). The build fails during the Extract, Transfer, and Load (ETL) reporting the 'Invalid Server Database' error on the screen as shown below:
When attempting to start IBM Cognos manually via IBM Cognos Configuration, the operation will fail with one of the following. Successfully launched a test JVM with the memory setting of '4096'. Note t...When attempting to start IBM Cognos manually via IBM Cognos Configuration, the operation will fail with one of the following. Successfully launched a test JVM with the memory setting of '4096'. Note that this does not guarantee that the IBM Cogn os service will start and run successfully. [ ERROR ] CFG-ERR-0106 IBM Cognos Configuration did not receive a response from the IBM Cognos service in the time allotted.
Look at the CLI output of:> netstat -ano| findstr -i 80 you will we see: SYSTEM (PID 4) is LISTENING on Port 80. (the World Wide Web Publishing service starts as PID 4 by default) Services which faile...Look at the CLI output of:> netstat -ano| findstr -i 80 you will we see: SYSTEM (PID 4) is LISTENING on Port 80. (the World Wide Web Publishing service starts as PID 4 by default) Services which failed to start: service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener.
