skip to content
Products documentation
User Tools
Log In
Site Tools
Search
Tools
Show pagesource
Backlinks
Media Manager
Sitemap
Log In
>
Media Manager
Sitemap
You are here:
Welcome to Redpeaks Wiki
»
products
»
cockpit
»
Welcome to Redpeaks Cockpit
»
Trouble shooting
»
Monitoring
»
BusinessObjects connection is not working
Sidebar
Redpeaks Cockpit
Release note
Product features
Install Guide
Architecture
Prerequisites
Install JAVA
Install Redpeaks cockpit
Install MySQL
Install Victoria Metrics
Startup configuration
User Guide
Overview
User interface
Applications
Monitoring
Dashboards
Settings
Administration
Best practices
Support
Guidelines
products:cockpit:1.0:troubleshooting:monitoring:businessobjects
Book Creator
Add this page to your book
Book Creator
Remove this page from your book
Manage book (
0
page(s))
Help
Table of Contents
BusinessObjects connection is not working
Context
Problem
How to fix
BusinessObjects connection is not working
Context
Connection to the BO instance is failing with message:
Could not reach
CMS
'hostname:6400'. Specify the correct host and port and check for network issues. (FWM 20030)
Problem
See SAP note: [
https://launchpad.support.sap.com/#/notes/2151044]
How to fix
To resolve this issue the local system must be able to resolve the hostname of the remote
CMS
, which is being returned by the name server (6400).
This can be achieved by:
Either adding the hostname and IP address to
DNS
OR By adding the information to the hosts file of the local operating system:
Go to C:\Windows\System32\drivers\etc (/etc/hosts on linux / unix)
Edit the “hosts” file
Add a new row to the end with the IP address, the server name, and the fully qualified domain name like: 10.100.100.100 servername servername.FQ.DN
/home/clients/8c48b436badcd3a0bdaaba8c59a54bf1/wiki-web/data/pages/products/cockpit/1.0/troubleshooting/monitoring/businessobjects.txt
· Last modified: 2024/05/01 18:52 (external edit)
Page Tools
Show pagesource
Backlinks
ODT export
Add to book
Back to top