Microsoft Office Document Cache has stopped working. What you should know about msosync.exe Microsoft Office Document Cache. Msosync.exe is not part of Windows. Aug 4, 2014 - We have encountered this problem ourselves and it took us a bit of time in order. Solutions that may or may not work, we have decided to publish this step by step. If the Microsoft Office document cache gets corrupted, each time the. The problem should be gone and you should no longer encounter the.
Hi All, I have a windows service to auto refresher Excel (I have to do that), the application will auto lunch Excel and refresh it. But recently after running more than 1 day, all the Excel processes will hang then no Excel can be refreshed, then I have to reboot the Production Server. I found the error for each Excel process, the event time exactly match the Process start time. I have disabled the alert in service (ExcelObj.DisplayAlerts = false) but the alert in Event Viewer indeed. Microsoft Excel A problem occurred while accessing the Office Document Cache. Do you want to repair this problem? P1: 701941 P2: 14.0.6029.1000 P3: e8d8 P4: And since this is windows service, no user will response to this albert so I saw lots of hanging processes.
The questions is: Why our Excel need to access to Office Document Cache? And how can resolve this issue so I don’t need to manually reboot the server everyday. I think the error is refering to the history log of recent files opened from office. The recent files are in the registry so when you open a new file you can see the list. There is an option in workbooks.open() method called AddToMru to disable the update of recent files. The default is False. Are yo setting it True?
See following webpage I think you are running Office 2010 SP1 June 2008. 14.0.6029.1000 is the version of the following file: Sharepointdesigner2010sp1-kb2460057-x86-fullfile-en-us.exe I would download the latest updates to the sharepoint if you haven't already. See websites below. You mave want to check the Event Logs on the SharePoint to get additional information on your problem. Your error message that you posted is refering to a SharePoint Release number and not the Excel Version. Do you want to repair this problem? P1: 701941 P2: 14.0.6029.1000 P3: e8d8 P4: I suspect the problem is with running a script that opens and closes a large number of workbooks.
I think everytime a workbook is opened the filename is going into a cache and eventually the cache fills up. My one question is 'Does the error messages start at the same time the script starts or does the error messages start later'? My one question is 'Does the error messages start at the same time the script starts or does the error messages start later'? Yes, exactly the same time. I have checked those hanging Excel processes, the start time match the alert time in Event view.