Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML SBM: Scheduled LDAP Sync jobs are not running, also impacts scheduled reports
This can happen if there is a user who sets up a scheduled job (LDAP import or scheduled report for example), and the user is later deleted. The system tries to run the scheduled job and fails because the user no longer has access to the system. This affects all future scheduled jobs and none of them will run.
CMS-XML Scheduled reports are not running
It is also possible for this problem to occur if there are events in the TS_NotificationEvents table that refers to a NotificationID in the TS_Notifications table that does not exist . To purge any of these possible orphaned events, run this query:
CMS-XML Scheduled reports do not work if user selects to run report on the last day of month
Scheduled reports do not work if user selects to run report on the last day of month
CMS-XML SBM: Scheduled reports do not run
The information in this document should be used if your scheduled reports where running on the selected schedule and then suddenly stopped running. NOTE: If you are running SBM 10.1.x, read about the related defect KB D18718 .
CMS-XML Since update to 11.3 scheduled reports are no longer running - Error: ... Exception occurred during invoking AE web service
Since update to 11.3 scheduled reports are no longer running - Error: ... Exception occurred during invoking AE web service
CMS-XML There are no Page Servers connected..." when trying to run or preview a report
>Error Displayed SYNOPSIS: Attempting to run or preview a report object from the Crystal Management Console results in the following error message in the Crystal Report Viewer:
CMS-XML Can't control the timeout value given for a scheduled report to run.
Would like to be able to control that timeout value and add time to it. If you have a scheduled report that takes longer than 60 seconds to run then it doesn't get sent. Being able to control this timeout will allow long running scheduled reports to be sent.
CMS-XML Message Parameter 'PESDimension' does not exist on this report Source Microsoft.ReportViewer.WebForms running report.
After upgrading to PPM 2009 R1 get the following error running a report created with the "Tasks by Investment" template. Error Detail Exception System.ArgumentException
CMS-XML Running the CMN120 report against a subsystem that does not exist get a RC=4093
SER1.Service SER1.Message SER1.Scope +++ RC(-3) +++ This should return a RC=08, just like when you run the CMN100 report for the same situation
CMS-XML VM: Can't run history on any archive report after failed UNLOCK
No History exists matching the requested specifications ... User performs an UNLOCK function on the archive. ... After dismissing the expected errors (i.e., Null Pointer Exceptions) a Show History report is attempted .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs