• State Suggested Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 8206 views
  • Users 0 members are here
Options
Related

"Attempted to read or write protected memory. This is often an indication that other memory is corrupt".

Bruno Depascale

Hi everybody, when I try to add a term from within Studio 2017 SR1 to multiform termbase, I got the following error message: 

"Attempted to read or write protected memory. This is often an indication that other memory is corrupt".

I have tried reorganizing the termbase, removing and reinstalling trados and multiterm 2017 and I have checked that both applications are up-to-date. Also, I don't have any antivirus installed.

Thank you for your help,

Bruno

Fullscreen 8171.errorstack.xml Download 
<SDLErrorDetails time="14/10/2017 12:10:52">
  <ErrorMessage>Attempted to read or write protected memory. This is often an indication that other memory is corrupt.</ErrorMessage>
  <Exception>
    <Type>System.AccessViolationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.MultiTerm.TMO.Interop</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   at Sdl.MultiTerm.TMO.Interop.TermbaseDefinitionClass.get__Schema()
   at Sdl.MultiTerm.Client.UI.Viewer.ScriptingHost.GetSchema()
   at Sdl.MultiTerm.Client.UI.Viewer.ScriptingHost.set_Termbase(TermbaseStatus value)
   at Sdl.MultiTerm.Client.UI.Viewer.TermViewer.StartEdit()
   at Sdl.MultiTerm.Client.UI.Viewer.TermViewer.EditNew(String source, String target)
   at Sdl.MultiTerm.Client.UI.Viewer.TermViewer.EditNewIncomplete(String source, String target)
   at Sdl.MultiTerm.Client.UI.Viewer.DefaultTermViewer.EditNewIncomplete(String source, String target)
   at Sdl.MultiTerm.Client.MiniEditor.MiniEditorControl.AddTerm(TermbaseStatus activeTermbase, String source, String target)
   at Sdl.MultiTerm.Client.MiniEditor.MiniEditor.AddTerm(TermbaseStatus activeTermbase, String source, String target)
   at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.MultiTermViewerWinFormsUI.AddTerm(ITermbaseInfo termbaseInfo, String source, String target)
   at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.MultiTermViewerWinFormsUI.AddTerm(String source, String target)
   at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.TermBaseViewPartX.TerminologyProviderViewerAddTerm(String source, String target)
   at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.TermBaseViewPartX.AddTerm(ITerminologyProvider termbase, String source, String target)
   at Sdl.TranslationStudio.Editor.Terminology.EditorTermbaseUtils.AddTerm(IEditorService editorService, ITranslatableDocument translatableDocument, String sourceText, String targetText)
   at Sdl.TranslationStudio.Editor.Terminology.Actions.AbstractAddNewTermAction.AddTerm()
   at Sdl.TranslationStudio.Editor.Terminology.Actions.AddNewTerm.Execute()
   at Sdl.Desktop.Platform.Implementation.CommandBars.StaticAction.Execute()
   at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass3.<ExecuteAction>b__2()
   at Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
   at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
   at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteActionForShortcut(Keys shortcut)
   at Sdl.Desktop.Platform.WinForms.StudioWindowForm.OnKeyDown(KeyEventArgs e)
   at System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
   at System.Windows.Forms.Form.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   at System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
   at System.Windows.Forms.Control.WmKeyChar(Message& m)
   at System.Windows.Forms.Control.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>14.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>14.1.6329.7</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1040</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>DESKTOP-Q95VB79\Bruno</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>DESKTOP-Q95VB79</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>3526180 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Hello ,

    As mentioned in the other post perhaps you can try a reinistall? It might even make sense to do this with a cleaner install. Try the following.

    1. Uninstall Studio
    2. Uninstall MultiTerm

    Now manually delete these folders if they are still there (back up your TMs, Termbases, AutoSuggest Dictionaries and Projects first in case you make a mistake):

    c:\ProgramData\Package Cache\SDL\SDLTradosStudio2017\
    c:\ProgramData\Package Cache\SDL\SDLMultiTermDesktop2017\
    c:\Program Files (x86)\SDL\SDL Trados Studio\Studio5\
    c:\Program Files (x86)\SDL\SDL MultiTerm\MultiTerm14\
    c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\14\
    c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\14.0.0.0\
    c:\Users\[USERNAME]\AppData\Local\SDL\SDL MultiTerm\MultiTerm14\
    c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\14\
    c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\14.0.0.0\
    c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL MultiTerm\MultiTerm14\
    c:\Users\[USERNAME]\Documents\Studio 2017\Project Templates\
    c:\Users\[USERNAME]\Documents\Studio 2017\Projects\projects.xml

    I think that's about it for a clean install. Then reinstall.

    If you still have problems after this I'd recommend you log a ticket with support so an engineer can look at this for you. This is clearly an installation problems and for licensing or installation issues that prevent you from working we have a route for all customers to get help. This can be achieved really quickly using this link:

    http://support.xl8.one

    Just fill in the form and submit it. Make sure your email address is entered correctly or nobody will be able to get back in touch with you.

    Regards

    Paul

    Paul Filkin | RWS

    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
    Hi Paul,
    I am experiencing the same symptoms, although I am receiving this error even just attempting to view the term within Trados Studio.
    All looks OK within MultiTerm.
    I have performed a "Clean Install", as per your instructions, but it has not resolved the issue.
    I will raise a support ticket as suggested.
  • 0 in reply to Paul
    Dear Paul,
    I did as you suggested. However, the problem is still there.
    Thank you
  • 0 in reply to Bruno Depascale

    Hi . .

    I was able to resolve this issue (with the aid of Bodgan@SDLSupport) by:

    1. Closing both Trados Studio and MultiTerm
    2. Renaming (rather than deleting) the folders Paul mentions above (with the suffix "_old")
    3. Performing a Repair of Trados Studio

    By renaming the folders and repairing, you should be prompted to set up "as a new user", when opening Trados Studio.

    Since following these steps, my similar issue has resolved.

    Hope this is useful to you.

    Kind regards

    Samuel
  • 0 in reply to Paul

    Dear Paul,
    I submitted a support ticket and Bogdan solved this issue, renaming the main folder for Studio and also renamed and did a reset to the settings, plugins and base settings for Studio( which were hidden by default ).
    However, I have now another problem :), namely the fact that Studio keeps crashing and that I got this error message: "Could not load file or assembly 'Sdl.TranslationStudio.Plugins.WorldServerTranslationProvider.Api"
    please see below the error details. By the way, I have to deliver a job now and I don't know what to do :)

    I tried to submit a new support case, but I get the error "Error: Error occurred while loading a Visualforce page.
    Please email us if you need to get in touch"
    Thank you!!!!!!!!!


    <SDLErrorDetails time="19/10/2017 19:34:48">
    <ErrorMessage>Could not load file or assembly 'Sdl.TranslationStudio.Plugins.WorldServerTranslationProvider.Api, Version=14.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888' or one of its dependencies. Impossibile trovare il file specificato.</ErrorMessage>
    <Exception>
    <Type>System.IO.FileNotFoundException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <FileName>Sdl.TranslationStudio.Plugins.WorldServerTranslationProvider.Api, Version=14.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</FileName>
    <FusionLog>WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    </FusionLog>
    <HelpLink />
    <Source>Sdl.TranslationStudio.Packaging</Source>
    <HResult>-2147024894</HResult>
    <StackTrace><![CDATA[ at Sdl.TranslationStudio.Packaging.ReturnPackageCreation.ProcessingWizardPage.Start(IJobService jobService)
    at Sdl.Desktop.Platform.Wizard.AbstractJobWizardPage`1.OnShow(Boolean first, Boolean back)
    at Sdl.TranslationStudio.Packaging.ReturnPackageCreation.ProcessingWizardPage.OnShow(Boolean first, Boolean back)
    at Sdl.Desktop.Platform.Wizard.AbstractWizard`1.SetPageIndex(Int32 index)
    at Sdl.Desktop.Platform.Wizard.AbstractWizard`1.Finish()
    at Sdl.Desktop.Platform.Wizard.AbstractWizard`1._form_Finish(Object sender, CancelEventArgs e)
    at Sdl.Desktop.Platform.WinForms.WizardForm._finishButton_Click(Object sender, EventArgs e)
    at System.Windows.Forms.Control.OnClick(EventArgs e)
    at System.Windows.Forms.Button.OnClick(EventArgs e)
    at System.Windows.Forms.Button.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>14.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>14.1.6329.7</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1040</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>DESKTOP-Q95VB79\Bruno</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>DESKTOP-Q95VB79</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>3526180 MB</PhysicalMemory>
    </Environment>
    </SDLErrorDetails>
  • 0 in reply to Bruno Depascale

    Hi  

    Unknown said:
    I submitted a support ticket and Bogdan solved this issue, renaming the main folder for Studio and also renamed and did a reset to the settings, plugins and base settings for Studio( which were hidden by default ).

    Great... so he basically did what was already suggested in here?

    Unknown said:
    However, I have now another problem :), namely the fact that Studio keeps crashing and that I got this error message: "Could not load file or assembly 'Sdl.TranslationStudio.Plugins.WorldServerTranslationProvider.Api"
    please see below the error details. By the way, I have to deliver a job now and I don't know what to do :)

    Try this:

    Reinstall World Server Components

    1. Make sure all  SDL applications are closed.
    2. Go to c:\ProgramData\Package Cache\SDL\SDLTradosStudio2017_SR1\modules\.
    3. Run the WorldServerComponents.msi installation file.

    Open SDL Trados Studio 2017 and try again.

    Paul Filkin | RWS

    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

    Dear Paul,
    Thank you for your reply. Bodgan solved this issue on my computer.
    However, Trados keeps crashing during the translation jobs and I HAVE TO WORK!!! I don't know what else to do. I have the latest version of Windows with all updates installed. I recently formatted my pc and it works perfectly, except for trados. Can you please tell me what can I do (except removing and reinstalling Trados, which I have done a dozen times already)?!
    Thank you :)

     And again, apart from crashing 20 times per day, term recognition only works from time to time...

    I know it is not your fault, but I have paid this software to work, and all it is doing right now is wasting a huge amount of my time.