TM problems after 6.2 server upgrade Persoa que publicou o fío: Kirsty Hamilton
|
|---|
Hello all,
One of the agencies that I work for regularly has recently upgraded from MemoQ Server 5 to Server 6.2., and I've been experiencing some problems since this upgrade. I'm not sure whether the problem lies with me or the agency, so I thought it would be worth asking here to see if anyone else has experienced this.
I have both MemoQ 5.0.67 and MemoQ 6.2.8 on my computer and have managed to work successfully on a version 6.2. project where I had never used any of ... See more Hello all,
One of the agencies that I work for regularly has recently upgraded from MemoQ Server 5 to Server 6.2., and I've been experiencing some problems since this upgrade. I'm not sure whether the problem lies with me or the agency, so I thought it would be worth asking here to see if anyone else has experienced this.
I have both MemoQ 5.0.67 and MemoQ 6.2.8 on my computer and have managed to work successfully on a version 6.2. project where I had never used any of the resources (TM, etc.) before. However, I seem to have problems whenever I've previously used a TM in version 5. I open the file in the project, click on 'pretranslate' and I get the message "You are not authenticated by the server yet.". The TM initially still had the old server URL next to it under "Project Home" > "Translation Memories", but I have managed to change the server URL on the toolbar at the top of the window, which then updated the list of TMs to show the new URL. All of the resources appear to now have the correct version 6.2 URL. And yet I still get the message "You are not authenticated by the server yet." when I try and pretranslate. I also see a 'lookup error' on the bar at the bottom of the window. When I hover my mouse over it, a message pops up saying "Translation memory lookup error. You are not authenticated by the server yet." and it shows the old, version 5 server URL. It looks as though my V6.2 MemoQ client SHOULD be accessing everything from the correct V6.2 server, and yet the lookup error suggests something is still trying to access the old server. I have no idea how to correct this and I'm not sure the agency does either.
I am also unable to save segments in the TM on the V6.2 server and see any matches in 'translation results' at the right-hand side of the screen unless I remove the server TM from the project and then add it again. The lookup error then disappears and I can save segments, matches appear in 'translation results' on the right and partial matches autopropagate as I move from segment to segment. And yet I still cannot pretranslate!
Has anyone experienced this before? It's very frustrating! If anyone can offer any help, I would very much appreciate it!
Thank you! ▲ Collapse
| | | | | Does ring a bell | Jan 31, 2013 |
I think this is quite similar to what happened to us when we decided to move our memoQ Server from one physical machine to another one. Our workstations kept trying to find the server in the old machine, because they had the old IP address recorded somewhere.
I reckon it could no harm to ask the customer whether they have a new physical machine or the IP address of the old machine has changed, even if the URL is the same. With that detail, contact Kilgray's support. They might be ab... See more I think this is quite similar to what happened to us when we decided to move our memoQ Server from one physical machine to another one. Our workstations kept trying to find the server in the old machine, because they had the old IP address recorded somewhere.
I reckon it could no harm to ask the customer whether they have a new physical machine or the IP address of the old machine has changed, even if the URL is the same. With that detail, contact Kilgray's support. They might be able to tell you how to fix this (could require some edit in the HOSTS file in your computer, or some other setting).
Would you mind to report the result here and what you did? It would be interesting to know. ▲ Collapse
| | | | Kirsty Hamilton
United Kingdom
Local time: 20:43
German to English
+ ...
INICIO DE TEMA | Sounds similar | Jan 31, 2013 |
Hi Tomas,
Thanks for that. Your problem sounds similar to mine. If you don't mind me asking, how did you resolve it?
To clarify, the agency is currently running both a V5 server and a V6.2 server for the time being, and the two servers have different IP addresses. It's the old IP address that appears as the URL in the lookup error.
| | | | | Another possibility | Jan 31, 2013 |
This is just very tentative, but just in case.
memoQ has an XML file which contains information about the server and location of the translation memories you use. The location depends on your operating system. It is called TranslationMemories.xml and in the case of Windows 7 it is located in C:\ProgramData\MemoQ\.
It is possible that the memory that's giving you trouble has wrong location data in this TranslationMemories.xml file. May I suggest that you:
1. Close ... See more This is just very tentative, but just in case.
memoQ has an XML file which contains information about the server and location of the translation memories you use. The location depends on your operating system. It is called TranslationMemories.xml and in the case of Windows 7 it is located in C:\ProgramData\MemoQ\.
It is possible that the memory that's giving you trouble has wrong location data in this TranslationMemories.xml file. May I suggest that you:
1. Close memoQ 6.2.
2. Temporarily rename this TranslationMemories.xml to something else, like zzTranslationMemories.xml, for instance.
3. Run memoQ, open the project, and work normally with your customer's project (might mean to do a new checkout of the project).
This will recreate a TranslationMemories.xml file with the now current information about the files on your customer's server. If this solves the problem, the old information in the XML file was probably the cause.
If that is the case, I would recover your old XML file, but would delete the block that refers to the memory that was giving you trouble:
1. Close memoQ 6.2.
2. Delete the newly created TranslationMemories.xml.
3. Copy your renamed zzTranslationMemories.xml (just to keep this one as a backup) and rename the copy with the old name, TranslationMemories.xml.
4. Open the XML file with an editor that will let you process text files (the Notepad for instance), find the name of the offending memory (you should find it between Name tags), and delete everything in its block which goes from tag "TMGlobalInfo" to "/TMGlobalInfo".
What this should do is that the data for this memory is recreated when you use it again in memoQ 6.2, while preserving the data of other memories you may use (either your own or from other customers using memoQ Server).
You might want to ask Kilgray before doing any of these things. In any case, if anything goes wrong, simply reuse your copy of the XML file you had at the very beginning and at least you will be in the situation you were before. ▲ Collapse
| | |
|
|
|
Carl Carter
Germany
Local time: 21:43
German to English
+ ...
| The answer may be in Kilgray's Knowledge Base | Jan 31, 2013 |
Hi Kirsty,
Perhaps this link to an article in Kilgray's new Knoweldge Base will help you: http://kb.kilgray.com/article/AA-00384
It's to do with servers being moved and translators' computers using old settings to try and gain access to them and employ the resources there (TMs, TBs, etc.), which won't work.
Regards
Carl
| | | | Kirsty Hamilton
United Kingdom
Local time: 20:43
German to English
+ ...
INICIO DE TEMA | Solution found! | Jan 31, 2013 |
Hi again Tomás,
Thank you for your advice. I didn't follow it completely, but you certainly pointed me in the right direction. I opened the TranslationMemories XML file and found the TM I've been having problems with. I noticed that the URL information was the IP address of the old server, so I changed it to the new one, reopened everything in MemoQ 6.2 and now I can pretranslate again! Thank you very much for your help!
| | | |
Kirsty Hamilton wrote:
Thank you for your advice. I didn't follow it completely, but you certainly pointed me in the right direction. I opened the TranslationMemories XML file and found the TM I've been having problems with. I noticed that the URL information was the IP address of the old server, so I changed it to the new one, reopened everything in MemoQ 6.2 and now I can pretranslate again! Thank you very much for your help!
That's great! Luckily many little things can be fixed by understanding these XML files a bit. I am glad this was useful!
| | | | Kirsty Hamilton
United Kingdom
Local time: 20:43
German to English
+ ...
INICIO DE TEMA | Thanks, Carl | Jan 31, 2013 |
Thank you, Carl. That article looks like exactly what I needed! At least I can now pass that on to the agency in case they have any more problems like this.
| | |
|
|
|
Kirsty Hamilton
United Kingdom
Local time: 20:43
German to English
+ ...
INICIO DE TEMA | Remember to make sure you can see hidden files | Feb 18, 2013 |
I just wanted to add that you probably have to make sure you can view hidden files in your system in order to find the folder where the XML file is saved. You should be able to find the instructions for your operating system quite easily on the Internet.
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » TM problems after 6.2 server upgrade | CafeTran Espresso | You've never met a CAT tool this clever!
Translate faster & easier, using a sophisticated CAT tool built by a translator / developer.
Accept jobs from clients who use Trados, MemoQ, Wordfast & major CAT tools.
Download and start using CafeTran Espresso -- for free
Buy now! » |
| | Wordfast Pro | Translation Memory Software for Any Platform
Exclusive discount for ProZ.com users!
Save over 13% when purchasing Wordfast Pro through ProZ.com. Wordfast is the world's #1 provider of platform-independent Translation Memory software. Consistently ranked the most user-friendly and highest value
Buy now! » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
