Hi Pavel Tsvetkov

Hi Alison,

1. Firstly, have you made sure your version MultiTerm is also up to date? To do this, if you have automatic updates set, just open MultiTerm and accept any update offered. If you don't have automatic updates, set, go to Help > Check for Updates. 

Yes, no updates available.

2. If these suggestions don't help, try reinstalling.

I have just tried that to no avail.

3. Fill in the form here:

Paul,

Is there a log file or any other file produced by Trados on my end when it crashes while trying to open *any* project in the project list that I can send to you to take a look? I have my hands literally tied with this problem...

Regards,

Pavel

Hi Paul,

Thank you for you message.

1. I contacted support on Saturday, but there has been no answer so far: Case No. 00405188

2. I am not sure they will respond at all, as this might not qualify as an installation issue for which free support is due?

3. I have found the log file, but it only contains information from the current opening of Trados... So, anything before the crash is not in the log. Very strange.

4. If I remove a Project from the list, close Studio, then restart and add the project back in again, when I try to open the project, Trados freezes and then closes, unfortunately.

5. I have just tried creating a new project from scratch and the project gets created OK, but when I try to actually open it, Trados freezes and then closes.

Does this help identify the culprit?

Best regards,

Hi Denise,

Thank you for your message. That is definitely good news!

The question is when will that happen? It has been three days now and if I had an urgent project on my hands, I would have missed all deadlines... 

Best regards,

Pavel

Hi everybody!

Today the remote session with an SDL engineer finally took place and it was successful. The issue seems to be a corrupt installation of projectTermExtract plugin.

Some notes:

1. First and foremost, the issue was solved and I can now use Trados, which means that I am happy with the result.

2. The support ticket was logged four days ago (on a Saturday) and four days, in my opinion, is too long to wait. Yes, I understand that free support cannot be expected to react on the same day, but in a fast moving business like the translation business four days is forever.

3. The whole plugin system is at fault, I am afraid. So, SDL allows anybody to create a plugin and offer it to professional translators? Of course, they use the plugins at their own risk, but that is just to avoid litigation, it does not solve the plethora of problems that arise.

4. Also, if this was caused by a plugin, why was not the problem reported as a plugin problem by Trados? Or at least why not automatically disable the offending plugin or all plugins on next restart? Many software titles have this feature and it works.

Food for thought...

Best regards,

Pavel

Hi everybody!

Today the remote session with an SDL engineer finally took place and it was successful. The issue seems to be a corrupt installation of projectTermExtract plugin.

Some notes:

1. First and foremost, the issue was solved and I can now use Trados, which means that I am happy with the result.

2. The support ticket was logged four days ago (on a Saturday) and four days, in my opinion, is too long to wait. Yes, I understand that free support cannot be expected to react on the same day, but in a fast moving business like the translation business four days is forever.

3. The whole plugin system is at fault, I am afraid. So, SDL allows anybody to create a plugin and offer it to professional translators? Of course, they use the plugins at their own risk, but that is just to avoid litigation, it does not solve the plethora of problems that arise.

4. Also, if this was caused by a plugin, why was not the problem reported as a plugin problem by Trados? Or at least why not automatically disable the offending plugin or all plugins on next restart? Many software titles have this feature and it works.

Food for thought...

Best regards,

Pavel