• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 302 subscribers
  • Views 1018 views
  • Users 0 members are here
Options
Related

Trados Studio does not start following installation of World Server components

Michael Taylor

Hello,

I have a problem with Trados Studio 2021 16.0.1.2917 (German version).

I downloaded and installed the World Server components. When I now try to start Trados Studio, I get the following error message and the application won't  open:

"Sdl.Desktop.IntegrationApi.Interfaces.IPluginLoggerFactory" in der Assembly "Sdl.Desktop.IntegrationApi, Version=16.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888" konnte nicht geladen werden.

(approx. English translation: "Sdl.Desktop.IntegrationApi.Interfaces.IPluginLoggerFactory" in the assembly "Sdl.Desktop.IntegrationApi, Version=16.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888" could not be loaded.)

Does anyone have any ideas?

Thank you.

Mike
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Thank you for your reply Paul.

    I had already tried to find a more appropriate version of the WordServer components, but there only sems to be one in the appstore (version 16.10.1894 for Trados Studio 2021).

    I've now attach the full error message as an xml.

    Fullscreen sdlerror-2023317-21h44m30s.sdlerror.xml Download 
    <SDLErrorDetails time="17.03.2023 21:44:45">
  <ErrorMessage>Der Typ "Sdl.Desktop.IntegrationApi.Interfaces.IPluginLoggerFactory" in der Assembly "Sdl.Desktop.IntegrationApi, Version=16.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888" konnte nicht geladen werden.</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[   bei System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
   bei System.Signature..ctor(IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
   bei System.Reflection.RuntimeConstructorInfo.GetParametersNoCopy()
   bei System.Reflection.RuntimeConstructorInfo.GetParameters()
   bei SimpleInjector.Advanced.AdvancedExtensions.Verify(IDependencyInjectionBehavior behavior, ConstructorInfo constructor)
   bei SimpleInjector.ContainerOptions.IsConstructableType(Type implementationType, String& errorMessage)
   bei SimpleInjector.Container.TryBuildInstanceProducerForConcreteUnregisteredType(Type type, InjectionConsumerInfo context)
   bei SimpleInjector.Container.<>c__DisplayClass202_0.<BuildInstanceProducerForType>b__0()
   bei SimpleInjector.Container.BuildInstanceProducerForType(Type serviceType, Func`1 tryBuildInstanceProducerForConcreteType)
   bei SimpleInjector.Container.BuildInstanceProducerForType(Type serviceType, InjectionConsumerInfo context, Boolean autoCreateConcreteTypes)
   bei SimpleInjector.Container.<>c__DisplayClass193_0.<GetRegistrationEvenIfInvalid>b__0()
   bei SimpleInjector.Container.GetInstanceProducerForType(Type serviceType, InjectionConsumerInfo consumer, Func`1 buildInstanceProducer)
   bei SimpleInjector.Container.GetRegistrationEvenIfInvalid(Type serviceType, InjectionConsumerInfo consumer, Boolean autoCreateConcreteTypes)
   bei SimpleInjector.Container.GetRegistration(Type serviceType, Boolean throwOnFailure)
   bei Sdl.Desktop.Platform.Implementation.SimpleInjectorObjectResolver.CanResolve(Type objectType)
   bei Sdl.Desktop.Platform.Implementation.ObjectResolverComposer.<>c__DisplayClass3_0.<CreateObject>b__0(IObjectResolver r)
   bei System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
   bei Sdl.Desktop.Platform.Implementation.ObjectResolverComposer.CreateObject(Type objectType, XElement attributeElement)
   bei Sdl.Core.PluginFramework.Implementation.Extension.CreateInstance()
   bei Sdl.Core.PluginFramework.ObjectRegistry`2.CreateObjects()
   bei Sdl.Desktop.Platform.Implementation.Studio.ExecuteStartupExtensions(ISplashScreen splashScreen)
   bei Sdl.Desktop.Platform.Implementation.Studio.Run(ISplashScreen splashScreen, IEventAggregator eventAggregator)
   bei Sdl.TranslationStudio.Application.Launcher.RunApplication()]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>Studio16</ProductVersion>
    <EntryAssemblyFileVersion>16.0.1.2917</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>HOME\Michael</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>HOME</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8275224 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>
    emoji
  • +1 in reply to Michael Taylor

     

    There could be several reasons why this is causing a problem, such as a missing or incorrect reference to the assembly, a version conflict between the assembly and the application, or a corruption of the assembly. It is also possible that the assembly is not deployed to the correct location or that the required permissions you have in windows are not set up correctly.

    But to resolve this issue, I'm pretty sure it is related to versioning.  You are running an old version of 2021 and you should really update (it won't cost you anything).  But if you don't wish to do this try the archived versions of the plugin -  Archived Versions: Worldserver Compatibility Pack for Trados Studio   Uninstall the plugin you have now through the windows control panel and then download and install the oldest one.

    I can't guarantee this will help and if it doesn't I'm afraid we will not do anything to try and fix it because you should be on the latest version of 2021.

    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
  • 0 in reply to Paul

    I've now downloaded and installed the Cummulative Update for Trados Studio 2021 and the current WorldServer Compatibility Pack from the appstore and it works! 

    Thanks very much for your help Paul.
    emoji
Reply Children
No Data