OK, it appears to be a problem with this one TM. Does anyone know of a repair tool or something that can be run in SQL or SDL Groupshare itself?

Hi Bobby Lahiere - Were you able to address / figure this out? Did you find the TM Service log entry for this error as Raphael suggested? In terms of the TM Repair tool, there is none that works directly on GroupShare or SQL. This one works with file-based TMs: https://appstore.sdl.com/language/app/sdltm-repair/298/ - also in general some "repairs" can be done just by exportin the GroupShare TM to tmx, creating a Studio file-based TM, then exporting from that again to TMX then using this TMX to create a new TM in GroupShare. Another 3rd party powerful tool to manipulate tmx files, including for the purpose of troubleshooting is Okapi Olifant: http://okapi.sourceforge.net/downloads.html - I hope this helps. Let us know.

Thank you

Adrian

We thought about exporting and repairing, but as you can see from my initial post, the system was not letting us export. After many attempts, it finally did, so who knows...all of this software has been quirky since we bought it and unless you pay the obscene fee for support, you are on your own...so we'll figure it out.

Hi Bobby Lahiere - interesting that it worked after many attempts. So after it exported, did you recreate the TM? It would still be good to know what happened. This space (communities) is being developed more and more and we hope that it will become the go-to place especially in situation where customers do not choose to have a Support Contract.

Hi Bobby Lahiere - interesting that it worked after many attempts. So after it exported, did you recreate the TM? It would still be good to know what happened. This space (communities) is being developed more and more and we hope that it will become the go-to place especially in situation where customers do not choose to have a Support Contract.