Sign in
 
HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery
TechCenter >
> 
> 
SharePoint 2010 Office Web Apps issue; Office Web Apps occasionally stop working

问题 SharePoint 2010 Office Web Apps issue; Office Web Apps occasionally stop working

  • Friday, October 28, 2011 4:19 PM
     
      Has Code
    Sign In to Vote
    0

    Hello,

    In our SharePoint 2010 environment, Office Web Apps occasionally stop working and produces an error.  Depending on which app it is, the error changes.  If OneNote starts failing, the error is "This notebook cannot be opened for editing".  Not all apps break at once and only one web front end is affected at a time (our environment has two total).  Basically, I'll get a call from an end user saying "I can't edit the following Word doc on SharePoint".  I'll check to see which server their session is on, create a session on that server, and see that the Word doc is failing to load with an error similar to the one above.  I then check to see if I can edit OneNote, PowerPoint, and Excel files and they all work fine.  I've also checked to see if I could edit a different Word document on the same web app and it fails with the same error.  However, if I load a Word document on a different web app that runs in a different app pool, the document loads fine.  I then run IISRESET on the affected server and that corrects the issue until it happens again.  It could be a month, a week, or even a few days until it starts happening again.  This happens on both of our WFE servers, just never at the same time.  

    I've enabled verbose logging for Office Web Apps and found the following in the ULS logs, but unfortunately, the error does not say what account is being denied access or what it is being denied access to.  Here's the error:

    csi server sandbox work throw exception: System.TypeInitializationException: The type initializer for 'Microsoft.SharePoint.Utilities.SandboxCommunicator' threw an exception. ---> System.ComponentModel.Win32Exception: Access is denied    
 at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)    
 at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)    
 at System.Diagnostics.Process.OpenProcessHandle()    
 at System.Diagnostics.Process.get_Handle()    
 at Microsoft.SharePoint.Utilities.SandboxCommunicator..cctor()     -
 -- End of inner exception stack trace ---    
 at Microsoft.SharePoint.Utilities.SandboxCommunicator.UnmarshalStreamFromSandbox()    
 at Microsoft.SharePoint.Utilities.SPUtility.PerformSandboxOperation(SandboxCommunicator communicator, ExecuteCellStorageBinaryRequestParameters paramVals)    
 at Microsoft.SharePoint.Utilities.SPUtility.ExecuteCellStorageBinaryRequest(SPFile spfile, Boolean fileExists, Stream request, Boolean coalesce, Guid& partitionID, String userName, Boolean coauthVersioning, String etagMatching, Boolean fExpectNoFileExists, String contentChangeUnit, String clientFileID, String bypassSchemaID, Int64 nLockType, String lockID, Int64 nTimeout, Boolean createParentFolder, String& etagReturn, Boolean& allRequestSucceeded, Int32& coalesceHRESULT, String& coalesceErrorMessage, Boolean& containHotboxData, Boolean& haveOnlyDemotionChanges, Int32& binaryReqCountQuota)


    The error above was captured the last time the OneNote web app failed. 

    Is anyone else experiencing this issue or know better yet, know how to resolve it?  I'm guessing SharePoint is being denied something on the IIS level, but I have no idea what.  I'm glad that I can temporarily resolve the issue by running IISRESET, but I need to get a long term solution.

    Thanks,

    Tim

     

All Replies

  • Monday, October 31, 2011 9:19 AM
     
     
    Sign In to Vote
    0

    Hi,

     

    From the error message “access is denied”, there might be a problem with the permissions for the service account that is used to run the Web application or one of the Office Web Apps services: Excel Calculation Services, PowerPoint Service, or Word Viewing Service. The Web application and service applications must have the appropriate permissions to access the content databases and the configuration database.

     

    Verify that the service account permissions for the Web application and the Office Web Apps services are appropriate. The Web application and service applications must have the appropriate permissions to access the content databases and the configuration database. For information about the appropriate service account permissions for the Web application and the Office Web Apps services, see Account permissions and security settings (SharePoint Server 2010).

     

    Thanks,

    Rock Wang

    Regards, Rock Wang Microsoft Online Community Support
     
  • Wednesday, November 02, 2011 6:40 PM
     
     
    Sign In to Vote
    0

    Hi,

     

    From the error message “access is denied”, there might be a problem with the permissions for the service account that is used to run the Web application or one of the Office Web Apps services: Excel Calculation Services, PowerPoint Service, or Word Viewing Service. The Web application and service applications must have the appropriate permissions to access the content databases and the configuration database.

     

    Verify that the service account permissions for the Web application and the Office Web Apps services are appropriate. The Web application and service applications must have the appropriate permissions to access the content databases and the configuration database. For information about the appropriate service account permissions for the Web application and the Office Web Apps services, see Account permissions and security settings (SharePoint Server 2010).

     

    Thanks,

    Rock Wang

    Regards, Rock Wang Microsoft Online Community Support

    Hi Rock,

    I've double checked permissions (but will triple check) previously but I really don't think this is the issue.  The OneNote web app should just work without any additional configuration so I don't really see how it could be perms.  Also, if it were perms, it should be consistently failing, not work for days and then suddenly die.  Maybe I'm wrong, but I just can't see this being a perms issue.

    Tim

     
  • Tuesday, November 22, 2011 11:51 AM
     
     
    Sign In to Vote
    0

    Hello Tim,

    Were you able to find the cause or solution to this? I get the same error as well. I also get this error when opening the file through the office client after it has failed to open in the browser. However If I just open it in the client always it works correctly.

    Any help will be much appreciated.

    Cheers,

    Sabrish

     



    • Edited by Sabrish Tuesday, November 22, 2011 12:39 PM
    •  
     
  • Tuesday, November 22, 2011 3:54 PM
     
     
    Sign In to Vote
    0

    Hello Tim,

    Were you able to find the cause or solution to this? I get the same error as well. I also get this error when opening the file through the office client after it has failed to open in the browser. However If I just open it in the client always it works correctly.

    Any help will be much appreciated.

    Cheers,

    Sabrish

     



    Aside from resetting IIS every time it happens, unfortunately no.  I will update if I come across a fix and hope you will do the same.

    Thanks,

    Tim

    • Proposed As Answer by al kerr Friday, February 24, 2012 4:55 PM
    • Unproposed As Answer by al kerr Friday, February 24, 2012 4:55 PM
    •  
     
  • Friday, February 24, 2012 4:57 PM
     
     
    Sign In to Vote
    0

    Hi,

    I had the same issue and it turned out to be the client integration settings in the Authentication Providers. I wrote a blog about how I fixed it, http://onefootinthecloud.blogspot.com/2012/02/this-document-cannot-be-opened-for.html

    Al

    • Proposed As Answer by WebAsh Monday, May 14, 2012 5:55 AM
    • Unproposed As Answer by Tiiiimmyyyyyyy Monday, May 14, 2012 2:11 PM
    •  
     
  • Wednesday, April 04, 2012 7:37 PM
     
     
    Sign In to Vote
    0

    Still a problem I'm afraid. I get the same error in my logs but it only happens sporadically. We get a rash of problems opening office files that only affects certain file types (Excel, OneNote, Word, etc). I tried an IISRESET and it fixed the problem for a few seconds and then I got the error again.

    This doesn't happen consistently so it's not a problem in the permissions. I checked my client integration settings and that's enabled (which it would have to be to have been working all this time). If I wait a day or so the errors will stop and then start again a few days from now on some other file type. Just making no sense...


    • Edited by Keith Work Wednesday, April 04, 2012 7:38 PM
    •  
     
  • Monday, May 14, 2012 2:21 PM
     
     
    Sign In to Vote
    0

    Hi,

    I had the same issue and it turned out to be the client integration settings in the Authentication Providers. I wrote a blog about how I fixed it, http://onefootinthecloud.blogspot.com/2012/02/this-document-cannot-be-opened-for.html

    Al

    I unmarked this as an answer since it does not resolve the problem I am still experiencing in my environment.  We're currently on the December 2011 CU but it looks like the February might resolve this.  I plan to deploy the February 2012 CU to our test environment and will let everyone know how it goes.  Apparently this CU has some Office Web App fixes but after reading the release notes, it doesn't look like have any effect.  I'm still hopeful :x
     
  • Thursday, May 24, 2012 5:50 AM
     
     
    Sign In to Vote
    0

    Hi Tim,

    We are experiencing the same issue, but with OneNote only, and only for external requests coming via TMG.

    Have you applied the latest CU yet to see if it helps?

    Cheers,

    Ashley

     
  • Thursday, May 24, 2012 3:55 PM
     
     
    Sign In to Vote
    0

    Hi Tim,

    We are experiencing the same issue, but with OneNote only, and only for external requests coming via TMG.

    Have you applied the latest CU yet to see if it helps?

    Cheers,

    Ashley

    Hi Ashley,

    It was decided we're going to skip the February 2012 CU since it doesn't appear it will fix any of our ongoing issues.  I'll be sure to post a reply if I come across any fixes.

    Tim

    • Proposed As Answer by Scotlandv1 Wednesday, June 20, 2012 6:34 PM
    • Unproposed As Answer by Scotlandv1 Wednesday, June 20, 2012 6:35 PM
    • Proposed As Answer by Scotlandv1 Wednesday, June 20, 2012 6:35 PM
    • Unproposed As Answer by Tiiiimmyyyyyyy Wednesday, June 20, 2012 7:10 PM
    •  
     
  • Wednesday, June 20, 2012 6:37 PM
     
     
    Sign In to Vote
    0
    This issue that you are experiencing is fixed in the SharePoint patch of April Cumulative update 2012, the article is:  2598304
    • Edited by Scotlandv1 Wednesday, June 20, 2012 6:38 PM
    • Proposed As Answer by Scotlandv1 Wednesday, June 20, 2012 6:38 PM
    • Unproposed As Answer by Tiiiimmyyyyyyy Wednesday, June 20, 2012 7:10 PM
    •  
     
  • Wednesday, June 20, 2012 6:39 PM
     
     
    Sign In to Vote
    0
    I'll have to check this out.  Thanks for the reply.
     
  • Wednesday, June 20, 2012 7:10 PM
     
     
    Sign In to Vote
    0
    After looking at the release notes, I'm doubtful this will fix the issue.  I couldn't find anything in the notes about it fixing Excel web apps randomly crashing; it looks to only fix an issue with bitmap files.  I'll still deploy to test soon and see what happens.  I'll update in a week or so with my findings.
     
  • Monday, October 15, 2012 11:36 AM
     
     
    Sign In to Vote
    0

    Hi Timy,

    I also have this issue. It's random and users cannot edit word files it will always open as Read Only, when try to do edit in browser, it ends up with : This document cannot be opened for editing and ULS logs the error you have in your first post....

    IISReset will solve that...for a while :)

    Please let me know if you have any resolution. We are on February2012 CU

    Thanks

    Tomas

    Tomas Paulas MCP,MCSA,MCSA-Messaging

     
  • Monday, October 15, 2012 1:41 PM
     
     
    Sign In to Vote
    0

    Hi Timy,

    I also have this issue. It's random and users cannot edit word files it will always open as Read Only, when try to do edit in browser, it ends up with : This document cannot be opened for editing and ULS logs the error you have in your first post....

    IISReset will solve that...for a while :)

    Please let me know if you have any resolution. We are on February2012 CU

    Thanks

    Tomas

    Tomas Paulas MCP,MCSA,MCSA-Messaging

    Hi Tomas,

    We still have not found a long term fix for this.  I no longer manage my company's SharePoint environment but am still actively involved (and probably always will be since I built the thing :p ).  This issue has been put on the back burner for the time being but I will update if any solution is found.  Of course please let me know if you find a way to resolve this.

    Thanks!

     
  • Friday, May 03, 2013 4:32 PM
     
     
    Sign In to Vote
    0

    Hi there,

    We had the same issue and as a temporary resolution we found that running each Web Application in its own application pool worked for us (we have < 10 Web apps).  Not ideal, but it's only a temporary fix.

    We also contacted Microsoft support and we informed that the following hot fix resolves this behavior:   http://support.microsoft.com/kb/2598304

    We tested in our dev environment and can confirm that the hot fix resolves the issue for us.  We also tested the SharePoint 2010 Service Pack 2 beta to make sure the fix made it in to the upcoming service pack and can also confirm that SP2 beta resolves the issue for us.  It should be noted that the hot fix is quite large and contains many fixes, not just the one mentioned here.  The install alone took us ~ 1.5 hours and needs to run on each SharePoint server in your farm.

    Being somewhat risk averse, we generally avoid hot fixes unless they are critical.  So we plan to continue to run each Web app in its own app pool until SharePoint 2010 SP2 is released, and then we'll revert back to our original design.

    Todd Klindt has a great post on how to change the App Pool for a SharePoint Web Application using PowerShell, which makes the process very easy:

    http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=276

    We had to perform an IIS reset on our servers after running the final ProvisionGlobally() command, but after that we were good to go.

    Hope this helps,

    Emer
     

     
  • Monday, May 06, 2013 12:55 PM
     
     
    Sign In to Vote
    0

    Hi there,

    We had the same issue and as a temporary resolution we found that running each Web Application in its own application pool worked for us (we have < 10 Web apps).  Not ideal, but it's only a temporary fix.

    We also contacted Microsoft support and we informed that the following hot fix resolves this behavior:   http://support.microsoft.com/kb/2598304

    We tested in our dev environment and can confirm that the hot fix resolves the issue for us.  We also tested the SharePoint 2010 Service Pack 2 beta to make sure the fix made it in to the upcoming service pack and can also confirm that SP2 beta resolves the issue for us.  It should be noted that the hot fix is quite large and contains many fixes, not just the one mentioned here.  The install alone took us ~ 1.5 hours and needs to run on each SharePoint server in your farm.

    Being somewhat risk averse, we generally avoid hot fixes unless they are critical.  So we plan to continue to run each Web app in its own app pool until SharePoint 2010 SP2 is released, and then we'll revert back to our original design.

    Todd Klindt has a great post on how to change the App Pool for a SharePoint Web Application using PowerShell, which makes the process very easy:

    http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=276

    We had to perform an IIS reset on our servers after running the final ProvisionGlobally() command, but after that we were good to go.

    Hope this helps,

    Emer
     

    Thank you for providing a work around and links to those hot fixes.  I no longer support SharePoint for my organization but have passed this along to the individual who handles it.  This issue was really a thorn in my side and I'm sure it's plaguing the new guy as well.