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

Recompute fuzzy index error in GroupShare

Jonathan Fray

Hi,

I would like to know how to solve an error that is occuring when I run a "Recompute Fuzzy Index Statistics" on a TM in GroupShare. In the settings of the TM it says that this process has never been done and is recommended but when I try to run this operation "Reindex the TM" in GroupShare the following error shows up:

"Timeout expired. The timeout period elapsed prior to the completion of the operation or the server is not responding."

Is there any way to solve this as I'm afraid I'm not getting enough leverage out of this TM?

Regards,

Jonathan
Rate translation
×
Suggest better translation
×
Parents
  • 0
    Hi Jonathan,

    There is two different tasks "Recompute Fuzzy Index Statistics" which is very fast and should be straightforward.
    This actually happens automatically in the background since GroupShare 2015, so you don't need to run this manually.

    The "Re-index Translation Memory" is actually a much longer and heavy task and is rarely needed (usually only if you change any TM settings or variable lists).
    The message you are getting indicates that the SQL Server is timing out potentially due to the TM size or the load on your GS system.

    Are you launching the Re-Index process from within Studio or the GS website?
    Maybe try the GS Website, as that actually creates a Background Task and the server executes the reindexing in the background rather than actively when launched from Studio.

    If this doesn't help I would suggest contacting our Customer Support colleagues so that they can assist you more actively and have a look at the system.

    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |

Reply
  • 0
    Hi Jonathan,

    There is two different tasks "Recompute Fuzzy Index Statistics" which is very fast and should be straightforward.
    This actually happens automatically in the background since GroupShare 2015, so you don't need to run this manually.

    The "Re-index Translation Memory" is actually a much longer and heavy task and is rarely needed (usually only if you change any TM settings or variable lists).
    The message you are getting indicates that the SQL Server is timing out potentially due to the TM size or the load on your GS system.

    Are you launching the Re-Index process from within Studio or the GS website?
    Maybe try the GS Website, as that actually creates a Background Task and the server executes the reindexing in the background rather than actively when launched from Studio.

    If this doesn't help I would suggest contacting our Customer Support colleagues so that they can assist you more actively and have a look at the system.

    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |

Children