• State Verified Answer
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 305 subscribers
  • Views 115 views
  • Users 0 members are here
Options
Related

SDL Trados Studio 2021 won't open today

Vianney Bossé

When I tried to open SDL Trados Studio 2021 today, after the loading screen, I got an error message and Trados won't open. Yesterday, I tried to install a WorldServer plugin for a new client. It probably has something to do with it since "plugin" appears in the error message, but I don't know how to solve the issue.

The error message is in French, but I found a post on this forum with a similar error message in English (just the "type" and "assembly" were different), so here it is:

"Sdl.TranslationStudio.api.ProjectManagement.IProjectManagementService" could not be started.

Could not load type 'Sdl.Desktop.IntegrationApi.Interfaces.IPluginLoggerFactory' from assembly 'Sdl.Desktop.IntegrationApi, Version=16.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888'."

The error file is below.

Thank you for your help. I have a small project for today, I will contact the PM and ask for someone else to take it.

Fullscreen 5127.sdlerror-2025822-9h54m24s.sdlerror.sdlerror.xml Download 
<SDLErrorDetails time="22/08/2025 09:54:32">
  <ErrorMessage>Impossible de charger le type 'Sdl.Desktop.IntegrationApi.Interfaces.IPluginLoggerFactory' à partir de l'assembly 'Sdl.Desktop.IntegrationApi, Version=16.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888'.</ErrorMessage>
  <Exception>
    <Type>System.TypeLoadException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <TypeName>Sdl.Desktop.IntegrationApi.Interfaces.IPluginLoggerFactory</TypeName>
    <HelpLink />
    <Source>mscorlib</Source>
    <HResult>-2146233054</HResult>
    <StackTrace><![CDATA[   à System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
   à System.Signature..ctor(IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
   à System.Reflection.RuntimeConstructorInfo.GetParametersNoCopy()
   à System.Reflection.RuntimeConstructorInfo.GetParameters()
   à SimpleInjector.Advanced.AdvancedExtensions.Verify(IDependencyInjectionBehavior behavior, ConstructorInfo constructor)
   à SimpleInjector.ContainerOptions.IsConstructableType(Type implementationType, String& errorMessage)
   à SimpleInjector.Container.TryBuildInstanceProducerForConcreteUnregisteredType(Type type, InjectionConsumerInfo context)
   à SimpleInjector.Container.<>c__DisplayClass202_0.<BuildInstanceProducerForType>b__0()
   à SimpleInjector.Container.BuildInstanceProducerForType(Type serviceType, Func`1 tryBuildInstanceProducerForConcreteType)
   à SimpleInjector.Container.BuildInstanceProducerForType(Type serviceType, InjectionConsumerInfo context, Boolean autoCreateConcreteTypes)
   à SimpleInjector.Container.<>c__DisplayClass193_0.<GetRegistrationEvenIfInvalid>b__0()
   à SimpleInjector.Container.GetInstanceProducerForType(Type serviceType, InjectionConsumerInfo consumer, Func`1 buildInstanceProducer)
   à SimpleInjector.Container.GetRegistrationEvenIfInvalid(Type serviceType, InjectionConsumerInfo consumer, Boolean autoCreateConcreteTypes)
   à SimpleInjector.Container.GetRegistration(Type serviceType, Boolean throwOnFailure)
   à Sdl.Desktop.Platform.Implementation.SimpleInjectorObjectResolver.CanResolve(Type objectType)
   à Sdl.Desktop.Platform.Implementation.ObjectResolverComposer.<>c__DisplayClass3_0.<CreateObject>b__0(IObjectResolver r)
   à System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
   à Sdl.Desktop.Platform.Implementation.ObjectResolverComposer.CreateObject(Type objectType, XElement attributeElement)
   à Sdl.Core.PluginFramework.Implementation.Extension.CreateInstance()
   à Sdl.Core.PluginFramework.ObjectRegistry`2.CreateObjects()
   à Sdl.Desktop.Platform.Implementation.Studio.ExecuteStartupExtensions(ISplashScreen splashScreen)
   à Sdl.Desktop.Platform.Implementation.Studio.Run(ISplashScreen splashScreen, IEventAggregator eventAggregator)
   à Sdl.TranslationStudio.Application.Launcher.RunApplication()]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>Studio16</ProductVersion>
    <EntryAssemblyFileVersion>16.0.2.3343</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Famille</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1036</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>Utilisateur\Utilisateur-</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>UTILISATEUR</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8272300 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Probability score: 0.8  

    Question improvement suggestion: Provide the exact error message in English and specify if you have already tried any troubleshooting steps.  

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

    Hello,  

    It seems you're encountering an issue with starting Trados Studio 2021 due to an error related to a plugin. Here are some steps you can follow to troubleshoot and potentially resolve this issue:

    **Step 1:** Close Trados Studio completely.  

    **Step 2:** Navigate to the following directory:  

    `C:\Users\%username%\App Data\Roaming\SDL\SDL Trados Studio\16\Plugins`  

    If you can't find the path, ensure that hidden items are visible in Windows File Explorer by clicking on the "View" tab and checking the "Hidden items" checkbox.  

    **Step 3:** Rename the `Plugins` folder to `Plugins_old`. This will disable any third-party plugins that might be causing the issue.  

    **Step 4:** Optionally, you can run a repair installation of Trados Studio. To do this, go to Control Panel > Programs and Features, find Trados Studio, right-click on it, and select "Repair".  

    **Step 5:** Restart your computer and then try to open Trados Studio again.  

    If the issue persists, you may want to check for any antivirus software that could be interfering with the application. Adding the Trados Studio installation folder as an exception in your antivirus settings can sometimes resolve such issues.  

    If none of these steps work, please consider checking for any recent Windows updates or reinstalling Trados Studio as a last resort.  

    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
    emoji
  • 0 in reply to RWS Community AI

    I tried several of these options (renaming the file "Plugins" to "Plugins_old"; restarting the computer) and nothing worked.

    I couldn't find the "Programs and Features" option in the Control Panel (I use Windows 10), so I couldn't try to repair Trados.

    Adding Trados to the exceptions of my antivirus doesn't seem to do anything either.

    I am not 100% sure that it has to do with plugins, I just saw "plugin" in the error message.

    If someone can help me interpret the error report so that I can fix the issue without reinstalling Trados, it would be perfect.
    emoji
  • 0 in reply to Vianney Bossé

    Hi Vianney,

    I'll share the articles from the KB for repairing Trados and for a reset of Trados to the default state.

    I suggest you do the second one, the reset to default:

    https://gateway.rws.com/csm?id=kb_article_view&sys_kb_id=792c79773b81e6d093afd79704e45af0&spa=1

    And this is for a repair:

    https://gateway.rws.com/csm?sys_kb_id=b24f61e983466690396947426daad39d&id=kb_article_view

    I am sorry, I am not that savvy to interpret the error report, but perhaps the reset to default solves your issue.

    Please let me know how it goes.

    Kind regards,
    Anca

    Anca Stoian | RWS Group

    emoji
  • 0 in reply to Anca Stoian

    Hi Anca,

    Thanks for your answer.

    I just found those two articles, but it didn't work. Renaming all the relevant folders created new ones as explained, but I still got the error message. Using the "Repair" option didn't help either, even though the repair process completed successfully.

    I'm considering reinstalling SDL Trados Studio 2021 as the last option I can think of.

    Do you know if the WorldServer compatibility plugin is known for causing this sort of things? My last Windows update was on 15/08/2021, so that can't be it (I could use Trados the past two days). My antivirus software doesn't seem to be the culprit either, since setting Trados as an exception doesn't change anything.
    emoji
Reply
  • 0 in reply to Anca Stoian

    Hi Anca,

    Thanks for your answer.

    I just found those two articles, but it didn't work. Renaming all the relevant folders created new ones as explained, but I still got the error message. Using the "Repair" option didn't help either, even though the repair process completed successfully.

    I'm considering reinstalling SDL Trados Studio 2021 as the last option I can think of.

    Do you know if the WorldServer compatibility plugin is known for causing this sort of things? My last Windows update was on 15/08/2021, so that can't be it (I could use Trados the past two days). My antivirus software doesn't seem to be the culprit either, since setting Trados as an exception doesn't change anything.
    emoji
Children
No Data