Skip to Content
avatar image
Former Member

Pending Jobs Stuck - Next Run Date 01/30/1979

BO 4.0 SP 02 Patch 14

Working with a client who over past year has experienced jobs remaining in a Pending State with a Next Run Date of 01/30/1979... the system then needs to be bounced and all services brought back up and running.

We have used a number of recommendations from SAP with no resolve - but want to know if there is anyway to alert us when pending jobs are not firing off and are sitting as pending for longer than 30 minutes?

Any suggestions welcome.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jan 08, 2015 at 08:07 PM

    Have you tried to add "-type OUTPROC" command line argument on the BI4.0 SP02 P14 AdaptiveJobServer? See SAP KB 1664719 - Scheduled Desktop Intelligence / Web Intelligence reports remain in Pending status in SAP BusinessObjects Enterprise XI 3.1 on http://service.sap.com/sap/support/notes/1664719.  Although this KB is intended for BOXI3.1, the "-type OUTPROC" command line argument can be still added to BI4.0. Also, check out SAP KB 1570942 - Multiple registry keys created by AdaptiveJobServer on http://service.sap.com/sap/support/notes/1570942 for side effect from adding "-type OUTPROC" command line argument. Hope this helps, Jin-Chong

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Yes, we have already tried that solution. Then was told my SAP that it can cause problems actually adding that to the command line - reference SAP KB 1570942 - Multiple registry keys created by AdaptiveJobServer.