Before I installed the TermExtractor (aka Sdl.Community.Excel.Terminology, which is confusing), Studio 2019 started alright (with about half a dozen other plugins installed). After I installed it, Studio gets stuck at Initializing Views and nothing more happens.
I also discovered that I could "uninstall" it by simply deleting it from the Unpacked and Packages folders in the SDL\SDL Trados Studio\Plugins folder. That is good to know.
But I would like to be able to use it.
I should add that after deleting the TermExtractor files as described, I also had to delete or rename the UserSettings, BaseSettings and Plugincache files in the 18.104.22.168 folder.
It seems the issue is NOT with TermExtractor. After having problems after adding this and that other plugin (either Initializing Views getting stuck or receiving the "'Sdl.Desktop.Platform.CommandBars.IActionService' could not be started" error -- mostly the latter), I tried deleting all plugins and then adding TermExtractor, and that worked fine.
So my problem is this: when I add a fair number of plugins, Studio cannot be started. It seems pointless to try to pinpoint any particular plugin, as this example shows. I do want to be able to add any number of plugins, but now I can't. Does anyone have a suggestion? (Repair doesn't work either.) I doubt re-installing Studio would help (others who get the IActionService error have tried, without success).
Hello @Mats Linder
It would seem that as when you remove the plugins and reinstall one by one everything is ok. But then when you get to X plugin, the problems arise.
This i think would suggest a conflict between X & Y plugin, so it would be helpful if you could let us know what plugins you have installed and then when the problems arise.
Actually, no. The first time, when I had about 6 plugins installed and then added TermExtractor, Studio got stuck so I removed TermExtractor and Studio worked. Then I added a few other plugins which resulted in the IActionService error. So I removed the last two added; still the same error. Then I gave up. It is not an attractive solution to try to add one plugin after another and open Studio after each one -- even if I could locate the problematic plugin, I still wouldn't know which one of the first 6 (or so) plugins that was involved in the conflict.
But I have another question. I deleted the Plugins folder and started anew, adding a few plugins without problems. However, now the Projects view is completely empty, something which did not happen before, regardless of whether I repaired Studio or deleted/renamed either the Plugins folder or the other three specific ones in the 22.214.171.124 folder. I find this mysterious.
I know the projects are there somewhere, in some folder, but I've forgotten where.
Hello @Mats Linder ,
This certainly sounds like very strange behavior-
First of all - please check that both the packages and unpacked folders are empty- e.g.
Next is the problem with your projects- I cannot see how an issue with the plugins can cause any issues whatsoever with your projects folder.
If they are no longer in your chosen folder (or the Studio default folder) then maybe try doing a Windows search-
Does this reveal their location?
I had deleted the whole Plugins folders, so the subfolders were certainly empty.
About the projects: This is what I find under user\Mats\Documents\Studio 2017\Projects:
projects.xml contains information about all projects that were previously listed (most of which are not placed here, which explains why there are so few project folders shown).
Is there somehow a broken connection between Studio and projects.xml?