Lech Lachowski 

Customising batch tasks is a feature available only in the Professional licence of Trados Studio. If you have a Freelance version, you can’t customise batch tasks. You don’t mention the type of licence of your Trados Studio copy, but this is my first guess…

Hi  Jesús Prieto 

I do not Think You are qutie right. I have freelance subscription for almost two year now, and this option was always available. I was very suprised lately when I couldn't curomize my batch tasks in my recent project. If You cut functionlity on freelance subscription, this does not speak well of RWS. If You will continue this cutting I will just change my CAT provider, because it is not a fair approach to the customer.

I will no longer mention the plethora of bugs in the Trados 2024 version and the problems with cloud options because I have written posts about it, which you can feel free to read In general, it is absurd and you will tell me that the option to customize batch jobs was not available earlier in the freelance version of studio, because I used it. if you do not believe my word, please check previous versions of Trados Studio 2022 in freelance subscription.

Best regards,

Lech Lachowski

Hello Lech, Jesús, Paul,

Just FYI, 2024 seems to really mess with tasks. I use 2022 Pro, since I installed 2024 Pro (I had to uninstall, too unstable), custom batch tasks do not work well in 2022 (I never got to make them work in 2024). Even if they do exist, they are not shown in the batch task menu anymore, not even after uninstalling and reinstalling (I was forced to do it manually).

Cheers,

Antonio

Antonio Jiménez Esteller 

You should check where you saved them.  If you did it for a specific Project then it will only be available for that project... similarly for project templates.  Maybe this is your problem?  I use them all the time and normally use them in different project templates and don't have this problem.

Thanks for your answer Paul, always so responsive. I wish I had made that mistake.

I defined all my batch tasks as Default from the Main Options menu, and they are available when I follow the steps to create a new project using the Default template or any other template. However, after the project is created, the custom task I have just applied to that project does not show at all in the menu with that (or any other) project selected. If I go to the Batch tasks dialog box, the custom tasks do show up (I now have just 2, since they are useless to me), but as soon as I select one of them and click Close, Studio closes abruptly with an error message. 

As I said, this happens since I installed 2024 and I have never been able to make it work, not even uninstalling and reinstalling. It is not the first time I uninstall a unstable new version (I have used trados since it was MS-DOS), but it has never messed with the existing version. 

Unfortunately I do not have time now to refresh Windows in my working machine and reinstall (too many licenses). When I have some time I will try with my portable

Antonio Jiménez Esteller 

Can you provide the full error stack for the error please?  These screenshots are not helpful:

Save the xml error you get and then attach to your reply (Insert - Image/Video/File).  That may point to the problem which could be related to you using old templates in 2024 for example?  You cannot do this, especially if you are using plugins as part of your tasks.  I am guessing a bit based on your screenshot, but the error stack may tell us more.

Hello Paul, Here it is:

<SDLErrorDetails time="25/07/2024 17:38:54">
  <ErrorMessage>El valor no puede ser nulo.
Nombre del parámetro: templates</ErrorMessage>
  <Exception>
    <Type>System.ArgumentNullException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <ParamName>templates</ParamName>
    <HelpLink />
    <Source>Sdl.ProjectApi.Implementation</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   en Sdl.ProjectApi.Implementation.Workflow.CreateComplexTaskTemplate(String name, String description, ITaskTemplate[] templates)
   en Sdl.TranslationStudio.Common.Tasks.SelectTaskTemplate.CustomTaskTemplateItem.GetTemplate()
   en Sdl.TranslationStudio.Common.Tasks.SelectTaskTemplate.SelectTaskTemplateViewModel.ExecuteManageTaskSequences()
   en Sdl.Platform.UI.Command.RelayCommand.Execute(Object parameter)
   en MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
   en System.Windows.Controls.Primitives.ButtonBase.OnClick()
   en System.Windows.Controls.Button.OnClick()
   en System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
   en System.Windows.UIElement.OnMouseLeftButtonUpThunk(Object sender, MouseButtonEventArgs e)
   en System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
   en System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   en System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   en System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   en System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
   en System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
   en System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
   en System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   en System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   en System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   en System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   en System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
   en System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
   en System.Windows.Input.InputManager.ProcessStagingArea()
   en System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
   en System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
   en System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
   en System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   en System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   en MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   en MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   en System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   en System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   en System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   en MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   en System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   en System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   en System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   en System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   en Sdl.TranslationStudio.Application.Launcher.RunApplication()]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>Trados Studio</ProductName>
    <ProductVersion>Studio17</ProductVersion>
    <EntryAssemblyFileVersion>17.2.10.19084</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 11 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>3082</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser> </LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName> </ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16688880 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Antonio Jiménez Esteller 

It seems as though your project template is missing something and whilst Studio should really handle these things gracefully it's not, possibly because you do seem to use various plugins and have these in your template, so it's unlikely the QA team tested these specific things.  Can you try creating a completely new template, not based on anything you had before, and create some custom tasks in there based on the things you have available right now.  Then test again with this new template and see if you still have similar problems with it?

Hi  Paul 

the real problem is as I said, and  Antonio Jiménez Esteller  confirmed, Trados Tsudio 2024 is very unstable and it should be staged verion only. And one important thing. With any other software, when I instal upgrade I do not need to mess with some files with user directory. In my case, after intalling Trados Studio 2024 my previous projects stopped beeing visible on the list. It no should be the case. Each upgrade should be compatybile withe the previous, but in the case of Trad Studio, before install any upgrage one shhould clean previous instalation including user file with settings and projects, and then they can install new version. If You tell me this is normal...

I just got back to Trados Studio 2022 and this way I do not have problems anymore. At least this kind of problems.

Kind regards 

Lech Lachowski

Hello Lech, Paul,

Paul, the screenshots I showed are from the scenario you suggest: I deleted the default template, it was automatically re-created blank and I used it. I tried this several times already.

And I agree with Lech, 2024 installation should never mess with 2022. I am glad Lech problems are over now that he is back to 2022.

Cheers,

Antonio

Lech Lachowski 

Lech Lachowski said:

In my case, after intalling Trados Studio 2024 my previous projects stopped beeing visible on the list. It no should be the case.

If you expected this to just be there then this is never the case.  The projects list will be empty because there is no migration process of any resources between versions.  All Studio versions are completely independent of one another and always have been.

Lech Lachowski said:

Each upgrade should be compatybile withe the previous, but in the case of Trad Studio, before install any upgrage one shhould clean previous instalation including user file with settings and projects, and then they can install new version.

This is not the case.  I never clean anything before an installation.

Most problems I see with these sorts of things are the result of users attempting (and I don't blame them for this as I would also try to find ways to make it easier if I didn't know better) to brings in resources from an older version to the new product.  By resources, I am not referring to TM's, TB's as these always work between versions, but rather things like User Profiles, Project Templates, Filetype Settings.  Unfortunately this is never a good idea as you can introduce problems because of incompatibility if you don't know enough about what will work and what won't.  Often this can mean understanding more about the versions of specific resources within Studio and this probably goes beyond what any user would spend time on.

Antonio Jiménez Esteller 

Antonio Jiménez Esteller said:

Paul, the screenshots I showed are from the scenario you suggest: I deleted the default template, it was automatically re-created blank and I used it. I tried this several times already.

The error stack you provided tells us the most likely source of the problem is that somewhere in the code, the templates argument is not being properly initialized or assigned before being passed to the CreateComplexTaskTemplate method. This could be due to things like this:

• A logical error where the templates array is not created.
• A missing assignment where the templates array is not populated.
• A condition where the templates array is conditionally assigned and the condition fails.

Based on the screenshot the areas I would be suspicious about would be where the custom tasks have used plugins.  Perhaps you can provide details of the plugins you have used, so I don't have to guess them all, and also confirm what steps the custom tasks consist of?  Then I can attempt to reproduce the errors... and I am very happy to try this.  If I just reuse the default template on its own I definitely don't get problems, and if I create custom tasks using Studio features without plugins I also don't get problems.  This all reinforces my opinion that the problem here lies with more specific actions that you have carried out on your templates.

Hello Paul, thanks for your offer to help, I do really appreciate it.
This all started happening when I installed 2024. Everything was working ok before. I guess as you say it has something to do with templates or plugins, but it continues to happen with a blank template and a clean install, after all possible sorts of uninstalls. I have found a way to work around that after many hours and I have spent too much time.
I will reset my working machine as soon as I have time and then I will try again, but I am afraid I have no time now, just too busy these weeks.

Hello Paul, thanks for your offer to help, I do really appreciate it.
This all started happening when I installed 2024. Everything was working ok before. I guess as you say it has something to do with templates or plugins, but it continues to happen with a blank template and a clean install, after all possible sorts of uninstalls. I have found a way to work around that after many hours and I have spent too much time.
I will reset my working machine as soon as I have time and then I will try again, but I am afraid I have no time now, just too busy these weeks.