Report Pending with 30 Jan, 1979; Job server has Failed Inst

security CMC
1

Dear Experts,

In our productive BO environment frequently I am observing that we have failed instances on the Adaptive job server, due to which other schedule does not run at expected time but get assigned "Jan 30, 1979 12:00AM” past dated hard coded date; also it does not let other jobs to be pushed to secondary available Job Server.
When I manually disable the Job Server which has failed instances other jobs start moving to Secondary job server.

I have followed various approaches also the ones mentioned in below SAP post, but still it did not work out for me.

https://launchpad.support.sap.com/#/notes/0002223979
https://launchpad.support.sap.com/#/notes/2316053

Kindly help if any one has any suggestions on this.

Regards,
Neeraj

neerajchourasiya06 (BOB member since 2011-04-11)

2

have you checked your license keys?

NycPriya (BOB member since 2010-11-04)

3

Hi,

Ideally, if the failed instances are causing delay in the scheduler, it should not cause any issues to existing recurring schedules. The jobs will be in pending state if there is a delay in the scheduler due to failures.

I would suggest to raise a SAP ticket to understand if there is a known bug in the existing product version which you have installed.

Regards,
Sukesh

sukrav :india: (BOB member since 2008-01-29)

4

I faced the same issue a month ago and the root cause was the SMDAgent installed in SAP BI server for generate EWA report.

we stop the agent and restart the job server and all works again as normal

cbonilla (BOB member since 2017-07-18)