You are currently working on UAT 

  • State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 429 subscribers
  • Views 1349 views
  • Users 0 members are here
Options
Related

Cannot change project settings, use search + replace anymore.

Georgina Wiersma

I have moved a project from my pc to my laptop and updated Trados 2017. It is 48000 words. I have translated it, just corrections now.

Since then, a number of features cannot be used, a.o. 'Insert translation with Ctrl T, Crtl Z (undo), I cannot use the feature Search and Replace (greyed out, Crtl F does not work). I can still work on the file and save it though... As this is a package from a client, I cannot just create a new project.

 I have copied the error message that I get when I try to check the project settings:

 

<SDLErrorDetails time="17-10-2018 14:07:48">
<ErrorMessage>Het doel van een aanroep heeft een uitzondering veroorzaakt.</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[ bij System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
bij System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
bij System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
bij System.Activator.CreateInstance[T]()
bij Sdl.Desktop.Platform.Settings.SettingsPageReference`1.Initialize()
bij Sdl.Desktop.Platform.Implementation.Settings.AbstractSettingsHost.EnsurePageInitialized(ISettingsPageReference r)
bij Sdl.Desktop.Platform.Implementation.Settings.AbstractSettingsHost.ActivateSettingsPageCategory(String[] path)
bij Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractProjectSettingsAction.<Execute>b__3_0(ISettingsDialog d)
bij Sdl.TranslationStudio.ProjectManagement.Actions.ProjectSettingsDialogHelper.Show(IProject project, IProjectManagementService service, ConfigureProjectSettingsDialogDelegate configureProjectSettingsDialog)
bij Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractProjectSettingsAction.Execute()
bij Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass30_0.<ExecuteAction>b__0()
bij Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
bij Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
bij Sdl.Desktop.Platform.WinForms.IgCommandBarAction.Execute()
bij Sdl.Desktop.Platform.WinForms.IgCommandBarAction._lazyButtonTool_ToolClick(Object sender, ToolClickEventArgs e)
bij Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick(ToolClickEventArgs e)
bij Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnToolClick(ToolClickEventArgs e)
bij Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.FireEvent(ToolbarEventIds id, EventArgs e)
bij Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick()
bij Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.DoClickProcessing(MouseEventArgs e)
bij Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.OnMouseUp(MouseEventArgs e)
bij Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)
bij Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)
bij Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e)
bij Infragistics.Win.UltraWinToolbars.UltraToolbarsDockArea.OnMouseUp(MouseEventArgs e)
bij System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bij System.Windows.Forms.Control.WndProc(Message& m)
bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
<InnerException>
<Type>System.ArgumentNullException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
<ParamName>source</ParamName>
<HelpLink />
<Source>System.Core</Source>
<HResult>-2147467261</HResult>
<StackTrace><![CDATA[ bij System.Linq.Enumerable.Where[TSource](IEnumerable`1 source, Func`2 predicate)
bij Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoriesControl..ctor()
bij Sdl.TranslationStudio.ProjectManagement.Settings.TranslationMemoriesSettingsPageControl.InitializeComponent()
bij Sdl.TranslationStudio.ProjectManagement.Settings.TranslationMemoriesSettingsPageControl..ctor()
bij Sdl.TranslationStudio.ProjectManagement.Settings.TranslationMemoriesSettingsPage..ctor()]]></StackTrace>
</InnerException>
</Exception>
<Environment>
<ProductName>SDL Trados Studio</ProductName>
<ProductVersion>14.0.0.0</ProductVersion>
<EntryAssemblyFileVersion>14.1.10014.38031</EntryAssemblyFileVersion>
<OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
<ServicePack>NULL</ServicePack>
<OperatingSystemLanguage>1043</OperatingSystemLanguage>
<CodePage>1252</CodePage>
<LoggedOnUser>DESKTOP-J6PAAE8\GeorginaW</LoggedOnUser>
<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
<ComputerName>DESKTOP-J6PAAE8</ComputerName>
<ConnectedToNetwork>True</ConnectedToNetwork>
<PhysicalMemory>6191468 MB</PhysicalMemory>
</Environment>
</SDLErrorDetails>
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hello ,

    The Stack trace would seem to suggest the issues are at least, in part caused by an issue with the project management/translation memories which appear to have been corrupted with the move to a new machine.

    Firstly (and the easiest option) is you can try 'Reset Windows Layout' (from the VIEW tab) which resolves a number of unexpected issues.
    Next would be to reset Studio -We have a free app that can help you with this.
    community.sdl.com/.../3212.sdl-freshstart

    If this does not work, then you may need to recreate the project and then 'Pre-Translate' through BatchTasks which should get you back to the stage you were in the translation.
    To do this, simply save the original SDLPPX and change this to a .ZIP file- Unzip the files and then import the resources into your own project (including the TM(s) replacing the new SDLXLIFF file with the original and then run a BatchTask/Pre-translate.
    It is worth remembering that when you return a package, this will only contains the SDLXLIFF file. In my experience most clients have no problem with this when you explain the issues.

    Please let me know how you get on.

    Oana Nagy | QA Engineer | RWS Group

Reply
  • 0
    Hello ,

    The Stack trace would seem to suggest the issues are at least, in part caused by an issue with the project management/translation memories which appear to have been corrupted with the move to a new machine.

    Firstly (and the easiest option) is you can try 'Reset Windows Layout' (from the VIEW tab) which resolves a number of unexpected issues.
    Next would be to reset Studio -We have a free app that can help you with this.
    community.sdl.com/.../3212.sdl-freshstart

    If this does not work, then you may need to recreate the project and then 'Pre-Translate' through BatchTasks which should get you back to the stage you were in the translation.
    To do this, simply save the original SDLPPX and change this to a .ZIP file- Unzip the files and then import the resources into your own project (including the TM(s) replacing the new SDLXLIFF file with the original and then run a BatchTask/Pre-translate.
    It is worth remembering that when you return a package, this will only contains the SDLXLIFF file. In my experience most clients have no problem with this when you explain the issues.

    Please let me know how you get on.

    Oana Nagy | QA Engineer | RWS Group

Children
No Data