Export (0) Print
Expand All
Expand Minimize

Word Automation Service timer job is not running (SharePoint Server 2010)

SharePoint 2010

Published: August 5, 2010

Rule Name: A Word Automation Services timer job is not running

Summary: Critical state of this SPHA rule indicates that the Word Automation Services Timer Job is not running when it should be running.

Cause: Word Automation Services uses a custom Timer Job to pull conversion items from the Word Automation Services database and then assign those conversion items to individual application servers. If the custom Timer Job does not run then conversion items cannot begin to convert.

Resolution: Enable the timer job by using the Central Administration Web site

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.

  2. On the home page of the Central Administration Web site, click Monitoring.

  3. Click Review Job definitions.

  4. Click Word Automation Services Timer Job.

  5. Click Enable.

Resolution: Enable the timer job by using Windows PowerShell

  1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.

  2. On the Start menu, click All Programs.

  3. Click Microsoft SharePoint 2010 Products.

  4. Click SharePoint 2010 Management Shell.

  5. At the Windows PowerShell command prompt, type the following command:

    Enable-SPTimerJob "Word Automation Services"
    

For more information, see Enable-SPTimerJob.

Resolution   Verify that the Word Automation Services service is provisioned correctly

  1. To verify that the Word Automation Services service is provisioned correctly, see Configuring Word Automation Services for Development.

Resolution   See other troubleshooting information

  1. For additional trouble shooting steps, see Word Automation Services Troubleshooting (SharePoint Server 2010).

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft