"Unable to find the specified file" error when trying to load a local termbase to Trados Studio 2024

Hello,

I was working in a project with a termbase created and stored in a shared folder. It worked all fine until I decided to update the termbase.

Since the termbase has been created from an XLSX glossary, I just created a new SDLTB from that XLSX file through the standalone Glossary Converter app in the same shared folder stated above.

When I tried to use this newly created SDLTB in my project, I got an "Unable to find the specified file" error. Since I am aware Trados has some problems dealing with termbases stored in shared folders, I moved the SDLTB to a local folder (under my C:\Users\[MyUserName]\Documents\ folder).

To my surprise, I still get the same "Unable to find the specified file" error. I tried repairing Trados installation, but the result is the same.

I am using Trados Studio 2024 - 18.0.2.3255 on a Windows 10 Pro laptop (64 bits).

Could anyone help with this?

Kind regards,

Manuel

emoji
Parents
  • See full stack trace below:

    <SDLErrorDetails time="30/04/2025 10:51:12">
      <ErrorMessage>Unable to find the specified file.</ErrorMessage>
      <Exception>
        <Type>System.IO.FileNotFoundException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
        <FileName />
        <FusionLog />
        <HelpLink />
        <Source>Sdl.TranslationStudio.Terminology</Source>
        <HResult>-2147024894</HResult>
        <StackTrace><![CDATA[   at Sdl.TranslationStudio.Terminology.FileTermbase.FileBasedTerminologyProvider.Initialize()
       at Sdl.TranslationStudio.Terminology.FileTermbase.FileBasedTerminologyProviderWinFromsUI.Browse(IWin32Window owner, ITerminologyProviderCredentialStore credentialStore)
       at Sdl.TranslationStudio.ProjectManagement.Terminology.ProjectTermbasesControl.UseTerminologyProviderPlugin_OnClick(Object sender, EventArgs e)
       at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
       at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
       at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
       at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
       at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
       at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
       at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
       at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
       at System.Windows.Forms.ToolStrip.WndProc(Message& m)
       at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
      </Exception>
      <Environment>
        <ProductName>Trados Studio</ProductName>
        <ProductVersion>Studio18</ProductVersion>
        <EntryAssemblyFileVersion>18.0.2.3255</EntryAssemblyFileVersion>
        <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
        <ServicePack>NULL</ServicePack>
        <OperatingSystemLanguage>3082</OperatingSystemLanguage>
        <CodePage>1252</CodePage>
        <LoggedOnUser>DESKTOP-B7O1942\Manuel</LoggedOnUser>
        <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
        <ComputerName>DESKTOP-B7O1942</ComputerName>
        <ConnectedToNetwork>True</ConnectedToNetwork>
        <PhysicalMemory>8271480 MB</PhysicalMemory>
      </Environment>
    </SDLErrorDetails>

    I tried resetting Trados to default settings, but same error keeps appearing.

    Any other help would be much appreciated.

    Kind regards,

    Manuel

    emoji
  •  

    I know you seem to have discussed the OneDrive thing already, but I do think you should validate what you're doing very carefully and don't assume that your 'local' is local just because it's on your computer.  Check the actual path to your 'local'.  You can get a good explanation just by dropping your error stack into ChatGPT.  For example... and the powershell script idea came from AI as well, and if you can use powershell it might be interesting to have it just as a quick check because it's not always obvious.

    ===========================================================

    This error:

    Unable to find the specified file.
    System.IO.FileNotFoundException
    Source: Sdl.TranslationStudio.Terminology
    

    suggests that Trados Studio was attempting to access a file—most likely a termbase or terminology provider file—but it could not be found at the expected location.

    Why OneDrive might be the culprit

    If the file (e.g., a .sdltb termbase) is stored in a OneDrive-synchronised folder, a few common OneDrive behaviours can cause this error:


    1. Files on Demand (Cloud-Only Files)

    OneDrive may mark some files as "online-only" to save disk space. These are visible in File Explorer but not actually present on disk until opened.

    • If Trados tries to load a .sdltb file that OneDrive has marked as "cloud-only", it will not be able to access the physical file and will throw a FileNotFoundException.


    2. Path Confusion due to Syncing

    Sometimes the expected path might have changed:

    • If the file was originally on C:\Users\Manuel\OneDrive\... and OneDrive desynchronised or changed folder structure (e.g., after a reinstall or re-login), the path may now be invalid, even though the file still "exists" in your OneDrive cloud account.


    3. Permissions or Locking

    OneDrive may also occasionally lock or delay availability of files during syncing operations, meaning Trados might try to access the file before it is fully available.


    Recommendation

    To confirm and fix:

    1. Locate the missing termbase file manually – Check if it's marked as "Available when online only" in File Explorer.

    2. Right-click and choose "Always keep on this device" – This will force OneDrive to download it locally.

    3. Check the actual file path in Trados – Go to Project Settings > Termbases and ensure the termbase path is valid.

    4. Avoid placing working files (especially termbases) in OneDrive – Instead, work from a local directory and back up to OneDrive separately if needed.

    Would you like help writing a PowerShell script to verify OneDrive status of specific files?

    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
  • Thank you for the explanation,  

    Based on your explanation, I assumed that if I recreated the termbase from a completely new and local file, it should work. Thus, I tried to do the following:

    1. I opened a blank spreadsheet in Excel.

    2. I copied the contents of a local copy of the XLSX glossary into this new Excel file and saved it on a local folder.

    3. Created a SDLTB from this new XLSX file through Glossary Converter (version 6.4.9138.36048).

    4. Tried to use it in the Trados Studio project.

    5. Same error keeps appearing.

    I do not know how to use PowerShell. Would that help to fix the issue or am I doing something wrong?

    Kind regards,

    Manuel

    emoji
  •  

    I copied the contents of a local copy of the XLSX glossary into this new Excel file and saved it on a local folder.

    Can you share the full path to your local folder?

    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
Reply Children