• Replies 13 replies
  • Subscribers 47 subscribers
  • Views 4376 views
  • Users 0 members are here
Options
Related

Cannot search our TMs

Jesse Good

Hi, we waited to update to Groupshare 2017 because of the many issues we heard, but we finally decided to take the plunge since it has been out for over a year now. However, as soon as we started to use it, we hit several issues that are important to our business processes:

1. We have many TMs over 200k, and we cannot search them!

https://gateway.sdl.com/communityknowledge?articleName=000003845

2. The TM export feature, TM indexing and other tasks cannot be canceled?
They remain queued even after hitting cancel in Trados Studio

3. Checking in large files times out

Overall, as a customer we are not having a very good experience...
Rate translation
×
Suggest better translation
×
Parents

  • Hi  

     I spoke to support, who don't seem to be aware of your logged case yet, but this is what they told me:

    1.  The issue is most likely CRQ-4012 which we know about.  It is planned to be addressed with the next set of updates for SDL Trados GroupShare, SDL Trados Studio (2017 SR1 + 2019)
    2. This is indeed the default behaviour, which existed ever since in Studio, even before GroupShare 2017.
    3. This can have various causes, e.g. might be down to the overall performance of the GS system or even the known issue with bigger file/# of files in the affected project, e.g. CRQ-4119 or as you are most probably already using CU03, LTGS-560.

    The best course of action is to make sure you have a case loggedand we can look at this properly.  But at least we have some issues known to check against.

    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

Reply

  • Hi  

     I spoke to support, who don't seem to be aware of your logged case yet, but this is what they told me:

    1.  The issue is most likely CRQ-4012 which we know about.  It is planned to be addressed with the next set of updates for SDL Trados GroupShare, SDL Trados Studio (2017 SR1 + 2019)
    2. This is indeed the default behaviour, which existed ever since in Studio, even before GroupShare 2017.
    3. This can have various causes, e.g. might be down to the overall performance of the GS system or even the known issue with bigger file/# of files in the affected project, e.g. CRQ-4119 or as you are most probably already using CU03, LTGS-560.

    The best course of action is to make sure you have a case loggedand we can look at this properly.  But at least we have some issues known to check against.

    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

Children