Skip to Content
0

CrystalReports2013ReportApplicationServer fails to start after fresh installation

Jan 26, 2017 at 07:21 PM

233

avatar image
Former Member

This service fails to start after doing a fresh BI Platform installation. BI 4.1sp8

Specifically installing on RHEL 7.2, Oracle 11.2 db, no audit

All of the other services start up and run fine but this one doesn't start, install gave no indication of errors.

Things I have tried:

1. cloning service (failure)

2. Deleting and creating new service (failure)

3. Running the repair script: https://service.sap.com/sap/support/notes/1612745 (repair script errors on 4.1 against regsvr32 and creates core dumps)

4. Uninstall/Reinstall (failure)

5. Reposcan found 0 issues

Saw the following post for WINDOWS: (https://archive.sap.com/discussions/thread/3541006)

1. Did you do the install using a user who is a member of the Administrator group of the server?

A domain user in RHEL

2. What user is starting the SIA (domain user or default user?)

Domain user

Error from registry_repair_script40.sh

Output from repair script after brand new install of BI4.1sp8, Crystal RAS doesn't start, so I performed the steps detailed in the note and receive the following:

./registry_repair_script40.sh

mv: cannot stat ‘/home/svc_reporting/sap/sap_bobj/enterprise_xi40/linux_x86/crpe/mw//registry’: No such file or directory

./registry_repair_script40.sh: line 36: 6406 Segmentation fault (core dumped) "$MWHOME"/bin-${MWCONFIG_NAME}_optimized/regedit -c "$MWHOME"/../regupdate.reg > /dev/null 2>&1

setup/setupfunctions.sh: line 430: 6407 Segmentation fault (core dumped) "$MWHOME/bin-${MWCONFIG_NAME}_optimized/regsvr32" -c -nodisplay -s "$ITEM32" > /dev/null

setup/setupfunctions.sh: line 430: 6408 Segmentation fault (core dumped) "$MWHOME/bin-${MWCONFIG_NAME}_optimized/regsvr32" -c -nodisplay -s "$ITEM32" > /dev/null

setup/setupfunctions.sh: line 430: 6409 Segmentation fault (core dumped) "$MWHOME/bin-${MWCONFIG_NAME}_optimized/regsvr32" -c -nodisplay -s "$ITEM32" > /dev/null

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

avatar image
Former Member Jan 26, 2017 at 10:07 PM
0

Because there are multiple core dumps, e.g. "registry_repair_script40.sh: line 36: 6406 Segmentation fault (core dumped)", I'd suggest you to

1. check out /var/log/messages and look for the error message(s) related to the 2013RAS start up failure,

2. The Xvfb is the X Windows Virtual Frame Buffer, which is used to generate a display on the server without the need for an actual display session. It is important to be aware of this daemon and what it is used for. Problems with, or lack of, an Xvfb daemon can cause issues with report viewing in BOE. Issues with the Xvfb processes can result in crashing RAS servers, Job Server Child processes and Page Server sub processes. If the BI4.x Xvfb is not compatible with your OS. use the system Xvfb instead of the BI4.1 Xvfb.

See SAP KB 1610649 - ReportApplicationServer can't be started in BusinessObjects Enterprise XI3.1 ServicePack 3 on HP Unix IA64

Regards,

Jin-Chong

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

The article you posted was specifically for xvfb in HPUX I am dealing with RHEL, as well it references 3.1 and I am on 4.1 so the resolution to the issue would not be the same necessarily. The issue stated there is:

This patch is too new for the Xvfb and it's not compatible with BOE Xvfb.

I do not know how to do this in 4.1 and in RHEL or the env.sh for RHEL.

The /var/log/messages was helpful though, I didn't realize logging happened anywhere other than the logging folder. The error I saw is:

kernel: boe_crprocd.bin[21176]: segfault at 0 ip 000000005b65ee6d sp 00000000ff8e2bd0 error 4 in libkernel32.so[5b61a000+131000]

All of the other servers showed as started successfully.

0
Former Member

The error for 'libkernel32.so' lead me to the following ticket:

2329754: https://launchpad.support.sap.com/#/notes/2329754/E

Which describes missing libraries:

Libraries sssd-client.i686 and sssd-client.x86_64 missing in Problematic environment.

I added these libraries and then rebooted the system, but that did not help in resolving the issue.

0