Due to essential maintenance, access to Trados cloud will be unavailable on Saturday 30 August from 00:00 to 12:00 UTC.
  • State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 434 subscribers
  • Views 655 views
  • Users 0 members are here
Options
Related

TMs in packages created with up-to-date Studio 2017 Pro give "The string was not recognized as a valid DateTime" error in Studio 2011 since around 07/2017

Jouni Karhu

The client claims that Studio 2017 is not compatible with Studio 2011, but this is not supported by the information on the SDL website. The translation memories should work just fine with 2011, and they *did*, until *something* happened in around July-August 2017. Since then, the memories either give an error right out, saying that the memory could not be opened because of the DateTime error, or they work for a while until a memory search runs into this kind of a string and gives an error message in the messages pane.

Yes, the client has the latest updates, and yes, I have the last version update for 2011 as well.

I have not found anything in my Web searches indicating that this is a widely occurring thing. I am running Windows 10 Home, and changing the locale/format etc. to English does not appear to have any effect compared to using the Finnish locale and format.

Anybody have any ideas? Is this a Windows thing, is this a runtime environment thing - should I update to Visual Studio 2017 runtime, or what have you?

I do realise that 2011 is no longer compatible with TM servers, but these are packages with the full memory included. If I get the memory as a TMX export, I can create a memory and import it just fine.

// JJ
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hello ,

    It is really difficult to say what could have caused and still is causing the problem and although in theory 2011 packages may support PPX packages from newer versions, this is not always the case depending on how the package was handled.

    If your client is running Studio 2017- then they are also going to be running .net 4.5.x framework or higher- where as you will likely be running .net 4.2.x (Studio 2019 uses 4.7.x) so there could indeed be some compatibility issues between the versions.
    By updating your .net and visual platforms, your version of Studio may not run at all.
    Therefore I suggest testing these packages on a colleagues/ friends machine with a newer version of Studio installed.
    Then you will have a very good reason to upgrade.
    Don't forget, older versions of Studio cannot handle newer Office/Indesign file types etc.either.

    Lydia Simplicio | 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

Reply
  • 0
    Hello ,

    It is really difficult to say what could have caused and still is causing the problem and although in theory 2011 packages may support PPX packages from newer versions, this is not always the case depending on how the package was handled.

    If your client is running Studio 2017- then they are also going to be running .net 4.5.x framework or higher- where as you will likely be running .net 4.2.x (Studio 2019 uses 4.7.x) so there could indeed be some compatibility issues between the versions.
    By updating your .net and visual platforms, your version of Studio may not run at all.
    Therefore I suggest testing these packages on a colleagues/ friends machine with a newer version of Studio installed.
    Then you will have a very good reason to upgrade.
    Don't forget, older versions of Studio cannot handle newer Office/Indesign file types etc.either.

    Lydia Simplicio | 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

Children
No Data