Your Office Solution Here

Powered by Microsoft China IW(Office/EPM/SharePoint) Team

DO NOT install the Office Web Apps in the DC, Office Web Apps would not work and Word Automation Service would crash

DO NOT install the Office Web Apps in the DC, Office Web Apps would not work and Word Automation Service would crash

  • Comments 1
  • Likes

[作者: 林冠斌工程师 , Office/Project支持团队, 微软亚太区全球技术支持中心]

[Author: Keith Lin, Office/Project Support Team, Microsoft Asia Pacific Global Support Center]

This would happened after you install SharePoint 2010 SP1.

 

Symptom

======================

  1. Word Automation Service never generate the destination file (maybe pdf, may be xps or other if the convertor support)
  2. When the Word Automation Service Timer Jobs runs, WordServerWorker.exe would keep crashing in the task manager.
  3. CPU might keep high consuming (but I did not verify, I only see this in the customer environment, I have few resource to research why).

 

You would see the below symptom in the ULS log and this will keep generating:

 

01/13/2012 16:06:12.18  w3wp.exe (0x2CA4)       0x151C  Word Automation Services          Office Viewing Architecture                f2yg       Medium               CreateSandBoxedProcessWorker() is called       

01/13/2012 16:06:12.18  w3wp.exe (0x2CA4)       0x151C  Word Automation Services          Office Viewing Architecture                bl3q       Verbose               AddILToken():  fIntegritySet:1, dilDesiredIntegrity:2       

01/13/2012 16:06:12.18  w3wp.exe (0x2CA4)       0x151C  Word Automation Services          Office Viewing Architecture                c12c       Verbose               AddILAce(): fIntegritySet:1, dilDesiredIntegrity:2             

01/13/2012 16:06:12.20  w3wp.exe (0x2CA4)       0x151C  Word Automation Services          Office Viewing Architecture                b10e      Medium               Created desktop: Service-0x0-98ddc741$\Microsoft Office Isolated Environment             

01/13/2012 16:06:12.20  w3wp.exe (0x2CA4)       0x151C  Word Automation Services          Office Viewing Architecture                c12c       Verbose               AddILAce(): fIntegritySet:1, dilDesiredIntegrity:2             

01/13/2012 16:06:12.20  w3wp.exe (0x2CA4)       0x151C  Word Automation Services          Office Viewing Architecture                2brt        Medium               AppWorker:94581f17-cc42-4dc8-8816-222ca926057a worker process is started Exe: WordServerWorker.exe Args: /id 94581f17-cc42-4dc8-8816-222ca926057a /convertingService net.pipe://127.0.0.1/WordServer7237b2b7-ef89-4fcd-9ef0-4cff03f29287 /assembly WdsrvWorker.dll /type WACWS /IsBatchedTracing True /LogQuota 100 WorkerType: WorkerType1 Directory: c:\windows\system32\inetsrv, pid : 6432, IsSandBoxed: True, UniqueSandBoxSid: S-1-5-26473-19571-45394-2039

01/13/2012 16:06:12.20  w3wp.exe (0x2CA4)       0x151C  Word Automation Services          Office Viewing Architecture                vioz        Medium               RemoveWorker isRemoved: True session id : uuid:98279299-9ed6-4f72-8c36-12498adf2d0e;id=2038, Guid: 712a4087-1169-4d3e-b282-e194e094b3e8

01/13/2012 16:06:12.20  w3wp.exe (0x2CA4)       0x2F90  Word Automation Services          Office Viewing Architecture                4sig        Medium               ChildProcess WordServerWorker.exe is launched inside worker 94581f17-cc42-4dc8-8816-222ca926057a. Pid 6432     

01/13/2012 16:06:12.20  w3wp.exe (0x2CA4)       0x2F90  Word Automation Services          Office Viewing Architecture                d9hn      Medium               NotifyNewChildProcessInWorker has seen WordServerWorker.exe in worker 94581f17-cc42-4dc8-8816-222ca926057a   

01/13/2012 16:06:12.68  w3wp.exe (0x2CA4)       0x36A4 Word Automation Services          Office Viewing Architecture                viou       Medium               ... registering worker 94581f17-cc42-4dc8-8816-222ca926057a    

01/13/2012 16:06:12.73  w3wp.exe (0x2CA4)       0x36A4 Word Automation Services          Office Viewing Architecture                viox        Medium               Worker 94581f17-cc42-4dc8-8816-222ca926057a is now initialized.            

01/13/2012 16:06:12.87  w3wp.exe (0x2CA4)       0x36A4 Word Automation Services          Office Viewing Architecture                vipx        Monitorable       AppWorker:94581f17-cc42-4dc8-8816-222ca926057a application server host exited unexpectedly  (thread: 682)       

01/13/2012 16:06:12.87  w3wp.exe (0x2CA4)       0x36A4 Word Automation Services          Office Viewing Architecture                c78j        Unexpected       AppWorker:94581f17-cc42-4dc8-8816-222ca926057a ProcessRequestDone() received error response WorkerCrashed, restarting the worker  

01/13/2012 16:06:12.87  w3wp.exe (0x2CA4)       0x36A4 Word Automation Services          Office Viewing Architecture                d1z7       Verbose               StopProcess() guid=94581f17-cc42-4dc8-8816-222ca926057a, thread=682             

01/13/2012 16:06:12.88  w3wp.exe (0x2CA4)       0x36A4 Word Automation Services          Office Viewing Architecture                xpre       Medium               Removing worker 94581f17-cc42-4dc8-8816-222ca926057a, thread: 682 

 

And the AppWorker would crash every second:

 

01/13/2012 16:05:55.45  w3wp.exe (0x2CA4)       0x266C  Word Automation Services          Office Viewing Architecture                c78j        Unexpected       AppWorker:732b937f-33e2-4815-bb30-4435d4607bf8 ProcessRequestDone() received error response WorkerCrashed, restarting the worker  

01/13/2012 16:05:56.15  w3wp.exe (0x2CA4)       0x151C  Word Automation Services          Office Viewing Architecture                c78j        Unexpected       AppWorker:a88c1161-e36e-42c8-b3ed-082c1dc1aab5 ProcessRequestDone() received error response WorkerCrashed, restarting the worker  

01/13/2012 16:05:56.92  w3wp.exe (0x2CA4)       0x266C  Word Automation Services          Office Viewing Architecture                c78j        Unexpected       AppWorker:4d374cd6-9316-4261-84ff-40c4cf8101c5 ProcessRequestDone() received error response WorkerCrashed, restarting the worker  

01/13/2012 16:05:57.63  w3wp.exe (0x2CA4)       0x151C  Word Automation Services          Office Viewing Architecture                c78j        Unexpected       AppWorker:2cbca247-f527-4d5a-8d4e-e388400f8031 ProcessRequestDone() received error response WorkerCrashed, restarting the worker  

01/13/2012 16:05:58.40  w3wp.exe (0x2CA4)       0x266C  Word Automation Services          Office Viewing Architecture                c78j        Unexpected       AppWorker:5bc6e6ef-59ca-4398-bcbd-4460cba9ab1d ProcessRequestDone() received error response WorkerCrashed, restarting the worker  

01/13/2012 16:05:59.13  w3wp.exe (0x2CA4)       0x151C  Word Automation Services          Office Viewing Architecture                c78j        Unexpected       AppWorker:659b2c18-3d98-4b72-96f3-12aea0c81231 ProcessRequestDone() received error response WorkerCrashed, restarting the worker  

01/13/2012 16:05:59.82  w3wp.exe (0x2CA4)       0x266C  Word Automation Services          Office Viewing Architecture                c78j        Unexpected       AppWorker:9f0e400d-e5a0-4ce8-a3ee-65246b74114d ProcessRequestDone() received error response WorkerCrashed, restarting the worker  

 

Reference

=======================

Here is the Office Web Apps deployment guide, and it emphasize that DO NOT install with DC.

http://technet.microsoft.com/en-us/library/ff431687.aspx

 

Here is another article, possible workaround when the Office Web apps is installed on the DC (I test this and it only works for Office Web App, the Word automation service symptom is still not resolving. We DON’T suggest customer to do this. If customer really insist, we could provide but make statement very clearly, take own risks).

http://gallery.technet.microsoft.com/scriptcenter/44ac3193-e7cc-4428-ae14-98177b5feab2

 

Comments
  • thank you

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment