Concordance and TM Lookup behave strangely

Hi

I don't know if you experience the same, but after installing CU8 we have issues with Concordance and TM Lookup. Some segments that we know for sure, they are in the TM are not  found by both. E.g. "Freundliche Grüsse" is an extact match that I can find when I search the TM in the TM view, but it is not found by Concordance or by Lookup. I reindexed the TM, but nothing changed.

Any thoughts?

Thanks,

Angelo

Parents Reply Children
  • Hi

    I could not reindex, it failed. It came out that I had a corrupted container. This is what I wrote on Monday to SDL support:


    Hello Laura

    It does not matter anymore.

    I had a huge problem during the week-end. I realized that in most TMs Concordance and LookUp did not work correctly (could not find segments that I know they hat to be there, and that I found in the TM search but not in the Editor with Concordance and Lookup). Somehow after the upgrade to CU8 one of my container was corrupted (the one that gave also the strange errors relating to Language Resource Template). I could not even open one TM in WebUI and click on Finish without making any change and I got the mentioned error. And other errors. I restored the server to CU7 and the problem was gone. I backed up the sql database of the  container in CU7, restored back to CU8, restored the sql db, but after opening Studio I got the message that the TMs structure had changed, so I could not use them.

    After several attempts of restoring, backing up, both the server and the SQL databases, and so one, the only thing I could do to fix the problem was to export all TMs in CU7, restore the server with CU8, delete all TMs, delete the container, recreate the container, import all TMs and update them with all the projects completed on September 6 and 7.

    Not what I had in mind for my week-end in Rome! But I could not wait till this morning to get support from SDL, because my people had to work this morning.

    I can send you all the CU8 logs and the backup of the SQL database of the damaged container, if it could help you to understand the problem.


    Thanks and regards

    Angelo