All scheduled BI Platform reports remain in Pending status, regardless of format, destination, etc.
Restarting the Server Node, the Server Intelligence Agent (SIA), or restarting the Central Management Server (CMS) may resolve the problem for a period of time.
Restarting the Adaptive Job Servers will not have any effect on the scheduling problem
CMS trace log (.glf) will contain ERRORS regarding the SchedulingThread
Testing (one or more of) the Authentication plugin’s ‘Update’ button, may result in communication or configuration failure.
- SAP BusinessObjects Business Intelligence 4.x
- With scheduled reports that were created (SI_OWNER) using accounts with authentication methods other than BI Platform Enterprise authentication, such as external SAPR3, WinAD, LDAP, sources.
BI, BI4, BI4.x, BI4.0, BI4.1, BI4.2, BI4.2, 4.0, 4.1, 4.2, 4.3, schedule, schedules, scheduled, scheduling, Pubilcations, Publishing, Publish, WebI, Crystal, CR4E, Web Intelligence, Lumira, LUM, LUMX, InfoView, BILaunchpad, CMC, BOE/BI, , KBA , BI-BIP-AUT , Authentication, ActiveDirectory, LDAP, SSO, Vintela , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , BI-BIP-SRV , CMS / Auditing issues (excl. 3rd Party Authentication) , BI-BIP-PUB , Publishing and scheduling in InfoView/BI launch pad , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.