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

Lech Lachowski 

Lech Lachowski said:

If You cut functionlity on freelance subscription

I cut nothing. I’m just a Trados Studio user..

This link mentions that a Freelance licence can’t create custom batch tasks: https://docs.rws.com/1145319/303450/trados-studio-2024/trados-studio-editions

being the cell highlighted in the Freelance edition column. And it has been like that fro years...

Lech Lachowski said:

if you do not believe my word, please check previous versions of Trados Studio 2022 in freelance subscription.

Sorry, I can’t check that since I have the Professional version. But other peers may post their findings…

Lech Lachowski said:

I do not Think You are qutie right. I have freelance subscription for almost two year now, and this option was always available.

He is correct.  This has been a differentiator between professional and freelance since 2009.

Hi  Paul 

mayby this is even truth but lets nt forgeto of pletoria bugs of ne version of trados studio 2024 This should betestunf version only. I have written many posts on this subject today and I got to the point of frustration.

Bestre gards,

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

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.

Hi  Paul 

Paul said:

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.

Paul, with all due respect, but a new software version should always be compatible with the previous one. Take, for example, the Google Chrome upgrade (retains user settings, passwords, cookies, history, etc.). Filezilla upgrade does not save saved servers and passwords. Such examples can be multiplied.

Paul said:

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

Paul, you are contradicting yourself, since you are not deleting anything the projects and settings should be preserved, which is not the case. Also, if I don't remove everything, a whole new installation throws errors every now and then. And this was alwayst the case even when it came to majaor upgrade withinin Studio 2022 - I was always loosing my settings and projects and got many errors. 

According to software best practices, every new version should be compatible with the previous one, and I'm not talking about compatibility with the version from 10 years ago, but at least with the previous one, even more so when it comes to projects.

Not to mention that the software I mentioned earlier is free, and Trados Studio is commercial software, so it should work even better, and the opposite is true.

Hi  Antonio Jiménez Esteller 

Thank you for your support because no one else wants to report that Trados Studio is very unstable and unusable.

Best regards,

Lech Lachowski

Lech Lachowski 

Lech Lachowski said:

Paul, with all due respect, but a new software version should always be compatible with the previous one. Take, for example, the Google Chrome upgrade (retains user settings, passwords, cookies, history, etc.). Filezilla upgrade does not save saved servers and passwords. Such examples can be multiplied.

I agree.  I am not disputing this at all, and in fact I do wish we had a better upgrade process that properly managed the transfer of data between versions, and the situation where new features make old ones redundant.  We may not be able to automatically support them because we are talking about things a lot more complex than Google Chrome or Filezilla, but we could make sure that they are not taken across into the new software even when a user attempts to do so.

All I stated is that there is no migration process of any resources between versions.  All Studio versions are completely independent of one another and always have been.  This is a fact and I didn't make any reference about what should and shouldn't occur.

Lech Lachowski said:

Paul said:

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

Paul, you are contradicting yourself, since you are not deleting anything the projects and settings should be preserved, which is not the case.

No I'm not, you have misquoted me.  Context is everything.  You said this:

Lech Lachowski said:

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.

But this isn't true, you don't have to clean anything and this is what I was replying to.

On reflection I wonder if what you really meant was that you have to move your projects and files from one location to another and cannot reuse the ones that were located in the previous version?  If this is the case then this is only partially true.  The location of projects is down to you.  If you decide to leave them in the default location which is indeed placed into a folder named after the version of the software you used at the time then this is your choice.  A more sensible way to work would be to store your projects, Translation Memories and Termbases is a location completely independent of the installation directories.  The software supports you doing this.  If you work this way then you never have to move them at all.

Settings are a different thing and even here the picture is a little grey.  Your project settings will stay with the projects, so these are indeed carried over as soon as you open the project in the new version.  However, if there are new filetypes in the new version for exa,ple you'll see additional messages in the settings telling you that new filetypes exist for example.  That seems logical since they were not in the previous version, but you probably won't really need them in an existing project anyway.

Older filetypes that are no longer supported and will not be in the new version are normally supported under the hood.  This is so your existing projects created in the older version can be completed successfully, but you should not be able to create new projects with these old and defunct versions.  There is a limit to this however, if you open a project from a really old version this may not be the case and you might not be able to save target files for example.  But again this is to be expected I think.  If users upgrade from version to version there is less likely to be problems but if they don't we cannot be expected to continually support, and provide legacy code in the product for every version we ever created.  Fortunately most users upgrade from version to version.  Sadly we don't see a balanced view of this in the forums for obvious reasons!

I did say that the picture with settings is a little grey and this is because things like project templates are better not reused.  I would always advise users to recreate their project templates.  This is because older templates will be using older code and potentially introduce problems into the new version.  This is an area I wish we did have a neat migration process but this is more complex than you probably think through.  That doesn't mean we shouldn't do it, it just means the complexity involved versus the benefits as a whole probably keep this lower in the overall priority and scheme of things.  We did look at this once with the migration tool in the appstore but in my opinion it's more trouble than it's worth because we cannot do this properly using the APIs.  It really needs to be done at the level of the core product.

All in all I'm not contradicting or arguing with you at all.  I'm just trying to explain to you how this works and am clarifying the statements you make that seem to be incorrect.

Lech Lachowski said:

Thank you for your support because no one else wants to report that Trados Studio is very unstable and unusable.

I wish!!