"Probability score": 0.8

"Question improvement suggestion": Please provide any error codes that accompanied the "Unable to find the specified file" error message. Also, specify if there were any recent changes to your system or Trados Studio software.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Manuel,

It seems like you've already taken some good troubleshooting steps, such as moving the termbase to a local folder and attempting to repair the Trados Studio installation. Here are a few more steps you can try:

Step 1: Ensure that the path to the termbase file does not contain any special characters or spaces. This can sometimes cause issues with file recognition.

Step 2: Check if the termbase file is not open in another program or process. If it is, close the other program and try loading the termbase again in Trados Studio.

Step 3: Try creating a new project and adding the termbase to see if the issue is specific to the current project.

Step 4: If the issue persists, you might want to try reinstalling Trados Studio. Before doing so, make sure to back up any important data.

Step 5: If none of the above steps work, it might be a good idea to check for any updates for your Windows OS and Trados Studio. You can check for updates within the application.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

Thank you for your answer. Unfortunately, I am afraid none of those suggestions works. See below error stack trace:

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

As far as I know, there haven't been any recent changes in my system nor in Trados Studio Software between normal operation and this error.

RWS Community AI said:

Step 1: Ensure that the path to the termbase file does not contain any special characters or spaces. This can sometimes cause issues with file recognition.

Step 2: Check if the termbase file is not open in another program or process. If it is, close the other program and try loading the termbase again in Trados Studio.

Step 3: Try creating a new project and adding the termbase to see if the issue is specific to the current project.

Step 4: If the issue persists, you might want to try reinstalling Trados Studio. Before doing so, make sure to back up any important data.

Step 5: If none of the above steps work, it might be a good idea to check for any updates for your Windows OS and Trados Studio. You can check for updates within the application.

Step 1: Path is OK. I even moved the SDLTB to the main "Documents" folder and it does not work.

Step 2: The termbase is not open in another program or process.

Step 3: I tried adding this termbase to another project and the same issue appears. Curiously enough, this other project does have local termbases loaded from a local folder and they work normally.

Step 4: I'd rather try to find a solution before reinstalling. It takes quite a while to configure Trados to my likings (apps installed, settings, etc.) and I just purchased Trados Studio 2024 a couple of weeks ago.

Step 5: My Windows OS and Trados Studio are updated to the most recent version.

Any other help would be much appreciated!

Kind regards,

Manuel

"Probability score": 0.7

"Question improvement suggestion": Please provide more details about the error stack trace. Also, it would be helpful if you could share the exact steps you took when creating the new SDLTB from the XLSX file.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Manuel,

I understand that the previous suggestions did not resolve your issue. Given the error message you provided, it seems like the issue might be related to the specific SDLTB file you are trying to load. Here are a few additional steps you can try:

Step 1: Try opening the SDLTB file with a different application, such as MultiTerm, to see if the file itself is not corrupted.

Step 2: If you have access to another computer with Trados Studio installed, try to load the termbase there. This can help determine if the issue is specific to your Trados Studio installation or the SDLTB file.

Step 3: Try creating a new SDLTB file from the XLSX glossary again. There might have been an issue during the conversion process.

Step 4: If the issue persists, you might want to consider contacting the RWS Support Team for further assistance.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

"Probability score": 0.7

"Question improvement suggestion": Please provide more details about the error stack trace. Also, it would be helpful if you could share the exact steps you took when creating the new SDLTB from the XLSX file.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Manuel,

I understand that the previous suggestions did not resolve your issue. Given the error message you provided, it seems like the issue might be related to the specific SDLTB file you are trying to load. Here are a few additional steps you can try:

Step 1: Try opening the SDLTB file with a different application, such as MultiTerm, to see if the file itself is not corrupted.

Step 2: If you have access to another computer with Trados Studio installed, try to load the termbase there. This can help determine if the issue is specific to your Trados Studio installation or the SDLTB file.

Step 3: Try creating a new SDLTB file from the XLSX glossary again. There might have been an issue during the conversion process.

Step 4: If the issue persists, you might want to consider contacting the RWS Support Team for further assistance.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

Hello again.

Thank you for your help. I cannot provide more details about the error stack trace because I already gave all the error details there are, xD.

About the exact steps, I just dropped the Excel file on Glossary Converter app and it created a SDLTB file from it. Nothing unusual. I tried opening the SDLTB file on Multiterm and it works perfectly.

I just have one computer, so I cannot try it on another.

Conversion process has been perfectly OK. I checked the log file and there were no issues at all.

Any other ideas?

Kind regards,

Manuel

"Probability score": 0.6

"Question improvement suggestion": Please provide more details about the Glossary Converter app you used, including its version and any settings you may have adjusted during the conversion process.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Manuel,

I understand your frustration and appreciate your patience. Since you've already tried several troubleshooting steps and the SDLTB file opens correctly in MultiTerm, it seems like the issue might be specific to Trados Studio. Here are a few more suggestions:

Step 1: Try resetting your Trados Studio settings to default. You can do this by going to File > Setup > Reset to Default Settings. Please note that this will remove any custom settings, so you may want to take note of them before proceeding.

Step 2: If you have any plugins installed in Trados Studio, try disabling them temporarily to see if they might be causing the issue.

Step 3: Try running Trados Studio as an administrator. To do this, right-click on the Trados Studio icon and select 'Run as administrator'.

Step 4: If the issue persists, you might want to consider contacting the RWS Support Team for further assistance.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

Hello again,

Thank you, but I just reset Trados Studio to the default settings, tried to use the termbase and same error keeps appearing.

I am afraid RWS Community AI won't help to solve the problem.

Any other help would be much appreciated!

Kind regards,

Manuel

¡Hola Manuel Rubio Máñez !

I am far from being an IT specialist and I am definitely not a Cloud user, but could it be that while you believe that your *.sdltb file is now in your "Documents" folder in your C:\ disk, it still is actually, physically in some shared folder in the Cloud, hence the persistent problem? I  heard/read about such situations.

Cordialmente.

Gérard

Salut Gérard LAMBERT !

I understand what you say. I deleted the SDLTB from the shared folder and recreated it through Glossary Converter in a local folder and the problem is still there :(.

Anyways, thank you for your help!

Cordialement,

Manuel