All scheduled Crystal reports stuck in pending status

Symptom

• Scheduled Crystal Reports stuck in pending status.
• View on demand runs without error
• ps -ef shows all XI servers are running 8 parent/child processes for each server instead of just 1. Ex (8 cms processes, 8 Crystal job server processes)
• Error is found in /var/log/messages:
• Mar 24 16:45:54 atldevlpmm11 boe_jobsd[19965]: Subprocess (Job Server Child) could not be started. Reason: Couldn't get IJob interface or writing IAudit: Pipe exception. Reason: boe_jobcd (procreport, 0, Timeout waiting for Child [19966] to register ([120]seconds). .

Environment

• Business Objects Enterprise XI 3.1 SP 3
• Redhat Enterprise Linux RHEL 4 update 2
• 32 bit

Reproducing the Issue

Schedule Crystal report via CMC or Infoview and observe status never changes from Pending.

Cause

Environment variable being set: LD_ASSUME_KERNEL=2.4.19

Resolution

1. Comment out environment variable LD_ASSUME_KERNEL=2.4.19 in linux user's profile.
2. Log out/in of linux shell or re-source the user profile.
3. Restart all BOE XI services.

Training

http://wiki.sdn.sap.com/wiki/display/profile/Ingo+Hilgefort

custom database logon in the CMC, the stored procedure runs more than once.

CE 10, BO XI R2 and BO 3.1

New Behavior:

To fix this problem, users must install this Hot Fix patch, and then do the following:

1) Ensure the registry key "VerifyStoredProceduresOnSetLocation" is set to “No.”

For CE9, the registry key is in the following directory: HKEY_LOCAL_MACHINE\SOFTWARE\Crystal

Decisions\9.0\Crystal Reports\DatabaseOptions\

For CE10, the registry key is in the following directory: HKEY_LOCAL_MACHINE\SOFTWARE\Crystal

Decisions\10.0\Crystal Reports\DatabaseOptions\

2) Add the command "procreportoptions __noverifydatabase" in the command line of the Pageserver and Jobserver.

Note: the command "procreportoptions __noverifydatabase" has two underscores.

Known Limitations:

This fix is for the ODBC driver only.

This fix won't work for the RAS server or the Native driver

HTTP 500 errors when opening Instance Manager - R3

Symptom

HTTP 500 errors when opening Instance Manager

Cause

A pending scheduled job exists that does not have the SI_NEXTRUNTIME property.

Resolution

To determine which object may be the cause of the error, do the following steps:

1. Enable tracing on the CMS without requiring a restart. See SAP note 1335757
2. Open Instance Manager and receive the HTTP 500 error
3. Stop the CMS tracing.
4. In the resulting log file, search for SI_NEXTRUNTIME. Copy the query and run it in Query Builder.
5. Search through the Query Builder results to see whether there is a scheduled object that has a blank SI_NEXTRUNTIME

In the Central Management Console(CMC), delete the pending instance that is missing the SI_NEXTRUNTIME.

Open Instance Manager to verify the error is resolved.

SAP Business Objects 3.1 Architecture