• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 49 subscribers
  • Views 1148 views
  • Users 0 members are here
Options
Related

Error message "TranslationProviderThrewException" when updating the main TM

Nadine Kontny

Hello everyone,

Recently I have been getting the error message "TranslationProviderThrewException" when I try to update the TM via the Batch task "Update Main translation memories".

In our company, all translators work with SDL Trados Studio Professional 2019 SR2. All our TMs are located on a server (SDL Trados GroupShare 2020 SR1). We have been working with this version for about a year.

I have already tried to work around the problem by exporting the content of my translation from the project TM to a tmx file and importing it into the main TM on the server. Unfortunately, that didn't work either, I got the error message "Error: System - Could not allocate space for object X' because the PRIMARY filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup".

Now I'm wondering if there is not enough space on the server or if we need to organise our TMs on the server (8 in total) differently (in separate containers)...?

On the other hand, so far only me and 2 other colleagues have had this error message, all the others have no problems even though they use the same TMs.

 I have already looked at the other articles related to this message but found nothing suitable. Our TMs seem to be up to date (the installation of the new Studio version was done by an SDL technician).

 Can anyone help?

Nadine
emoji
Rate translation
×
Suggest better translation
×
  • 0

    Hi 

    To address this error where you mention: 

    Nadine Kontny said:
    Error: System - Could not allocate space for object X' because the PRIMARY filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup

    We believe the issue to be caused by reaching storage capacity on database. So our recommendation would be to create a new DB to store the new data/TMs or update to a higher version of SQL which raises the default 10GB limitation per DB. 

    How big are your TM's collectively? As it seems clear server spec and operational requirements need evaluating which I believe you already assumed given you mentioned 

    Nadine Kontny said:
    enough space on the server or if we need to organise our TMs on the server

     I hope this information clarifies your next step

    Lyds

    Lydia Simplicio | 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

    emoji
  • 0 in reply to Lydia Simplicio

    Hello Lydia!

    Thanks a lot for your answer.

    In the meantime, we have "solved" the problems with our server TMs or rather worked around it.

    In fact, I have created new TMs with the same structure and put the content of our old TMs in them by tmx exports. Then, after verifying that the new ones work, I have deleted the old ones. And, I put all these TMs in a newly created DB Container.

    I can't tell you why but it has worked - we have no more error messages or server problems. Perhaps, the TMs were too old...? They exist since 2009 but were continuously adapted to the new Studio versions. I have no idea but I'm happy thal all works (at least for the moment ;-) ).

    Nadine
    emoji