The Servicing Director Event Manager application can be commanded to run all scheduled events by scheduling software, such as Microsoft Windows Task Scheduler.

The Servicing Director Event Manager application allows you to schedule events to run each day, and these events appear in the Scheduled Instances list on the Event Manager screen.

At the end of the day, you must click Run All on the Event Manager screen to actually command Event Manager to run all scheduled events.

You can also have Microsoft Windows (or other third-party) scheduling software issue the command to Event Manager to run all scheduled events, allowing you to run the events unattended, with no one at the desktop. You can use the unattended running of the events to run the events in the evenings or on weekends, as needed, with the Servicing Director applications computer still on, but no one has to be there at that time.

The Windows Task Scheduler software can be used to automatically issue the command to Event Manager to run all scheduled events.

Other Windows scheduling software should also be able to issue the command to Event Manager.

Note: Running the Event Manager unattended after 11:00 PM (based on the local computer clock used to run Event Manager) is not recommended. If you do choose to run the Event Manager unattended after 11 PM, scheduling events other than daily, such as month end events, takes much more care, and you are required to add a setting to Event Manager for the Auto Run setting.

The Windows Task Scheduler instructions are provided below for your local System Administrator or IT group, who has experience with your Microsoft Windows software. Other Windows scheduling software instructions are not provided here, and therefore you must refer to the other software support for those instructions.

If you choose to automate Event Manager to run all scheduled events, consider normally following information covered in the Servicing Director Help topics or other articles in the knowledge base.

• You must configure the Change Posting Date Update event to automatically complete.
• You must review the Event Manager Run All event log as soon as possible after the automated Event Manager run all scheduled events is completed. The log will show if any Events failed, and you will need to know if an event failed as soon as possible because you may be able to correct the error or correct the system, preventing further errors, or problems.
• You should use the Event Manager Email Notification event to e-mail you about whether all scheduled events completed successfully or whether any event failed.
• You must maintain the Event Manager Holidays calendar to be sure it has the current non-business holidays and weekend days.
• An unattended Event Manager will accommodate being run every day of the year, as Event Manager will start to run all events or skip the events and exit based on your user-maintained Holiday calendar.
• You must disable the automated scheduling of Event Manager at the end of the year during the year-end processing to allow your business to complete any adjustments for the end of the year before returning to regular end of day Run All event scheduling.
• Event Manager will use your user maintained Holiday calendar and determine whether to run scheduled events or not.  When your scheduling software runs Event Manager on a Holiday (or non-business day) on the Event Manager calendar, then it will simply exit and not run any events.
• The unattended Event Manager will select the schedule of events based on the computer clock date. When you have the Windows scheduling software run Event Manager before midnight, the computer clock date will likely always match your Current Transaction Posting date when the Event Manager starts, so Event Manager will select the list of events which match those events scheduled for your Current Transaction Posting date. Therefore, if you have events to run on specific days and not daily, schedule them for the day which matches the computer clock date on that day.
• You must not use the Servicing Director Read-Only mode during the unattended run all scheduled events. See other articles for more information about Read-Only mode.
• Your users may wish to or be required to attend the running of some events, and therefore those events will have to be run manually, and not scheduled to run with Event Manager.
• As of this writing, an Event Manager issue prevents every unattended run of Event Manager from exiting normally when all the events are completed. Therefore, the EventMgr.exe process will continue to run after it has an unattended start, and it must be ended by the scheduling software sometime after all the events have had enough time to finish, and before a user tries to access the Event Manager to view the Event Manager Run All event log.

• The Auto Run setting only applies when scheduling on or after 11:00 PM, and If this setting is missing, the automated Event Manager may incorrectly run on a Holiday. Use the Event Manager Options menu Auto Run screen to set this value. Set the time on the Auto Run screen to 1 hour later than when your scheduling software is starting the automated Event Manager. For example, if you schedule the automated Event Manager to start at 11:00 PM, then set the Auto Run setting to 12:00 AM, or if the start time is 2:00 AM, then set the Auto Run to 3:00 AM.
• Event Manager will still not run any events if the Current Transaction Posting date is in the future when compared to the current computer clock. The Event Manager will add any time value you enter for the Auto Run Setting to the Current Transaction Posting date and compare that value to the current clock date and time. This adjusted Current Transaction Posting date and time will be in the future if it is greater than the current clock date and time, and Event Manager will simply exit and not run any events.
• An unattended Event Manager selects the schedule of events based on the computer clock date. This differs from when a user starts Event Manager, and the schedule of events by default is based on the Current Transaction Posting date. Beware, the unattended Event Manager run after midnight will select a list of events from the next day, based on the after midnight computer clock date. This is not usually an issue for daily events as they are on every schedule, but if you schedule any events to run on specific days and not daily, then be careful to schedule them to run on the next day--the day after your original choice of day. For example, if you have an event which needs to run only the "last day of the month", then schedule the event to run on the 1st day of the month because the computer clock date after midnight of that last business day of the month will be the 1st of the next month.
• When scheduling any events to run on specific days and not daily, use only the Scheduling option of Once, and set the day to run the event (as above, the day after your original choice of day.  Other Scheduling options such as Monthly "The last day of the month" or "Day = 1" will not correctly schedule your event for specific days when the specific day is a Holiday. For example, for an event which needs to run only the "last day of the month", then schedule the event to run on the 1st day of the month, once for every month of the year, scheduling the event 12 times.
• When scheduling any event to run on specific days and not daily, use only the Scheduling option "if Scheduled day is a holiday" set to "Execute event only on holiday".  Any other Holiday choice will not correctly schedule your event for specific days when the specific day is a Holiday.
• As you schedule any event to run on specific day and not daily, you have to adjust for Holidays manually, scheduling the day you want after midnight before or after your Holiday.  For example, If your last day of exactly month is a Sunday (Holiday), and you want to run the end of month event after your last business day on Friday, then you will use the Once scheduling option and schedule the event for Saturday (the after midnight day for your Friday business day.

• Be a member of the local computer Administrators group.
• Be granted the Local Security Group User Rights Assignment of "Log on as a batch job".
• Must have all the Windows permissions required by the events configured by the users. For example, your users may configure an event to export files to a user defined file location requiring permission to write to the location. To confirm you have a Windows account with correct Windows permissions, be sure to first demonstrate you can perform the Scheduled Task interactively. To do this, when it is time for Event Manager to run all scheduled tasks, log in to the Servicing Director applications computer with the Windows account you are going to use for Task Scheduler task, and interactively launch the Event Manager run all scheduled events by clicking Run All. Complete the full Run All as the actual Windows account interactively to make sure the Windows environment for that Windows account will provide all that is needed to run the unattended Event Manager.  Follow-up the above by testing your Task Scheduler task next.   To do this, log in to the Servicing Director applications computer with the Windows account you are going to use for Task Scheduler task, and start the Task Scheduler task, and the automated run of the the Event Manager should start and display on the desktop as it runs for you to observe for any issues.

• If the SvcData network shared folder is on a remote network location (a file, directory, or folder not located on the local computer running Task Scheduler), then it must not use a Windows mapped drive for the network path.  The SvcData folder network must use a Windows UNC path instead of a mapped drive. The Servicing Director applications installed on the computer running Task Scheduler will have an SvcData folder path configured, which will be the folder used by the local copy of Event Manager. Task Scheduler does not recognize a Windows mapped drive when run unattended and if the SvcData folder uses a mapped drive, the unattended Event Manager will start and do nothing as it will be denied access to the SvcData folder.
• You must configure any events using a network location for a file path (such as a file import or export) to use a Windows UNC path, and not use a Windows mapped drive. Task Scheduler will not recognize a Windows mapped drive. Manually enter the UNC file path into the event criteria screen, and do not use the Browse button provided for local and mapped drives.
• You cannot select the Task Scheduler task Security option "Do not store password" for the user account running the task (step 8 below) if you want to use any network location. This Security option limits the user account access to only local file paths, and this Security option will prevent access to a network location for the SvcData folder as well as to any network location user defined in event criteria. If the SvcData folder and all the user defined event criteria uses a local file location, then you can use this task Security option.

• On a 64-bit Windows computer:

C:\Windows\SysWOW64\config\systemprofile\Desktop

• On a 32-bit Windows computer:

C:\Windows\System32\config\systemprofile\Desktop

1. Follow your Windows documentation to start the Task Scheduler console provided by Microsoft.
2. Start the Create Task wizard.
3. On the task General properties tab, select the following:

• Select your own name for the task.
• Select the task Security option to "Run whether a user is logged on or not".  Do not select the Security option "Do not store password" if you re using any network file locations as described above.
• Checkmark the Security option "Run with highest privileges".
• No other General properties are required.

4. On the task Trigger properties tab, select the following:

• Start the task Daily, and Recur every 1 days. The user maintained Event Manager Holiday calendar will control when to run the events.
• Select a start time before 11:00 PM as recommended above.
• Checkmark "Stop task if it runs longer than" and select the number of hours between your start time and the first time a user will be checking the Event Manager Run All Event Log the next business day. For example, if your start time is 11 PM, and your local IT or system administrator will be viewing the Event Manage log file the next day at 5 AM, then select to stop the task after 6 hours.
• Checkmark "Enabled" when you ready to begin using this task.
• No other Trigger properties are required.

5. On the task Action properties tab, select the following:

• Start a program.
• Browse to the EventMgr.exe file in your Servicing Director folder. The default location for your Servicing Director folder will be one of the following:

C:\Program Files\D+H\Servicing Director
C:\Program Files (x86)\D+H\Servicing Director

• Add Arguments (optional) field text exactly as follows:

• No other Action properties are required.

6. On the task properties Settings tab, select the following:

• Checkmark "Allow task to be run on demand".
• Checkmark "Stop task if it runs longer than" and select the number of hours between your start time and the first time a user will be checking the Event Manager Run All Event Log the next business day. For example, if your start time is 11 PM, and your local IT or system administrator will be viewing the Event Manage log file the next day at 5 AM, then select to stop the task after 6 hours.
• Checkmark "If the running task does not end when requested, for it to stop".
• No other Settings properties are required.

7. Click OK.
8. When the wizard prompts you to enter the name and password of a Windows user, enter the Windows account you previously determined has all the Windows permissions necessary to complete the Event Manager events.

ArticleNumber:

000050024