Office could not Create the work file on Rds

Question

Hello,

I have a strange issue today with office on Rds.

I have:

• 1 RDS broker in W2012R2
• 2 RDS serveur in Windows 2016
• Office 2016
• Users profiles are set in Ad
• 1 GPO with folder redirection in a share
• Home folder in another one (dont know why)

I have just one user with this issue.

When he open Outlook or Word he has the error message :

"Could Not Create the Work File. Check the Temp Environment Variable"

But the softs works fine.

When he tried to open an attached file (pdf, word etc...) he has a message who said he dont have permissions to create a file to the local admin inetcache folder.

When he tried to save a word file he has the message "file path is too long".

I have check some points:

• Recreate totaly user profile and redirection do the same
• Temp Environment Variable point to the good location %username%...\inetcache but there are no file in it.
• Redirection works fine

It's just on one user the others dont have any problem.

(I prefer upd but it's historicaly like that)

Thanks you in avance if you have any Idea or suggestion.

Answer 1

Hello Pierre,

Thank you for your question and for reaching out with your question today.

The error messages you are encountering in Outlook and Word, such as "Could Not Create the Work File" and "File path is too long," indicate that there might be issues with the user's profile and permissions on the RDS environment. Here are a few steps you can take to troubleshoot and resolve the issue:

1. Check the user's permissions: Ensure that the user has the appropriate permissions on the RDS server, including read/write access to their profile folders, temporary folders, and the location where the files are being saved. Verify that the user has the necessary permissions to access and modify the local admin inetcache folder.
2. Verify folder redirection settings: Double-check the folder redirection GPO settings to ensure that they are correctly configured and applied to the user. Ensure that the user's profile folders, such as Documents, Desktop, and AppData, are redirected to the correct network location. Verify that the redirection is functioning properly by creating and modifying files in the redirected folders.
3. Clear temporary files: Have the user manually clear the temporary files on the RDS server. In File Explorer, navigate to the user's profile folders (e.g., %USERPROFILE%\AppData\Local\Temp) and delete all temporary files. Additionally, clear the contents of the local admin inetcache folder.
4. Check file path length: Verify that the file path where the user is trying to save files is not exceeding the maximum path length limit (260 characters). If it exceeds the limit, try shortening the file path by renaming folders or saving to a different location.
5. Run Office repair: Use the Microsoft Office repair feature to scan and repair any potential issues with the Office installation. Open the Control Panel, go to Programs, find Microsoft Office in the list, and choose the Repair option. Follow the on-screen instructions to complete the repair process.
6. Test on a different user profile: Create a temporary test user account with similar permissions and settings as the affected user. Log in with the test account and check if the same issues occur. This will help determine if the problem is specific to the user profile or a system-wide issue.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Best regards.