SAP Knowledge Base Article - Preview

1901238 - Malformed scheduled start date creates thousands of failed reports


When scheduling any report as a monthly recurring, if the start date is modified to use a 2-digit year the result will be the one recurring job plus 100's to 1000's of failed instances.  This can immediately be seen in the history page after clicking schedule. The failures appear to be indefinite and do not stop until the job is paused or deleted.


CMS Logs will show references similar to:

2013/08/14 20:44:54.844|==| | |18152|7576| |||||||||||||||(.\RunnableCallback.cpp:78) starttime=13-09-02@08:30:00.000  nextrt=221-09-02@08:30:00.000 now=2013-08-14@16:44:54.844
2013/08/14 20:44:54.891|==| | |18152|7576| |||||||||||||||(.\ScheduleThread.cpp:4219) CScheduleThread::constraintsMet(): time constraint o.k. for object [7773591]: [221-09-02@08:30:00.000]<=[2013-08-14@16:44:54.875]<=[2023-04-09@18:30:00.000]



BusinessObjects Enterprise XI 3.1 Service Pack 5


SAP BusinessObjects Enterprise XI 3.1


jkuhn TE# 5050153104  PR ADAPT01703205 FR ADAPT01703206  , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.