Troubleshooting Reading Tasks in DocRead
If you are wondering why you have no ‘Reading Tasks’ when you have assigned a ‘Required’ or ‘Recommended’ document to a group or audience of users this post will help you resolve and troubleshoot the most common reasons.
Reading Tasks are not created immediately
The biggest cause for no Reading Tasks is because users expect tasks to be created as the document becomes published in the document library. This is not the case as it would create serious performance problems for documents that need to be sent to thousands of employees. All processing is done via a scheduled SharePoint Timer job, or when a DocRead Administrator manually processes Reading Tasks for that site. Please note, when ‘Process Reading Tasks’ is triggered from the site only groups are processed not Audiences.
Document is not approved
If you have content approval activated on the document library, DocRead will only create Reading Tasks once the document has been approved.
The document is not published
If versioning is enabled on the document library, DocRead will only create Reading Tasks once the document is published.
Licencing Violation – maximum number of users
If you have reached the maximum number of users that your licence allows then DocRead will not process any further tasks. To verify this – look at the DocRead Event logs (accessible from Central Admin) and filter on ‘Error’. If you have an entry relating to a “licencing violation”, you will need to purchase additional licences from us.
One of the DocRead Timer Jobs hasn’t run
To ensure that the performance impact of processing Reading Tasks is kept to a minimum, audiences are only processed via a timer job. This means that if you attach a particular audience to a document, you must wait until the next ‘Audience Timer Job’ has run. Once this job has run the ‘Readership Processing Job’ will need to run afterwards which has the job of creating the tasks for the users in the audience.
The SharePoint Timer job service isn’t running
If the SharePoint timer service isn’t running, then none of the DocRead timer jobs will run, please ensure that this service is activated.
A DocRead timer job was ‘run immediately’
If one of the DocRead timer jobs was ‘run immediately’ from Central Admin and not configured back to a schedule, then this will effectively have stopped that job. Please ensure, that the timer jobs are scheduled.