My company has been using this app for the last year and a half and it's really a timesaver. We have a Professional Network licence for both Studio 2017 and 2019 and the app is installed in both of the versions of the programmes. We've had no issues (except the occasional "Service not working" which we were able to reslove) so far.
A couple of days ago, we've updated the 2017 version to CU15 (we were behind on the updates), the 2019 version to SR2 and also installed MultiTerm for both versions. Then we installed the 3.12.1 version of SDL Analyse as it is compatible with SR2. However, after starting up the app for the first time after the updates, the issue "No project templates are defined" appeared.
Our IT company tried to reinstall the app, made sure we have no old Studio versions left over, tried the solution in this thread (https://community.sdl.com/product-groups/translationproductivity/f/openexchange_applications/10998/sdl-analyse---no-project-templates-are-defined) and made sure we have folder c:\Users\[USERNAME]\AppData\Roaming\SDL\ProjectApi with the Sdl.ProjectApi.xml file (pointing to the correct LocalDataFolder location) there for every user, all to no avail. What is more, the appearance of the "No project templates are defined" error is that much stranger since we do not actually use project templates ...
This thread (https://community.sdl.com/product-groups/translationproductivity/f/openexchange_applications/13941/sdl-analyse---no-project-templates-are-defined-project-templates-on-a-server) seems promising but offers no solutions. :) Would anyone be able to help me out?
Looks to me like a consequence of some weird screwup in the ProjectApi folder number in Studio 2019 SR1 and newer:
I'm waiting for an explanation from SDL side too.
Hi Jure Velikonja, we tackled a similar issue a few weeks ago here that might help you resolve this issue after upgrading to SR2
thank you for the link! I have checked that thread during initial troubleshooting and followed the solve, i.e. made sure we have folder c:\Users\[USERNAME]\AppData\Roaming\SDL\ProjectApi\184.108.40.206. with the Sdl.ProjectApi.xml file (pointing to the correct LocalDataFolder location) there for every user. That did not help, unfortunately, as SDL Analyse still reports "No project templates defined".
What boggles me is that we have never used any project templates, so I am really not sure what is causing the problems.
Patrick Andrew Hartnett, can you perhaps think of any other solve we could try?
On a machine where I installed Studio 2019 SR2 directly, i.e. without any previous Studio 2019 installed, I have a folder 220.127.116.11 only...
So, try to rename that 18.104.22.168 folder to 22.214.171.124 and see if it helps.
My wild guess is that there is some screwup in the folder numbering on SDL side... just as I mentioned in the thread in Developers forum.There were NEVER any minor numbers changed in these folders in the previous Studio versions, no matter if SR1, SR2 or even SR3 were released... and things simply worked so far. And now this...
thank you for the suggestion! I tried that during initial troubleshooting: I only had folders 126.96.36.199 and 188.8.131.52, so I added folder 184.108.40.206 and copied Sdl.ProjectApi.xml into it. This unfortunately did not solve the issue.
Hi Jure Velikonja, SDL Analyze is looking for the project server file (e.g. projects.xml) which should be found in the path (root) defined in the Sdl.ProjectApi.xml from the attribute value for LocalDataFolder
<?xml version="1.0"?><Application xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xmlns:xsd="">www.w3.org/.../XMLSchema" Version="220.127.116.11"> <LocalProjectServers> <LocalProjectServerInfo LocalDataFolder="C:\Users\UserID\Documents\Studio 2019\Projects" UserId="GLOBAL\UserID" /> </LocalProjectServers></Application>
Note: in this case, there should exist a file called projects.xml in the folder: C:\Users\UserID\Documents\Studio 2019\Projects\
Patrick Andrew Hartnett said:SDL Analyze is looking for the project server file (e.g. projects.xml) which should be found in the path (root) defined in the Sdl.ProjectApi.xml from the attribute value for LocalDataFolder
Aaaaha! So SDL Analyze is in exactly the same trouble as I am: https://community.sdl.com/developers-more/developers/language-developers/f/sdk_qa/27004/how-to-get-programmatically-the-number-of-appdata-roaming-sdl-projectapi-folder
So I'm wondering when someone from SDL responsible for this is going to explain what's going on.
Hi Patrick Andrew Hartnett,
thank you for the quick reply. I checked what you suggested and:
It seems that all is in order in this respect.
Do you think that the fact that we are runnings Trados Studio (and consequently SDL Analyse) on a server and the users are using/runnin it via RDS might have something to do with the issues?
Hi Jure Velikonja,
Yes, it has been previously noted that this specific scenario can cause problems in loading SDL Analyse remotely on a server, although I have not been able to confirm or test this effectively, as I don’t have access to setting up that type of workshop.
At this point, It is unclear to me if this is an issue related to identifying the project server that corresponds to the studio projects folder or more related to insufficient access rights in running the self-hosted web service that is required as a mediator in automating these processes through the plugin itself.
I would recommend first identifying which one of these is the root cause and then take it from there.