You are currently working on UAT 

  • State Verified Answer
  • Replies 4 replies
  • Subscribers 430 subscribers
  • Views 3332 views
  • Users 0 members are here
Options
Related

Error message: The specified URI is not a valid server-based translation memory URI. Parameter name: uri.

Chiara Mascardi

Hello, community! 

I've just opened a project package for translation in SDL Trados Studio 2017, and I've tried to set my parameters in Home > Project settings; but when I've clicked on Project settings, the error message "The specified URI is not a valid server-based translation memory URI. Parameter name: uri" was displayed.

If I click on ok, the error message disappears, I'm still on my Editor view and I can work on it, but without support from my TM, Termbase or other tools. I'm basically prevented from opening and editing my settings!

I know that this error message has already been filed by several translators in the community; the same error has already happened to me once recently, so I tried to follow some threads and perform some restoring actions. Unfortunately, neither renaming the folder "Plugin" in Studio, nor running a repair installation could solve the problem.

There's more: after running a second repair installation, my software crashed completely and stopped working.

I had to uninstall both Studio and Multiterm, and to reinstall them from scratch. 

Now that my Studio is working properly again, I would avoid repeating the above mentioned processes (they didn't help much!)... 

Does anybody have other suggestions or ideas? Could it depend on some errors in the project file, rather than on my software or some corrupted parts?

Thank you so much for your support (and apologies for this long, detailed explanation!)

Chiara
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hi

    If I click on ok, the error message disappears, I'm still on my Editor view and I can work on it, but without support from my TM, Termbase or other tools. I'm basically prevented from opening and editing my settings!

     

    After you hit ok the first time, you should check if you can access the settings by clicking on "Project Settings" again.
    You might be able to access it the second time.

    If you can access the settings, I recommend removing the TM and the re-adding it. If that doesn't work, remove the TM, then rename it and try again.

    Now, if you cannot access the project settings even after trying a couple times, you could try to manually remove it from the sdlproj file:
    1. Close Studio
    2. Open the sdlproj file in a text editor
    3. Search for the tag CascadeItem and remove everything from the start to the end tag*
    * If you make a mistake you can break the file, so I recommend making a back up!

    Could it depend on some errors in the project file, rather than on my software or some corrupted parts?

    This is a Studio bug, so your installation is not the problem. Studio cannot properly read the path name of the TM stored in the sdlproj file.
  • 0 in reply to Jesse Good
    Hi, Jesse!

    first of all, thank you for your solicitous answer (it's still Sunday afternoon, after all! :)

    I actually omitted to write that I had already tried to access the settings after clicking "ok" on the error message, and I did it several times - but I was always prevented from opening them (I've always got a new error message).

    As I understand, the problem should not be due to my own Studio program, but it's rather a general Studio bug.
    I also add that I've received the project package by a very trusted customer - if I understood it well, the problem lies on the incompatibility of my customer's TM (embedded in the incoming project) and my Studio, isn't it?
    (this only happens with this particular TM, by the way; I've never had problems with another of their TMs carrying a different language pair!).

    Is there anything that could be done to this problematic TM (by them, in case), in order for me to be able to read and use it too?
    If not, I could simply take the source sdl.xliff file, open it as a single file, and use it with my TMs, thus avoiding the risk of breaking the file.

    What do you think about it? Thank you again for your support, have a nice Sunday!!
  • 0 in reply to Chiara Mascardi
    Hi

    You could ask your customer to try renaming the TM, that might solve the problem.
    Since it only happens with a certain TM, most likely it is an incompatibility issue as you mention.

    Also, the workaround you suggested would be fine. When you open it as a single file you could try adding your customer's TM also.
Reply Children