• State Verified Answer
  • Replies 12 replies
  • Answers 6 answers
  • Subscribers 433 subscribers
  • Views 4087 views
  • Users 0 members are here
Options

"Translate in SDL Trados Studio" context menu missing and SDL file extension rules gone

Olav

Hello,

 

I had left SDL Trados Studio 2017 after installing SDL Trados Studio 2019. After I uninstalled SDL Trados Studio 2017, a context menu "Translate in SDL Trados Studio" is missing and default file extensions of SDL (for example .xliff, .sdltm etc.) are not connected with SDL anymore. Althought I have SDL Trados Studio 2019 installed. Why the uninstall of SDL Trados Studio 2017 left removed context menu "Translate in SDL Trados Studio" and default file extensions of SDL when I had SDL Trados Studio 2019 also installed and I have not uninstalled 2019?

I connected .xliff with .exe of SDL Trados Studio 2019 but this opens a new instance of SDL Trados Studio 2019, not a new project dialogue or something similar.

 

How to restore the normal situation that all necessary SDL context menu options and file extensions are connected with SDL Trados Studio 2019 in a way that no new instance of SDL Trados Studio 2019 is opened when .xliff is clicked and SDL Trados Studio 2019 is already running?
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Hi 
     
    Please try running a Windows Repair of Studio, via Control Panel...
     
    Close all SDL applications.
     
    Open the Control Panel via Windows button>Windows System>Control Panel:
    Windows Vista/7: Start > Control Panel > Programs > Programs and Features.
    Windows 8: Right-click on the screen at bottom-left corner and choose Control Panel > Uninstall a Program.
    Windows 10: Right-click on Start (Windows button) >Windows System > Control Panel > Select View by: Small Icons > Programs and Features.
     
    Click/highlight the relevant SDL product in the list (e.g. SDL Trados Studio 2019 SR1) and click Repair on the top toolbar (or in right-click context menu).
     
    Restart Studio.
     
    Repeat the above for the MultiTerm components.
    I actually repair all components of MultiTerm then I repair Studio,  periodically. It's worth the time it takes, especially after a big update/upgrade and Windows automatic updates.
    The same goes for other complex software, Microsoft Office for example.
     
    All the best,
    Alison
  • 0 in reply to Alison Field
    Hi Alison

    Does the Windows Repair of Studio deletes user configured settings? Should I back up some data/folder before I do this?

    Best Regards,
    Olav
  • 0 in reply to Olav
    Hi Olav,

    You can first save your user profile settings in Studio via File > Setup > Manage User profiles > Export... (there is always the slight chance that they are causing the problem but then you can do it all again without importing your profile settings). When you've finished the repair process, you can use the same path to import your profile settings.

    You may still have to enter your initial 5 languages, if you have a Freelance license.

    All the best,
    Alison
  • 0 in reply to Alison Field

    Hi Alison,

    after the Windows Repair of Studio, I got error: "<SDLErrorDetails time="19.12.2018 21:47:49">
    <ErrorMessage>Cannot validate SDL plug-in: Sdl.Common.Licensing.Provider.SafeNetRMS.SafeNetRMSLicensingProviderFactory, Sdl.Common.Licensing.Provider.SafeNetRMS, Version=15.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888 : C:\Program Files (x86)\SDL\SDL Trados Studio\Studio15\Sdl.Common.Licensing.Provider.SafeNetRMS.dll</ErrorMessage>
    <Exception>
    <Type>Sdl.Core.PluginFramework.PluginFrameworkException, Sdl.Core.PluginFramework, Version=1.8.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</Type>
    <HelpLink />
    <Source>Sdl.Core.PluginFramework</Source>
    <HResult>-2146233088</HResult>
    <StackTrace><![CDATA[ at Sdl.Core.PluginFramework.DefaultPluginTypeLoader.LoadType(IPlugin plugin, String typeName)
    at Sdl.Core.PluginFramework.Implementation.Extension.get_ExtensionType()
    at Sdl.Core.PluginFramework.Implementation.Extension.CreateInstance()
    at Sdl.Core.PluginFramework.ObjectRegistry`2.CreateObjects()
    at Sdl.Common.Licensing.Provider.Core.LicensingProviderManager.get_LicensingProviderFactories()
    at Sdl.Common.Licensing.Provider.Core.LicensingProviderManager.CreateProvider(ILicensingProviderConfiguration config, String preferredProviderId)
    at Sdl.Common.Licensing.Manager.ApplicationLicenseManager.GetCurrentLicensingProvider()
    at Sdl.Common.Licensing.Manager.ApplicationLicenseManager.ShowLicensingDialog(LicensingFormConfiguration formConfiguration, IList`1 customPages)
    at Sdl.TranslationStudio.Common.Licencing.LicensingService.ShowLicenseDialog(Boolean startupCheck)
    at Sdl.TranslationStudio.Common.Licencing.LicensingService.StartupLicenseCheck()
    at Sdl.Desktop.Platform.Implementation.Studio.Run()
    at Sdl.TranslationStudio.Application.ApplicationStartup.RunApplication()
    at Sdl.TranslationStudio.Application.Launcher.RunApplication()]]></StackTrace>
    </Exception>
    <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>15.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>15.0.0.29074</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1257</CodePage>
    <LoggedOnUser>[username]</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>[computer name]</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16202716 MB</PhysicalMemory>
    </Environment>
    </SDLErrorDetails>".

    Fullscreen 0083.sdlerror-20181219-21h47m42s.sdlerror.xml Download
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    <SDLErrorDetails time="19.12.2018 21:47:49">
    <ErrorMessage>Cannot validate SDL plug-in: Sdl.Common.Licensing.Provider.SafeNetRMS.SafeNetRMSLicensingProviderFactory, Sdl.Common.Licensing.Provider.SafeNetRMS, Version=15.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888 : C:\Program Files (x86)\SDL\SDL Trados Studio\Studio15\Sdl.Common.Licensing.Provider.SafeNetRMS.dll</ErrorMessage>
    <Exception>
    <Type>Sdl.Core.PluginFramework.PluginFrameworkException, Sdl.Core.PluginFramework, Version=1.8.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</Type>
    <HelpLink />
    <Source>Sdl.Core.PluginFramework</Source>
    <HResult>-2146233088</HResult>
    <StackTrace><![CDATA[ at Sdl.Core.PluginFramework.DefaultPluginTypeLoader.LoadType(IPlugin plugin, String typeName)
    at Sdl.Core.PluginFramework.Implementation.Extension.get_ExtensionType()
    at Sdl.Core.PluginFramework.Implementation.Extension.CreateInstance()
    at Sdl.Core.PluginFramework.ObjectRegistry`2.CreateObjects()
    at Sdl.Common.Licensing.Provider.Core.LicensingProviderManager.get_LicensingProviderFactories()
    at Sdl.Common.Licensing.Provider.Core.LicensingProviderManager.CreateProvider(ILicensingProviderConfiguration config, String preferredProviderId)
    at Sdl.Common.Licensing.Manager.ApplicationLicenseManager.GetCurrentLicensingProvider()
    at Sdl.Common.Licensing.Manager.ApplicationLicenseManager.ShowLicensingDialog(LicensingFormConfiguration formConfiguration, IList`1 customPages)
    at Sdl.TranslationStudio.Common.Licencing.LicensingService.ShowLicenseDialog(Boolean startupCheck)
    at Sdl.TranslationStudio.Common.Licencing.LicensingService.StartupLicenseCheck()
    at Sdl.Desktop.Platform.Implementation.Studio.Run()
    at Sdl.TranslationStudio.Application.ApplicationStartup.RunApplication()
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    SDL Trados is not starting anymore after clicking "OK" in the error dialogue.
  • 0 in reply to Olav

    Hello  

    The posted 'error stack' relates to an error regarding the licensing server and Studio 2019 and not Studio 2017 and therefore needs to be looked at by our licensing/support team.

    As I cannot verify your license version, if you do not own the license personally, please ask the account admin where the license is registered, to log a ticket on your behalf.

    Screenshot of SDL Account support page with options to submit a new Translation Productivity case, request installation help, or request a license reset.

     

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


    Generated Image Alt-Text
    [edited by: Trados AI at 2:57 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Lydia Simplicio
    Looks like the chaotic product versioning gives a hard time even to SDL staff...
    Studio 15.x.x.x is Studio 2019, not Studio 2015... (Studio 2015 would be numbered 12.x.x.x)
  • 0 in reply to Evzen Polenka
    Thanks ,

    Well spotted :-) Original reply now correctly edited

    Indeed, the error stack is referring to 2019- This was actually a typo and not a confusion over versioning.

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

  • 0 in reply to Lydia Simplicio

    Installation of SDL Trados Sudio 2019 SP1 fixed the error.
  • 0 in reply to Alison Field

    Hi Alison,

    I have installed SDL Trados Studio 2019 SP1 but this fixed the icons for some of SDL file extensions which I had not configured by myself. Should I do the Windows Repair of Studio to 2019 SP1 too to try to fix those icons?
    I believe that the cause of this issue is manually setting the default software for SDL file extensions. I should had do the windows repair first, not setting SDL Trados Studio .exe file as a default opening software.
    For example, the icon for .sdlxliff is like this: Two file icons side by side, the first icon is incorrectly displaying the SDL Trados Studio .exe icon instead of the default .sdlxliff icon, the second icon is the correct default icon for .sdlxliff files.. But this is the icon for .exe of SDL Trados. I remember that the default icon for .sdlxliff looks differently.

     

    Best Regards,

    Olav
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 2:57 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Olav

    Hi 

    Yes, a Windows Repair of Studio 2019 SR1 normally should solve the icons issue and should reset the file extension associations.

    The only icons you need to change manually are any pinned Studio shortcut on your Start screen or your toolbar as these often appear as blank after an upgrade or reinstallation of Studio. Unpinning them then repinning sorts this issue out.

    I hope this helps.

    All the best,

    Alison
1 2