SDL 2017 TMs corrupt with error "string is not recognized as valid datetime value".

 HI
Upgraded to 2017 and now my TMs are suddenly corrupt. The error message is "string is not recognized as valid datetime value". Any suggestions anyone?
TIA

  • Hi, Martti - would you be able to provide us with a TM that demonstrates this problem, e.g. by email to kflanagan@sdl.com or some other non-public means? I think this may be a SQLite issue that we can investigate.

    Regards

    Kevin

  • Hi Kevin
    Tried creating a new TM for your analysis, could not even do that: same error message.
    Martti
  • Hi Martti,

    If you are unable to create a new TM it sounds as though there is a problem with your installation. Please can you try resetting Studio first of all and then see if you can create a new TM?

    So rename this folder (just add _old to the end or something, it's not important what you rename it to) and restart Studio:

    c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\14.0.0.0

    It sounds as though Studio is hanging onto the problem you had before so a reset might clear this.

    Regards

    Paul

    Paul Filkin | 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

  • HI Paul
    Thanx. Tried it, no success.
    Removed all versions of trados, reinstalled 2017 - no success
    There seems to be a problem with the 1st TM this problem appeared with. I cannot export it and cannot really even browse it without trados warning me of possible corrupt TM.
    I finally managed to export it using wfconverter, but now I cannot use it to create a new TM since trados still wont create a new tm with any language combination (not just with the one of the 1st TM).
    So the problem is not with the TM after all....
    Please have some new suggestions ;)

    For now I have to go back to v. 2015 and wait for the next build of 2017
    regs
    Martti
  • Hi Martti,

    Can I see your TM? If it's a problem for Studio than I should be able to reproduce it and then we can fix it. If you have the exchange file that would also be useful. You can send them to pfilkin@sdl.com if this is ok? A link to the files in dropbox or googledrive would be fine.

    Regards

    Paul

    Paul Filkin | 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

  • HI
    the bloody thing is humungous, over 40MB zipped. And at this point I dont think that is the problem. Even if the TM was corrupted, how is it preventing studio from creating new TMs, which at this point is the biggest problem.
    I would be more interested to know how to ensure a totally clean re-install (without formatting the HD), to get rid of all historic settings which might foul the install.

    Possibly totally unrelated: can you explain why this studio by default tries to create the new TM into the system folder, which it of course cannot not do, and thereby creates another error unless I specifically define a different path. I could not find the default folder in settings.
    regs
    Marttti
  • Hi Martti,

    40Mb zipped isn't that big... but ok. No problem.

    Clean install... try the following.

    1. Uninstall Studio
    2. Uninstall MultiTerm

    Now manually delete these folders if they are still there (back up your TMs, Termbases, AutoSuggest Dictionaries and Projects first in case you make a mistake):

    c:\ProgramData\Package Cache\SDL\SDLTradosStudio2017\
    c:\ProgramData\Package Cache\SDL\SDLMultiTermDesktop2017\
    c:\Program Files (x86)\SDL\SDL Trados Studio\Studio5\
    c:\Program Files (x86)\SDL\SDL MultiTerm\MultiTerm14\
    c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\14\
    c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\14.0.0.0\
    c:\Users\[USERNAME]\AppData\Local\SDL\SDL MultiTerm\MultiTerm14\
    c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\14\
    c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\14.0.0.0\
    c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL MultiTerm\MultiTerm14\
    c:\Users\[USERNAME]\Documents\Studio 2017\Project Templates\
    c:\Users\[USERNAME]\Documents\Studio 2017\Projects\projects.xml

    I think that's about it for a clean install. Then reinstall.

    If you still have problems after this I'd recommend you log a ticket with support so an engineer can look at this for you. This is clearly an installation problems and for licensing or installation issues that prevent you from working we have a route for all customers to get help. This can be achieved really quickly using this link:

    http://support.xl8.one

    Just fill in the form and submit it. Make sure your email address is entered correctly or nobody will be able to get back in touch with you.

    Regards

    Paul

    Paul Filkin | 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

  • Thank you, i'll give it a try
    regs
    Martti
  • Hi Martti,

    Are you using Windows 10?

    There was a bug in the Finnish culture locale in Windows 10:

    http://www.heikniemi.net/hardcoded/2015/08/windows-10-breaks-net-date-parsing-in-certain-locales/

     

    Check if you have the following update installed:

    https://support.microsoft.com/en-us/kb/3093266

     

    However, the update seems to be for .NET 4.6 and Trados uses .NET 4.5.2....

    Another workaround would be to change the system locale in Windows 10...

    Also, do you see a floppy disk in the bottom-left corner?
    If you do, please save the error details and post them here.

  • HI Jesse
    Yep, win10
    But nope, "update does not apply to this computer" and changing the time separator did not help either.
    Sorry, cannot spot the floppy, any other places I could find a trados error log?
    tia
    Martti
1 2 3