Unable to rename specific TMs - problem with double entries in sts.Resource table

Hi community,

there is a special set of TMs on our GS 2014 Server which cannot be renamed to the correct name.

The error message is that the resource is already existing.

When looking into the sts.Resource table this is true: the resource name is already existing as resourceTypeID=8 i.e. also a TM.

But this TM will not be shown in the GS GUI.

So I guess the hidden TMs are hanging, not grounded.

Can I delete them in the sts.Resource table simply, or do I have to respect other side effects also?

Does someone has experience with removing not grounded objects from sts.Resource table?

Regards

Rainer

Parents
  • Hi,

    it looks as you detached TM container on SQL, so the sts.Resource table was not updated correctly and it still contains references to the non-existing TMs, if you would do it from GS UI, the sts.Resource should have been updated correctly and consistently. This is most natural explanation in my view, unless it is another glitch in GS. Could you let me know if my assumption is right or what did you actually do?

    Anyway, in general there are 3 tables which contain information about the resources (TMs, lng. resources, etc...) .

    - SDLSystem.etm.TranslationMemory

    - SDLSystem.sts.Resource

    - [ContainerName].dbo.translation_memories

    These have to be checked for inconsistencies. 

    regards,

    Fana

Reply
  • Hi,

    it looks as you detached TM container on SQL, so the sts.Resource table was not updated correctly and it still contains references to the non-existing TMs, if you would do it from GS UI, the sts.Resource should have been updated correctly and consistently. This is most natural explanation in my view, unless it is another glitch in GS. Could you let me know if my assumption is right or what did you actually do?

    Anyway, in general there are 3 tables which contain information about the resources (TMs, lng. resources, etc...) .

    - SDLSystem.etm.TranslationMemory

    - SDLSystem.sts.Resource

    - [ContainerName].dbo.translation_memories

    These have to be checked for inconsistencies. 

    regards,

    Fana

Children