SAP Business Object Intelligence 4.2 SP08 Patch 400 Bug in Windows Platform
In this blog post, I would like to share my SAP Business Object Intelligence 4.2 SP08 Patch 400 installation/upgrade Bug experience, which includes symptoms, issues and fixes.
SAP Business Object Intelligence 4.2 SP08 Patch 400
Operating System Windows 2016 R2
Database MS SQL 2016
Distributed Deployment (Tomcat, CMS nodes on separate hosts)
After upgrade/Installation to 4.2 SP08 Patch 400 following error(s) while connecting from Analysis Office.
“Error while trying to login using AO: Could not log on to BIP server: Invalid CMS” and Unable to login to CMS via AO Application intermittently including administrator user”
CMS.exe will consume 100% of 1 CPU core. For example: If you have 4 CPU cores it will show 25%, 2 cores 50%, 64 cores 1.55%
When the above occurs, login to Central Management Console or BI Launchpad is not possible, with below error generated
Account information not recognized could not reach CMS ‘<CMS>’. Specify the correct host and port and check for network issues. (FWM 20030)
The Central Management Server reports the following error: assert failure ServerWatcher.cpp:322).
(0 : Error notifying clients)
This issue has been identified as Bug in the Product. Please refer below KBA.
2968256 – Unable to login to CMC/BILP and high CMS CPU usage after upgrade
2983066 – BI Platform 4.2 Patches 8.4 and 7.12 for Windows unavailable for download
2888396 – Output FRS intermittently crashes under load
2943844 – [CVE-2020-6308] Server-Side Request Forgery vulnerability in SAP BusinessObjects Business Intelligence Platform (Web Services)
It is amazing/frightening how many patches are released in SP08, although there are no new features since SP07