• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 3213 views
  • Users 0 members are here
Options
Related

Sudden ITD pre-scanning error in Studio 2015 (both SR2 and SR3 tested)

Stephanos Siopoulos

Hello, I have been using Studio 2015 with ITD files for over a year now, successfully importing them and converting them to SDLXLIFF files using the project creation wizard.

All of a sudden, a few weeks ago, the following issue appeared, preventing me to work with ITD files since.
I tried repairing my installation to no avail, and I also installed SR3 thinking it would re-register any filters etc, again to no avail.

 

Btw, I'm using Win 10 (Creator's Update) which I'm suspecting is the culprit.
Has anyone else experienced this or similar error?

Thank you in advance for contributing to resolving this issue, as it's severely affecting my workflow.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Hi again.

    Any idea of what might be causing this?

    I checked the Windows registry and saw that one of the keys of the mentioned CLSID, points to the ItdApi20 DLL file, found in this path:

    However, I'm under the impression that the path Common\Files\SDL\SDLX2011 does not pertain to Studio but rather the SDLX "Lite" I have also installed on my PC. Btw, FYI never had I installed any other version of Trados or SDLX on this PC configuration.

    Can you please confirm whether the highlighted path belongs to SDLX Lite or to Studio 2015? If, as I suspect, the former is the case, then it would seem that for some reason Studio 2015 actually attempts to use SDLX Lite's filters to parse ITD files and so, understandably, fails (!)

    Incidentally, I tried to uninstall the SDLX Lite by using the only relevant entry in the Programs & Features list, only to encounter this very peculiar error:

    "You must uninstall SDLX before installing SDLX Lite" (!)

    This is crazy on two levels: first, I'm not trying to install SDLX Lite but actually to uninstall it and, second, to my knowledge SDLX (full) was never installed on my PC to begin with (!)

     

     

    So, given all the above additional info, I would really appreciate any ideas on what might be causing this whole mess and what can be done to restore proper ITD file parsing/conversion/import in Studio 2015 SR3.

    Thank you!
  • 0

    Hi  

    Extracted from the KB:

    If you have completely removed Trados 2007 before any new installation of SDL Trados Studio it should be installing by default the necessary components. 
    If you have completely removed Trados 2007 while SDL Trados Studio was already installed, it is required to install the SDL Trados Legacy Compatibility Module
    There are 2 options to proceed here:
     
    • Option 1:
      Run the SDL Trados Studio installer again. The installation process will be installing all missing components.
       
    • Option 2:
      Go to the following folder and install the SDL Trados Legacy Compatibility Module manually using the TradosCompatibility2.msi:
      • For Studio 2017: C:\ProgramData\Package Cache\SDL\SDLTradosStudio2017\modules
      • For Studio 2015: C:\ProgramData\Package Cache\SDL\SDLTradosStudio2015\modules

    See if this helps?

    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
    Hi Paul,
    Thank you for replying to my query!
    I had indeed checked this KB article before and installed the SDL Trados Legacy Compatibility Module, however this didn't solve the issue.
    Apparently, even installing SR3 on top of SR2 didn't make a difference, so I guess I'll have to try a full uninstallation and then installing everything from scratch. Let's see how that goes... :-\\
  • 0 in reply to Stephanos Siopoulos
    Hi Stephanos,

    ok - let me know if this improves. I guess we can't rule out Windows Creator. I have only seen someone test Studio 2017 with this build, did some testing and did have to work around a few things, but he got it running in the end I think.

    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

    Hi Stephanos and Paul,

    Yes, I did update to the so-called Creators Update and ran into a few minor problems, not only with Studio.

    After updating Windows to the Creators Update, Studio's automatic updates mechanism stop working and threw a couple of error messages (something I was able to reproduce on another computer). Deleting the updates folder and running a repair install (right click SDL Trados Studio 2015/2015 from the Programs and Features menu and select Repair) fixed that.

    I had also ran into an issue with Word (of all things) and a few other programs. Most of those issues were minor: an error occurred using a certain function or something simply didn't work.

    Repair installing/re-installing those programs did the trick.

    I'm not a fan of Windows' in-place upgrades. They are much better than in the past, but still not as reliable for a production environment as they should be. That said, it seems this is how Windows is going to get updated from now on, and re-installing the system after every new major update (disguised as an update) is probably an even more of a pain.

    Because those issues are more likely to be Windows related than Studio (or any other program, unless that program is no longer supported) related,  in a production environment I would suggest waiting with major Windows updates for at least 4-8 months.

    Another potential solution would be to remove the Creators Update, or restore a system image taken before the Creators Update was applied. The latter would be the safest option considering all that can go wrong and not necessarily gets undone rolling back Windows to a previous version, and therefore I recommend creating a system image before applying any major update just to be on the safe side. Windows' built-in tool is a good enough and easy solution for that.

    But other than those few annoyances, I didn't notice any other compatibility or stability issue.