Alasdair MacCaluim 

Hi again Paul.

OK - this is getting weird! I followed your advice and it worked - many thanks!

BUT - then I noticed that there is said in the project settings view that the TM needed upgraded and may need reindexed or something like that. I thought it would be worthwhile doing that - but it didn't work. (Even before I had the current problem with pre-translation, when I was using Trados 2017, often matches didn't show up when I did pre-translation so I thought this might solve this problem).

As this didn't work, I tried repairing it with the Plugin you recommended. I downloaded it and thought it was installed but it didn't appear in the add-ons section of Trados.

Assuming that it the plugin would appear if I restarted the computer, I closed and restarted the computer.

When it reopened it, Trados wouldn't open! It starts loading and goes as far as the creating application window screen and then closes. AArgh! Do you have any advice? Ta!

Alasdair

Alasdair MacCaluim 

I tested the app first to make sure it works... and it seems to for me anyway:

Thanks Paul! MY HERO! 

I removed the SDLTM repair file as advised and Trados will now load up again. 

I've also managed to get SDLTM repair installed. 

However, when I put the TM in to the SDLTM repair, I get this error message: 


 

Alasdair

Thanks Paul! MY HERO! 

I removed the SDLTM repair file as advised and Trados will now load up again. 

I've also managed to get SDLTM repair installed. 

However, when I put the TM in to the SDLTM repair, I get this error message: 


 

Alasdair

Alasdair MacCaluim 

ok - I don't know what that is... I also tested a couple of TMs, including one large corrupted one, and they all work ok for me.  So, we need to look a bit deeper and the best place to start is with the proper error message that is behind that headline:

Can you force the error again by trying to do what you did before, and then click on the small disk symbol.  This will allow you to save the error stack, as an XML file, somewhere on your computer.  So save it to your desktop top, and then attach it to your reply to this post by using the Insert -> image/video/file menu directly underneath where you are typing your reply.

Thanks so much! I did the same thing again and got the same error message. 

<SDLErrorDetails time="03/03/2025 15:51:52">
  <ErrorMessage>Could not find file 'C:\log_26b5da6b-009d-4cad-b662-4c7dbbf6730c.txt'.</ErrorMessage>
  <Exception>
    <Type>System.IO.FileNotFoundException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <FileName>C:\log_26b5da6b-009d-4cad-b662-4c7dbbf6730c.txt</FileName>
    <FusionLog />
    <HelpLink />
    <Source>mscorlib</Source>
    <HResult>-2147024894</HResult>
    <StackTrace><![CDATA[   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at 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)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
   at System.IO.StreamReader..ctor(String path)
   at Sdl.Community.TMRepair.SDLTMRepair.btnRepair_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.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 11 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>2057</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>LAPTOPALASDAIR\Gaeli</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>LAPTOPALASDAIR</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16551224 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Alasdair MacCaluim 

Thanks for sharing the full message.  It looks as though your SDLTM might also be in a folder on the OneDrive path.  The SDLTMRepair plugin likely expects a standard local file, and if you save it in a folder that is on the OneDrive path, and don't set up OneDrive to make sure that the file is always available, then the plugin won't be able to find it.  This is because Windows will present a placeholder instead of the file while it's trying to download the file to make it available.

Some Windows subsystems (e.g., WinIOError, System.IO.FileStream) may use the root of c:\ as a fallback location to store error logs or diagnostic output.  So if the plugin doesn’t explicitly set a logging path (and I don't believe it does as it expects the file to be there), Windows may try to create temporary logs in c:\.  That could also be problematic depending on your read/write permissions.

So if this is the case your solution is to either don't use OneDrive for your TMs and generally I would recommend that because these can be quite large resources; or make sure that the folders containing these files are always available offline as well as in the OneDrive cloud.

Same sort of thing would apply if you use any other cloud solution for your files like dropbox or google drive.  The files must always be available offline and not just on demand (which I think is the OneDrive default to help save you hard drive space... and cause you problems ;-))

Thanks Paul! That's great advice. I'll move it from OneDrive.

Thanks very much! That worked! I'm incredibly grateful for you help on this