After you run Event Manager and run all scheduled events, the Current Transaction Posting Date on the system is not advanced or changed, and it is still the same Transaction Posting date as the just finished business day.

IMPORTANT! Do not click on the Run All button again until this issue is resolved.

The Change Posting Date event is normally required to perform the end of day Run All events, and it is normally scheduled with a priority which puts it first or nearly first on the list of scheduled events. 

The Change Posting Date event is scheduled first ,or nearly first, because most of the events base their processing on the transaction posting dates set by the Change Posting Date event.  If the Change Posting Date event is not run, is cancelled by the user, or is directed by the user to not change or advance the date, the transaction posting dates do not change and the rest of the events repeat yesterday's processing using yesterday's dates. 

Only the Change Posting Date event changes the Current Transaction Posting date and no other part or process in Servicing Director can change that date. There is no known reason for the Change Posting Date event or any other scheduled event to become unscheduled other than for a user to make the event unscheduled at some point in time. 

You can cancel the Change Posting Date by clicking the Cancel button which only cancels the single Change Posting Date event. The other Run All scheduled events will continue with the dates unchanged.

You can also change the Current Transaction Posting date by entering a date value in the Change To field which overrides the date chosen by the event. Unfortunately, these user changes are not logged by the application which means there will be no record of the changes.

Workaround:

IMPORTANT! Do not click on the Run All button. Do not choose to Run All scheduled events until troubleshooting this problem is complete and you determine to move forward with the Run All scheduled events.

1. Stop all users from entering new transactions. Do not enter new transactions until troubleshooting this problem is complete. Enabling Servicing Director Read-Only mode is one way to do this. For more information, select Using Servicing Director Read-Only Mode from the Related Articles portlet on the right side of this page. 
2. Confirm the transaction dates by opening the System Administration application > Table Setup > Company > Transactions tab.  Confirm all three dates are listed (Current, Prior and Last) in the Transact Posting Dates section.  For more information about the transactions dates, select Viewing the Servicing Director Current, Prior, and Last Transaction Dates.
3. Create the Event Log By Date report from Event Manager, using the start time criteria of the last known good Run All scheduled events.  Enter the StartTime > date of last known good Run All scheduled event in the criteria.  For more information, select Event Log by Date Report.
4. Locate and confirm your most recent Servicing Director database backup files.
5. Review the Event Log By Date report you created for the Change Posting Date event and confirm it was run.
6. If the Change Posting Date event was run, check with the users to see if the event was cancelled or the date change was overridden.
7. If the Change Posting Date event was not run, check to see if the event is no longer scheduled or if a user deleted it from the current schedule or from all schedules.

ArticleNumber:

000062534