Cannot search our TMs

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...

Translate

Rate translation

Suggest better translation

Parents

Mitja Kelenc over 6 years ago

Hi Jesse, we have GU 2017 on producing since it got out from CU2. We had this issues also but with CU 4 thing get better. Do not import over Studio it takes a lot of time. because of alignment after import. this is also Failed every time with bigger imports. We always import over GroupShare Website. There you can see better what is going on when importing. Which CU do you have? We have some performing issues but in all GU 2017 is better than GU 2015.

We have multiple TMs with over 750K TU's. When searching concordance where results are big just try to concordance search multiple words.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Jesse Good over 6 years ago in reply to Mitja Kelenc

Hi Mitja

Thank you for the advice.
We are using 14.2.20522.7 - SR1 CU7.

However, right now I cannot even check out files or publish files on the server as it times out.
I've already set the time out to 180 for all Proxy but it doesn't help...
gateway.sdl.com/.../000004673

Any ideas?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Enrico Rosso over 6 years ago in reply to Jesse Good

hello Jesse,
How big are the files you're trying to check-out?
Were projects published in GS2017 or inherited from GS2015?
Are local studio project files located on a networked drive?
Are you using the latest Studio version available?

While GS2017 has issues in checking-in/out files (sometimes you have to restart services in order to check-in) the latest CU(7) works fine enough even with big files.

Maybe it could be worth performing a trace route to your server to see if there's some slow node in the path and to measure network performance.

I know some questions may seem trivial, but at least you can phase-out the trivial issues.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Reply

Enrico Rosso over 6 years ago in reply to Jesse Good

hello Jesse,
How big are the files you're trying to check-out?
Were projects published in GS2017 or inherited from GS2015?
Are local studio project files located on a networked drive?
Are you using the latest Studio version available?

While GS2017 has issues in checking-in/out files (sometimes you have to restart services in order to check-in) the latest CU(7) works fine enough even with big files.

Maybe it could be worth performing a trace route to your server to see if there's some slow node in the path and to measure network performance.

I know some questions may seem trivial, but at least you can phase-out the trivial issues.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Children

Jesse Good over 6 years ago in reply to Enrico Rosso

Hi Enrico

1. Files are around 3 to 5 MB (only checking one out at a time)
2. Published in GS2017
3. Local projects are located in My Documents
4. Yes, latest version of Studio

I also sent all log files/error messages to SDL support.
I will let you know if I figure out the problem!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Enrico Rosso over 6 years ago in reply to Jesse Good

Good luck Jesse!
I can confirm, having myself a quite problematic GS2017 installation, that nonetheless you shouldn't have such issues with those files.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Jesse Good over 6 years ago in reply to Enrico Rosso

Okay, I think we found the root of the issue.
Basically we keep running our of hard disk space!
Does anyone know how much hard disk space we need?

Currently we have around 800 projects and 30 TMs. We have been trying to remove projects/TMs to free up space, but then the space keeps filling back up!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Enrico Rosso over 6 years ago in reply to Jesse Good

Hello Jesse, back in some older GS2017SR1 version there was an issue with log files set to "debug" level, so they kept growing in order of several Gbytes. I'd check log files for sdl services. also i'd check log files for sql server and plan a maintenance plan with shrink. Then Temporary folder. Also the new GS2017SR1 grows database space to accomodate the translation models for the new TM features (fragment search and such).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Jesse Good over 6 years ago in reply to Enrico Rosso

Hi Enrico

Actually I noticed the log files grow to GBytes on my server and I have to keep deleting them. Do you know how to change the level?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Enrico Rosso over 6 years ago in reply to Jesse Good

Sure, here it is:

https://gateway.sdl.com/apex/communityknowledge?articleName=000006001
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Burckhardt Rueffer over 6 years ago in reply to Jesse Good

We encountered the same issue - it was the debug log files that were switched on by default. The problem was solved by installing CU7, Version 14.2.20522.7. According to support, as a quick fix, you can kill those files - they are not needed and won't show up again after the upgrade.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Jesse Good over 6 years ago in reply to Burckhardt Rueffer

Thanks for the help! I was able to free up 400GB of space after removing the log files...
Now my next problem is matching isn't bringing up the 100% matches in the translation memory results window...
It seems re-indexing the TMs fixes this, but it keep returning a System.Net.Http.HttpRequestException when I reindex a TM
Anybody encounter this issue?

Also, we have TMs with 400,000 units or so, and it takes from 10 to 30 seconds to get results per segment and concordance is even longer...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Trados GroupShare > 1. General

Cannot search our TMs