Trados 2017 new install: SDL Plugin Management not open, Error when installing plugins manually

Hi everybody, 

on my new SDL Trados 2017 installation the SDL Plugin Management is not starting. I can't install *.sdlplugin files with a double click and also can't install plugins manually via the folder C:\Users\<user>\AppData\Local\SDL\SDL Trados Studio\14\Plugins\Packages.

 

I get an error message in Trados when trying to use this plugin (message below).

I am administrator of the computer, tried the repair function and reinstalled everything. Also with deleting the existing folder under AppData (because they remain after the deinstallation).

 

 

All hints are welcome.

Thanks, Markus

<SDLErrorDetails time="22.11.2016 16:42:59">
<ErrorMessage>Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.</ErrorMessage>
<Exception>
<Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
<HelpLink />
<Source>Sdl.Community.StudioMigrationUtility</Source>
<HResult>-2147467261</HResult>
<StackTrace><![CDATA[ bei Sdl.Community.StudioMigrationUtility.Services.StudioVersionService.CreateStudioVersion(RegistryKey studioKey, String version, String publicVersion)
bei Sdl.Community.StudioMigrationUtility.Services.StudioVersionService.FindAndCreateStudioVersion(String registryPath, String studioVersion, String studioPublicVersion)
bei Sdl.Community.StudioMigrationUtility.Services.StudioVersionService.Initialize()
bei Sdl.Community.StudioMigrationUtility.Services.StudioVersionService..ctor()
bei Sdl.Community.StudioMigrationUtility.Integration.StudioMigrationUtilityViewPartAction.Execute()
bei Sdl.Desktop.IntegrationApi.AbstractAction.Sdl.Desktop.IntegrationApi.Extensions.Internal.IAction.Execute()
bei Sdl.Desktop.IntegrationApi.Internal.Adaptors.InternalActionAdaptor.Execute()
bei Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass3.<ExecuteAction>b__2()
bei Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
bei Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
bei Sdl.Desktop.Platform.WinForms.IgCommandBarAction.Execute()
bei Sdl.Desktop.Platform.WinForms.IgCommandBarAction._lazyButtonTool_ToolClick(Object sender, ToolClickEventArgs e)
bei Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick(ToolClickEventArgs e)
bei Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnToolClick(ToolClickEventArgs e)
bei Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.FireEvent(ToolbarEventIds id, EventArgs e)
bei Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick()
bei Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.DoClickProcessing(MouseEventArgs e)
bei Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.OnMouseUp(MouseEventArgs e)
bei Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)
bei Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)
bei Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e)
bei Infragistics.Win.UltraWinToolbars.UltraToolbarsDockArea.OnMouseUp(MouseEventArgs e)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
</Exception>
<Environment>
<ProductName>SDL Trados Studio</ProductName>
<ProductVersion>14.0.0.0</ProductVersion>
<EntryAssemblyFileVersion>14.0.5746.0</EntryAssemblyFileVersion>
<OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
<ServicePack>NULL</ServicePack>
<OperatingSystemLanguage>1031</OperatingSystemLanguage>
<CodePage>1252</CodePage>
<LoggedOnUser>xxxxx</LoggedOnUser>
<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
<ComputerName>xxxxx</ComputerName>
<ConnectedToNetwork>True</ConnectedToNetwork>
<PhysicalMemory>33427764 MB</PhysicalMemory>
</Environment>
</SDLErrorDetails>

Parents
  • Hi Markus,

    The error message suggest you have actually installed this twice, maybe different versions and definitely in two different places.  please can you do the following:

    1. Download the latest version from the appstore
    2. Delete these files/folders if they exist:
      c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\14\Plugins\Packages\Studio Migration Utility.sdlplugin
      c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\14\Plugins\Unpacked\Studio Migration Utility
      c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\14\Plugins\Packages\Studio Migration Utility.sdlplugin
      c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\14\Plugins\Unpacked\Studio Migration Utility
    3. Double click the version you downloaded and try again.  If there is no response then manually copy the plugin into this location:
      c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\14\Plugins\Packages\

    Then restart Studio and hopefully this will help.

    Regards

    Paul

    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

  • Hi Markus,

    Many apologies but I have deleted your reply and we can't recover it!!  I did read it first though so perhaps I can just confirm that you removed the locations I mentioned above and then Studio started again.  But when you attempted to install the plugin it failed with the error stack below.  Also you advised that the plugin is working fine on a different computer.

    <SDLErrorDetails time="23.11.2016 11:32:16">
    <ErrorMessage>Ein Aufrufziel hat einen Ausnahmefehler verursacht.</ErrorMessage>
    <Exception>
    <Type>System.Reflection.TargetInvocationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>mscorlib</Source>
    <HResult>-2146232828</HResult>
    <StackTrace><![CDATA[ bei System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
    bei System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
    bei System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
    bei System.Activator.CreateInstance(Type type, Boolean nonPublic)
    bei System.Activator.CreateInstance(Type type)
    bei System.Lazy`1.CreateValue()
    bei System.Lazy`1.LazyInitValue()
    bei System.Lazy`1.get_Value()
    bei Sdl.Community.ReindexTms.ReindexTmsRibbon.GetContentControl()
    bei Sdl.Desktop.IntegrationApi.AbstractViewController.Sdl.Desktop.IntegrationApi.Internal.IViewController.GetContentControl()
    bei Sdl.Desktop.IntegrationApi.Internal.Adaptors.InternalViewAdapter.GetContentControl()
    bei Sdl.Desktop.Platform.WinForms.ViewPane.set_ViewReference(IViewReference value)
    bei Sdl.Desktop.Platform.WinForms.StudioWindowForm.UpdateActiveView()
    bei Sdl.Desktop.Platform.WinForms.StudioWindowForm.LoadViews()
    bei Sdl.Desktop.Platform.Implementation.StudioWindow.Init()
    bei Sdl.Desktop.Platform.Implementation.Studio.CreateWindowInternal(Boolean setActive)
    bei Sdl.Desktop.Platform.Implementation.Studio.Run()
    bei Sdl.TranslationStudio.Application.Launcher.RunApplication()]]></StackTrace>
    <InnerException>
    <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.Community.Toolkit.Core</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[ bei Sdl.Community.Toolkit.Core.Services.StudioVersionService.CreateStudioVersion(RegistryKey studioKey, String version, String publicVersion)
    bei Sdl.Community.Toolkit.Core.Services.StudioVersionService.Initialize()
    bei Sdl.Community.Toolkit.Core.Services.StudioVersionService..ctor()
    bei Sdl.Community.ReindexTms.TranslationMemory.TranslationMemoryHelper..ctor()
    bei Sdl.Community.ReindexTms.ReindexForm..ctor()]]></StackTrace>
    </InnerException>
    </Exception>
    <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>14.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>14.0.5746.0</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>xxx</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>xxx</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>33427764 MB</PhysicalMemory>
    </Environment>
    </SDLErrorDetails>

    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

  • Can you confirm that you are not trying to run the plugin manager version that is on the app store instead of the one that is preinstalled with Studio 2017?

    I think the best way to resolve this will be with a skype session so we can take a look at what you are doing and what's on your machine. can we do this on Monday perhaps?

    In the meantime have you tried manually copying the sdlplugin files to this location?

    c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\14\Plugins\Packages\

    Then start Studio and see if they have installed correctly.

    Regards

    Paul

    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

  • Thank you for the quick reply, Paul. Yes, I am trying to access the preinstalled version and have tried manually dropping the plugin files in the folder you indicated. Monday would work for me, preferably in the morning (PST). Thank you!
  • Morning would work for me too seeing as you are 9-hrs behind me ;-) Drop me an email at pfilkin@sdl.com and we can arrange a time and share skype details.

    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

  • Dear Paul,

    Yes I copied the sdlplugin files to the indicated location. However, even with the latest update version of Studio the Reindex TMs plugin doesn't work, and accessing its pane gives the same error message.

    Neither the plugin manager that is preinstalled with Studio nor the app store version start.

    Regards

    Kai
  • Dear Kai,

    Have you tried the registry fix on the first page of this thread? Only remove the references to Studio versions that you no longer have installed.

    Regards

    Paul

    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

  • To everyone,

    Looking at the errors, this appears to be due to leftover registry keys from previous installations.

    Go to
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SDL\

    Studio4 folder corresponds to Trados Studio 2015 and anything below that is older installations of Trados. If you no longer have those versions installed, delete the leftover registry entries (Studio2, Studio3, etc)
  • Tada... This was the trick. Now the plugin manager works again and the Reindex pane is accessible.

    Thank you, Paul!

    Regards

    Kai
  • Tada... This was the trick. Now the plugin manager works again and the Reindex pane is accessible.

    Thank you, Jesse!

    Regards

    Kai
  • Jesse,

    I just wanted to say thanks! My Plugin Manager stopped working at some point and this fixed it (deleting all entries for Studio 2015 in my case).
  • Hi ,

    Just on the back of this, can you try cleaning up and installing SDL Analyse again as this might also be related to the problem you had with that.

    Thanks

    Paul

    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

Reply Children