You are currently working on UAT 

  • State Suggested Answer
  • Replies 4 replies
  • Answers 3 answers
  • Subscribers 429 subscribers
  • Views 1598 views
  • Users 0 members are here
Options
Related

Error: Invalid Date String when upgrading TM - Studio 2019

Marisol Lieve

Hello,

I get the error message "Invalid Date String" when trying to upgrade a translation memory in the Translation Memories view in Studio.

Any help?

Many thanks!

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

    This I believe happens when the TM becomes corrupt- which can happen for instance: if the TM's are stored in the cloud (not locally) and the internet connection is at best flaky.
    You can test if the TM is corrupt by trying to open it in the Translation memory pane in Studio.
    If so you can try and repair using the following free app
    appstore.sdl.com/.../

    It is always a good idea to back up your TM's (no matter where they are stored).
    appstore.sdl.com/.../

    If you need to reset Studio- navigate to the following address-
    C:\Users\[username]\AppData\Local\SDL\SDL Trados Studio\15.0.0.0
    and rename the Translationmemoryrepository.xml (just add _OLD at the end and then restart Studio.

    Did this help?

    Oana Nagy | QA Engineer | RWS Group

  • 0 in reply to Oana Nagy

    Hi Steven,

    Many thanks for your reply.

    I had already tried the SDLTM Repair app and reset Studio but without any luck.

    I can actually open the TM but Studio warns me that it needs maintenance, then the process fails. Please see the error message details:

    Process failed (28/01/2019 12:42:30)
    System.Exception: Invalid date string: �
    at Sdl.LanguagePlatform.TranslationMemoryImpl.Storage.Utils.StringToDate(String s)
    at Sdl.LanguagePlatform.TranslationMemoryImpl.Storage.SqliteStorage.GetDateTime(DbDataReader reader, Int32 column)
    at Sdl.LanguagePlatform.TranslationMemoryImpl.Storage.DbStorage.ReadTu(DbDataReader reader)
    at Sdl.LanguagePlatform.TranslationMemoryImpl.Storage.DbStorage.GetTuRange(DbCommand getTusCmd)
    at Sdl.LanguagePlatform.TranslationMemoryImpl.Storage.SqliteStorage.GetTusForReindex(Int32 tmId, Int32 startAfter, Int32 count, Int64 currentSigHash)
    at Sdl.LanguagePlatform.TranslationMemoryImpl.ResourceManager.HasLegacyFileBasedHashChanges(AnnotatedTranslationMemory tm, Int64 currentHash)
    at Sdl.LanguagePlatform.TranslationMemoryImpl.ResourceManager.ReindexTranslationUnits(PersistentObjectToken tmId, CancellationToken token, IProgress`1 progress, Boolean selective)
    at Sdl.LanguagePlatform.TranslationMemoryImpl.API.SelectiveReindexTranslationUnits(Container container, PersistentObjectToken tmId, CancellationToken token, IProgress`1 progress)
    at Sdl.LanguagePlatform.TranslationMemoryApi.FileBasedTranslationMemory.SelectiveReindexTranslationUnits(CancellationToken token, IProgress`1 progress)
    at Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoryAutomation.Jobs.SelectiveReIndexTranslationMemoryJobRequest.Execute(IJobExecutionContext context)

    Any other workaround?

    Thanks!

    Marisol
  • 0 in reply to Marisol Lieve
    Hello ,

    I believe the above indeed refers to a corrupted memory.
    If using TMRepair did not work- then you can try and export the TM to TMX- and try and clean up the TM
    Maybe the following program could help - okapi.sourceforge.net/.../

    Then import the TMX into a new TM.

    Also did you rename the Translationmemoryrepository.xml?

    Oana Nagy | QA Engineer | RWS Group

  • 0 in reply to Oana Nagy
    Hello ,

    We encountered a problem with the app (which is why it appeared not to work).
    This has now been fixed.
    Please remove the old version from your system and install the new version from the app and try again.

    Oana Nagy | QA Engineer | RWS Group

Reply Children
No Data