• State Verified Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 431 subscribers
  • Views 3601 views
  • Users 0 members are here
Options
Related

Trados 2015 SR2 Error adding Term Base to project Retrieving COM class factory failed

Sian Cooper

Hi, I am working on a project provided from a package. I have added my own TM and the Cloud (which keeps losing contact but that's another matter), and have realised about half way through that there are some repeated terms it would be really hand to quick add, so I'm selecting a Term Base I created for another project. I get the error

Retrieving the COM class factory for component with CLSID {12A4009E-2DB3-46E0-9C44-D7740FE9A927} failed due to the following error: 8007007e The specified module could not be found.

Full stack trace attached. Below. I hope. Daft UI.


Any suggestions, please? Thanks!

Fullscreen 3348.sdlerror-201648-23h15m12s.sdlerror.xml Download 
<SDLErrorDetails time="08/04/2016 23:15:19">
  <ErrorMessage>C:\Program Files (x86)\SDL\SDL Trados Studio\Studio4\Studio Menu Maker.exe</ErrorMessage>
  <Exception>
    <Type>System.IO.FileNotFoundException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <FileName />
    <FusionLog />
    <HelpLink />
    <Source>System.Drawing</Source>
    <HResult>-2147024894</HResult>
    <StackTrace><![CDATA[   at System.Drawing.Icon.ExtractAssociatedIcon(String filePath, Int32 index)
   at Sdl.TranslationStudio.Start.Help.StartExplorerBarControl.PopulateOpenExchangeApps()
   at Sdl.TranslationStudio.Start.Help.StartExplorerBarControl..ctor()
   at Sdl.TranslationStudio.Start.Splash.SimpleStartView.<.cctor>b__0()
   at System.Lazy`1.CreateValue()
   at System.Lazy`1.LazyInitValue()
   at System.Lazy`1.get_Value()
   at Sdl.TranslationStudio.Start.Splash.SimpleStartView.GetExplorerBarControl()
   at Sdl.Desktop.Platform.WinForms.StudioWindowForm.UpdateActiveView()
   at Sdl.Desktop.Platform.WinForms.StudioWindowForm.LoadViews()
   at Sdl.Desktop.Platform.Implementation.StudioWindow.Init()
   at Sdl.Desktop.Platform.Implementation.Studio.CreateWindowInternal(Boolean setActive)
   at Sdl.Desktop.Platform.Implementation.Studio.Run()
   at Sdl.TranslationStudio.Application.Launcher.RunApplication()]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>12.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>12.2.5087.4</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>SIAN\Sian</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>SIAN</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>4144356 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Hi Sian,

    Seems a little déjà vu in part ;-)

    First the error attached is coming from menumaker and I'm sure we dealt with this a week or three ago? Is it the right error stack?

    Second this is not the latest version of Studio (if the version in the error stack is correct) and there was a lot of discussion around this error which was resolved with a previous update.

    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

  • 0 in reply to Paul

    Oh damn. Wrong error stack. Sorry. I am definitely on latest version, though. Let's try this one!

    Fullscreen sdlerror-201652-17h30m57s.sdlerror.xml Download 
    <SDLErrorDetails time="5/2/2016 5:31:04 PM">
  <ErrorMessage>Retrieving the COM class factory for component with CLSID {12A4009E-2DB3-46E0-9C44-D7740FE9A927} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E).</ErrorMessage>
  <Exception>
    <Type>System.IO.FileNotFoundException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <FileName />
    <FusionLog />
    <HelpLink />
    <Source>Sdl.MultiTerm.Core.Connectors</Source>
    <HResult>-2147024770</HResult>
    <StackTrace><![CDATA[   at Sdl.MultiTerm.Core.Connectors.LegacyInlineConnector..ctor()
   at Sdl.MultiTerm.Client.TerminologyProvider.TerminologyPrioviders.MultiTermTerminologyProviderFactory.CreateTerminologyProvider(Uri terminologyProviderUri, ITerminologyProviderCredentialStore cs)
   at Sdl.Terminology.TerminologyProvider.Core.TerminologyProviderManager.GetTerminologyProvider(Uri uri)
   at Sdl.TranslationStudio.Common.CommonPaths.GetTerminologyProvider(IWin32Window owner, String path)
   at Sdl.TranslationStudio.Common.CommonPaths.OpenTerminologyFiles(IWin32Window owner, String terminologyFileFilter)
   at Sdl.TranslationStudio.ProjectManagement.Terminology.FileBasedMultiTermProviderWinFromsUI.Browse(IWin32Window owner, ITerminologyProviderCredentialStore credentialStore)
   at Sdl.TranslationStudio.ProjectManagement.Terminology.ProjectTermbasesControl.TerminologyProviderPluginOnClick(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.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>SDL Trados Studio</ProductName>
    <ProductVersion>12.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>12.2.5099.5</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>SIAN\Sian</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>SIAN</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>4144356 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>
  • 0 in reply to Sian Cooper
    Did you also update MultiTerm? Should be 12.2.1629.0

    If you did can you try the resolution in this KB? The error message is the same.

    kb.sdl.com/.../article

    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

  • 0 in reply to Paul
    Oh, interesting. I have updated Multiterm, but I don't run it directly often, when I just opened it it gave me this same error message 3 times before displaying the opening screen (when I was able to check the version no.).

    I'll uninstall/reinstall it and then try the KB article. It's not 100% the same error message (I don't see 'The type initializer for 'Sdl.MultiTerm.Core.Utilities.IOUtilities' threw an exception.', although the COM class error is the same), but it certainly sounds possible - I am deeply suspicious of the new Firefox script-blocking facility I have installed - works very well at blocking scripts in Firefox, but it may be exceeding its limits; also I have had horrible probs. with Win 10, which lost knowledge of a load of default file types, basic registry buggeration, so this sounds eminently possible. I'll let you know. Thanks!