After a certain point, on SIA number 1, there is no way to get Web Intelligence Processing Server and Connection Server to a running state: CS goes into “failed” state after some attempts to start (we can see it going into “starting” and then “initializing” state). WIPS is neither trying to start: he stays in “stopped” state and, trying to start it manually, it goes immediately in “failed” state.

Before performing below steps stop all the BI services and kill any stuck processes for WebI Processing Server and Connection Server

1. Locate the boconfig.cfg file e.g. /home/bi4/BI4/setup/boconfig.cfg and copy the boconfig.cfg file from a working BI4 system and make sure you amend the paths and filenames to match your current system. Refer to SAP KBA: 2358425 - ConnectionServer will not start

2. Then remove tmp/bo_config.mutex. Refer SAP KBA: 2331564

3. Start the servers.

Though you did not run out of disk space I would recommend for the above steps.

- Change made on this host, prior the issue, was the disinstallation of the SAP Solution Manager Diagnostic, but, after the issue, we restored the file systems involved. Now SMD is working fine again, but BO’s issue is still present.

- There are no space issue on this host !

- We checked folder “<inst_dir>/sap_bobj/data/Auditing”: its size is 156 KB

In that folder there are 1454 files with extension *.txt; all of them are 0 KB size except one:

Add comment

The /var/log/messages is not giving much insight. Can you apply High level traces on Connection and WebI Processing Server by changing the log level from unspecified to High and start both the servers. Once they fail collect both the glf files and provide it to us.

Lets see the log files first and then we can think of performing the steps mentioned in KBA: 2331564