- Your issue with scheduling Resync as a background job is tied directly to the allowable time-frames that are specified in LMS_ADMIN. In this configuration, you will find the section: <AllowedTimeFrames> This section contains individual time frames that define when background jobs can be scheduled. If you wanted to run the job immediately, it would have to be during one of the allowable time-frames currently specified in the LMS_ADMIN configuration.
Changing the Allowable Timeframes for Background Jobs.
- To get around the time restrictions, you can open up the time-frames to be run at anytime on any day by setting each timeframe to an asterisk, which will allow background jobs to be run at anytime. This is how you would configure the timeframe to be wide-open:
<StartTime minute="*" hour="*" day="*" month="*" year="*" dayofweek="*" />
<EndTime minute="*" hour="*" day="*" month="*" year="*" dayofweek="*" />
- One thing I do want to caution you of, is that running Resync can be a very process intensive task and should be scheduled as a background job when the LMS is not under high-usage. The reason for this, is that process-intensive tasks will cause the system's performance to degrade while the process is running, which could hinder the use of the LMS by other users until the process has finished.
KBA , LOD-SF-LMS , Learning Management System , How To