• State Verified Answer
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 434 subscribers
  • Views 5182 views
  • Users 0 members are here
Options
Related

Studio 2017 AutoSuggest candidates not displayed

MMM

Issue may be related to inability to add or generate AutoSuggest dictionaries.

(Attempting to add a dictionary gives error message "The AutoSuggest dictionary file could not be read," and trying to generate one fails after extracting phrases, with message "unable to open database file," details attached (hopefully).) AutoSuggest dictionaries are one of my selected AutoSuggest providers, but after excluding them, still no display of any candidates from other providers.


All settings in Studio 2017 are identical to those in Studio 2015, where everything works fine. Tried repairing the installation, reinstalling, and restarting. Looking forward to seeing AutoSuggest candidates when I start typing, but so far, nothing at all. Any help would be appreciated. Thank you. P.S. Looking forward to Regex Match Autosuggest Provider for 2017.

Fullscreen sdlerror-20161118-11h46m21s.sdlerror.xml Download 
<SDLErrorDetails time="11/18/2016 11:46:33 AM">
  <ErrorMessage>unable to open database file</ErrorMessage>
  <Exception>
    <Type>System.Data.SQLite.SQLiteException, System.Data.SQLite, Version=1.0.103.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139</Type>
    <ResultCode>CantOpen</ResultCode>
    <ErrorCode>14</ErrorCode>
    <HelpLink />
    <Source>System.Data.SQLite</Source>
    <HResult>-2147467259</HResult>
    <StackTrace><![CDATA[   at System.Data.SQLite.SQLite3.Open(String strFilename, String vfsName, SQLiteConnectionFlags connectionFlags, SQLiteOpenFlagsEnum openFlags, Int32 maxPoolSize, Boolean usePool)
   at System.Data.SQLite.SQLiteConnection.Open()
   at Sdl.LanguagePlatform.TranslationMemoryTools.PhraseExtraction.DatabaseConverter.CreateBiligualPhraseFile(String path)
   at Sdl.LanguagePlatform.TranslationMemoryTools.PhraseExtraction.DatabaseConverter.Convert(String flatFilePath, String dbFilePath)
   at Sdl.LanguagePlatform.TranslationMemoryTools.PhraseExtraction.PhraseExtractionProcessor.CreatePhraseDb(DataLocation location, String dbFilePath)
   at Sdl.LanguagePlatform.TranslationMemoryTools.PhraseExtraction.PhraseExtractionProcessor.Process(String tmxFilePath, CultureInfo sourceCulture, CultureInfo targetCulture, Int32 maxIterationCount, Int32 maxTUs, String dbFilePath)
   at Sdl.TranslationStudio.Common.Jobs.PhraseExtractionJobRequest.Execute(IJobExecutionContext context)
   at Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__3()
   at Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
   at Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>14.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>14.0.5746.0</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1041</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>TEN\MMM</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>TEN</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8388132 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Just a few final follow-up comments for posterity, and I will abandon this solo thread.
    - Some AutoSuggest candidates are now displayed for me. (I double-checked this setting and used a viable segment for testing: AutoSuggest > Translation Memory and Automated Translation > Minimum suggestion length... + Minimum number of characters...) However, not as many candidates as usual, probably because my AS dictionaries cannot be loaded. (See below.)
    - I still think there might be an AutoSuggest dictionary bug in Studio 2017, at least for me, because the error message "The AutoSuggest dictionary file could not be read" is always displayed when I attempt to add any of my regular dictionaries. Another chronic error message is "unable to open database file" (see 1st msg above).
    - Cannot insert recognized terms with registered keyboard shortcuts.
    I suppose the issues will eventually be resolved. Thanks to the developers, anyway.
  • 0 in reply to MMM
    Hi MMM,

    Maybe check your dictionary is the same flavour as your project languages? The AutoSuggest Dictionaries have to match exactly, so en(US) cannot be used for en(GB) for example.

    Did you try and use project templates from an older version of Studio? Never a good idea to do this, always better to recreate them from scratch.

    Based on your shortcut problems maybe try a reset as well... no specific reason for suggesting this other than it cures a number of ills. Rename this folder (just add _old to the end or something, it's not important what you rename it to) and restart Studio:

    c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\14.0.0.0

    Regards

    Paul

    Paul Filkin | 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

  • 0 in reply to Paul
    Update: Unusual (network) file paths apparently not supported for AutoSuggest Dictionaries (when adding existing ones, or as destinations for new ones that are generated)

    Thank you, Paul, for your sensible suggestions. Good advice about not using older project templates. FYI, I had already tried various troubleshooting and upgrading techniques with the Roaming and Local folders.

    There seems to be a bug, at least for me, in the file paths of AutoSuggest dictionaries that are supported.
    For Parallels users (for example), these dictionaries cannot have file paths such as \\Mac\Lorem\Ipsum\Ω Dolor\Sit.... (Personally, I use an omega character for sorting in macOS, but the \\Mac at the beginning instead of C:\Users\ might give Studio 2017 problems.)
    This apparent bug causes the initial error message of "Unable to open database file" for me. Using a local file path with C:\Users\ solves it.
    Thanks again. Very much looking forward to using Studio 2017, now that I seem to be on the right track.
Reply
  • 0 in reply to Paul
    Update: Unusual (network) file paths apparently not supported for AutoSuggest Dictionaries (when adding existing ones, or as destinations for new ones that are generated)

    Thank you, Paul, for your sensible suggestions. Good advice about not using older project templates. FYI, I had already tried various troubleshooting and upgrading techniques with the Roaming and Local folders.

    There seems to be a bug, at least for me, in the file paths of AutoSuggest dictionaries that are supported.
    For Parallels users (for example), these dictionaries cannot have file paths such as \\Mac\Lorem\Ipsum\Ω Dolor\Sit.... (Personally, I use an omega character for sorting in macOS, but the \\Mac at the beginning instead of C:\Users\ might give Studio 2017 problems.)
    This apparent bug causes the initial error message of "Unable to open database file" for me. Using a local file path with C:\Users\ solves it.
    Thanks again. Very much looking forward to using Studio 2017, now that I seem to be on the right track.
Children
No Data