Session hosts, Remote app hosts and office document upload center

Hi

I currently have two Remote desktop Collections that consist of the following:

2 Desktop Session hosts with User Profile disk share, lets call them Desktop1, Desktop2 and  \\share\desktop

2 Remote app Session hosts with User Profile disk share, lets call them Remote1, Remote2 and \\share\remote

In both collections i am having issues with the Office document cache becoming corrupted.
this happens mostly when the user are logged on to a diffrent node then the one they were on previously.

For the Desktop users they recieve the error message and is able to correct the issue them selves, however they are frustrated that they have to go threw all the error messages.

But for my Remote app users the problem is worse:
They are using Dynamics AX and from there they can start a mail merge that wants to open Word.
If their document cache is corrupted they are never prompted with the error message and Dynamics AX becomes unresponsive.

how can i provide my users with a better experience 

June 18th, 2015 7:21am

Hi Kent,

Based on your description, there are several issues in your terminal services. Now I suggest you collect the event log first and check which fault module occurs your issue, and you can try to control the fault module to look for methods to solve your issue.

Press Win + R, type "eventvwr" in the blank box, press Enter. In the Event Viewer, browse to Applications and Services Logs\Microsoft\Windows\Terminal Services, there may be some errors after the crash.

If your issue still exists or you need more help with terminal services, please post your issue to Terminal Services Forum.

https://social.technet.microsoft.com/Forums/office/en-US/home?forum=winserverTS

The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.

Regards,

George Zhao
TechNet Community Support

Free Windows Admin Tool Kit Click here and download it now
June 19th, 2015 8:01am

Ok i will try and post my question in the Terminal Services Forum.

I don't believe that my Terminal Servers are at fault, everything else works fine, only the document cache is corrupt periodicly, and search the internet shows i am not the only person that has frustrations with the cache feature.
No errors apart from "the Document cache is corrupt" is generated. 

No actual programs crash, the Office Document Upload Center simply states:

The cache is corrupt, would you like to repair. after saying yes it then states repair failed would you like to rename the folder and create a new cache folder. after accepting this the user can continue working.

The reason AX becomes unresponsive is the upload center has taken focus but not displaying on the remote app users screen.

I have Created a Group Policy user preference that deletes the Document cache folder upon login.
This prevents the document cache from being corrupted as the folder is created at launch of an office program.
This is not a permanent solution, but my users are no longer bothered by the issue.

The new post can be found here

https://social.technet.microsoft.com/Forums/office/en-US/9919e7ca-a5b2-4752-ac86-c455695f5112/session-hosts-remote-app-hosts-and-office-document-upload-center?forum=winserverTS

should any one feel like going down the rabbit hole.


June 19th, 2015 8:23am

Hi Kent,

Based on your description, did you get the error message as shown in the following figure? I suppose I maybe misread your issue.

If yes, this happens because the Microsoft Office document cache is corrupted, unusable and unrepairable. You can try to delete it and have Microsoft Office create a fresh cache for its documents.

Please refer to this article and try the method and check if it works for you.

http://www.7tutorials.com/fix-problems-microsoft-office-document-cache-being-corrupted

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

And you said you >>rename the folder and create a new cache folder. <<, did you create the new cache folder by these steps?

And you can also refer to this issue post:

http://answers.microsoft.com/en-us/office/forum/office_2013_release-office_storage/csisyncclientexe-consuming-cpu-on-win-81-microsoft/1c0954ff-0588-4211-9e5b-bd91081d61f6

Hope its helpful.

Regards,

George Zhao
TechNet Community Support

Free Windows Admin Tool Kit Click here and download it now
June 19th, 2015 9:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics