Error during project finalisation : file does not exists

Hi

Our Trados Studio 2022 software is installed on a (Windows )Remote Desktop Server (RDS) solution.
All files that we are using with Trados Studio are located on a shared drive hosted by the domain controller's machine and mounted on the RDS server as a remote drive.

We have several transaction project managers who are using this architecture. For one of them only, sometimes when she finalises a project she receives the error :

FIle xxx does not exist.

When we copy the same file on a computer drive not shared, sometimes she can achieve the process and sometimes the same error appears.

See the pictures below.

After the 3 screens seen in the picture are closed, the Trados Studio simply crash the application. 

It appears only for one user the job can be done by another user with the same file and the file will be processed without any error.

Does anybody get this situation on his side? What should we do to avoid this

Let me know if you have any questions.

Thanks for your help.

Regards

Error message in Trados Studio task results showing 'File does not exist' for a file on a remote drive.

Trados Studio error dialog box with message 'Project save failed' and an 'OK' button.Detailed error message in Trados Studio indicating a specific file on a network path is not found.



Generated Image Alt-Text
[edited by: Trados AI at 1:04 PM (GMT 0) on 29 Feb 2024]
emoji
  •  

    Seems to be a user specific issue so I would look there:

    1. User Permissions: The affected user might not have the necessary permissions to access the file on the shared drive. Verify that this user has the same level of access as other users who do not experience the problem.

    2. Corrupted User Profile: The user profile on the RDS might be corrupted. Try recreating the user profile to see if this resolves the issue.

    3. Network Issues: Since the file is on a shared network drive, intermittent network issues might be causing the file to appear unavailable. Checking the network stability and the connection to the shared drive might reveal problems.

    4. Path Length Limitation: Windows has a MAX_PATH limitation which limits the file path length to 260 characters. If the path to the file exceeds this limit, it might not be accessible. Try shortening the file path or enabling long path support on the server.

    5. File Locking Issues: If the file is locked by another process, it could lead to this error. Ensure that no other processes are using the file when the affected user attempts to access it.

    6. Antivirus or Security Software: Sometimes, security software can interfere with the access to files on network drives. Check any installed antivirus or security software for false positives or overzealous protection settings.

    7. File Corruption: The file itself might be corrupt. Since copying the file to a local drive sometimes works, try creating a new copy of the file from a version that is known to work.

    8. Mapping Drive: Try mapping the network location to a drive letter as this can simplify path handling.

    All guesses to be honest!

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji