Yulia Kovalskaya 

Come on Yulia... you should know we need more info than that:

Go through these:

1. click that link (1) and see if it finds any existing posts in the community that might help solve your issue.
2. click that link (2) and see if the KB contains a solution
3. save the error stack to your desktop and attach that to your next reply since this contains the detail that could really help

Screenshots of the error window rarely tell us enough about the problem.

Dear Paul!

Here I am. Again

You were right. The error disappeared with one click: by pausing OneDrive sync...

Nevertheless, attaching the error log file herein:

<SDLErrorDetails time="08/04/2025 9:30:39">
  <ErrorMessage>No se puede encontrar una parte de la ruta de acceso 'C:\Users\cperezr\AppData\Local\Temp\SDLTempFileRegen\sdlxliff_41e01010-8710-4482-adfc-fc8c502620b2.tmp'.</ErrorMessage>
  <Exception>
    <Type>System.IO.DirectoryNotFoundException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>mscorlib</Source>
    <HResult>-2147024893</HResult>
    <StackTrace><![CDATA[   en System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   en System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   en System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   en System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)
   en System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
   en System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
   en Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileWriter.WriteSdlXliffToFile(String tempOutputFile)
   en Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileWriter.Complete()
   en Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.Complete()
   en Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.Complete()
   en Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.Complete()
   en Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
   en Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
   en Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.SaveBilingualImpl(String[] bilingualFilePaths, Boolean copy, IJobExecutionContext context, Boolean isAutoSaved)
   en Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.Save(IJobExecutionContext context)
   en Sdl.TranslationStudio.Api.Editor.SaveJobRequest.Execute(IJobExecutionContext context)
   en Sdl.Desktop.Platform.Implementation.Services.JobExecuter.Execute(JobData jobData)
   en Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter`1.ExecuteWithResourceLogging(TCommandData commandData, String message)
   en Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
   en System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   en System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>Trados Studio</ProductName>
    <ProductVersion>Studio16</ProductVersion>
    <EntryAssemblyFileVersion>16.2.12.9338</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Enterprise</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>3082</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>TALGO\cperezr</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>LES00137</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8231036 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

I also looked through other users´ comments ...and , yes, it´s all the same. OneDrive is evil for Trados resources:).

As far as I can understand, there are only two options: pausing the sync funciton at the beginning of the day and then letting it perform one sync for backup reasons before finishing work (cloud option is out of our reach, unfortunately). Oder?...:)

Yulia Kovalskaya 

Yulia Kovalskaya said:

here are only two options: pausing the sync funciton at the beginning of the day and then letting it perform one sync for backup reasons before finishing work (cloud option is out of our reach, unfortunately). Oder?...:)

Oder... place your Studio files in a folder that is not on the OneDrive Path.

Yulia Kovalskaya said:

Nevertheless, attaching the error log file herein:

That error could be caused by OneDrive indeed.  The error is "A part of the path could not be found..." which means that when Trados Studio tried to save a bilingual file, the temporary directory or the file it expected no longer existed at the moment it tried to write to it.

OneDrive is known to sometimes:

• Offload files from the local system, especially in AppData\Local\Temp, which it may treat as redundant if files haven’t been accessed recently.
• Interfere with file creation or deletion in synced folders, particularly if multiple sync states conflict (e.g., local deletion vs cloud availability).
• Lock or delay file availability if the sync status is in flux (e.g., "Sync pending").

If AppData\Local\Temp is under OneDrive management - which sometimes happens if OneDrive has been configured to back up Desktop, Documents, and other user folders, including parts of AppData - this could easily cause the folder to disappear or be inaccessible mid-operation.

Ooook! So maybe we could ask the IT department to configure a dedicated folder for our translation stuff that would not be backed up by OneDrive?? I will explain them the particularity of our files and maybe they offer some solution. Anyway, sync OFF will always be the quickest and the easiest one!

And, Paul!....No "thank you" is enough to show my gratitude for all your help over these ...years!!!!

Yulia Kovalskaya 

Yulia Kovalskaya said:

So maybe we could ask the IT department to configure a dedicated folder for our translation stuff that would not be backed up by OneDrive??

That's one solution.  They could also revert the Documents folder to its original local path by following these steps:

• Right-click on the Documents folder in File Explorer and select Properties.
• Navigate to the Location tab.
• Click on Restore Default, then apply the changes.

This action will move the Documents folder back to its default location on your local drive allowing users to control what they want on OneDrive rather than defaulting every piece of software you install.

However, this would definitely have to be done in conjunction with your GroupIT as it most likely has wider implications for their overall data management strategy.

Ultimately the best solution so software providers are not always fighting with Microsoft is for software providers, like us, to support installation with customisable paths for user data and not just follow Microsofts lead.  Something I hope we can address in the future.

Yulia Kovalskaya said:

No "thank you" is enough to show my gratitude for all your help over these ...years!!!!

Be careful... you'll ruin my reputation as a snarky and rude individual!

Paul said:

However, this would definitely have to be done in conjunction with your GroupIT as it most likely has wider implications for their overall data management strategy.

Great, we will see what can be done to eliminate these type of errors! Doesn´t look like something requiring too much effort from the IT-department! And less, with your advices!

Paul said:

Be careful... you'll ruin my reputation as a snarky and rude individual!

Yeah, I´ve read some hardcore stuff in some posts.... But, honestly, I like you being snarky :). Because when you are, it´s never unjust! ;)