Hello!
I'm running SDL Trados Studio 2015 - 12.0.4961.2 and downloading packages from WorldServer 10.4.3.195 in Windows 10, I get the following error message when I try to open the packages in Studio: "The process cannot access the file Worldserver.ldb because it is being used by another process".
I have tried repairing the WorldServer Components installation, but it did not solve the issue. Studio claims everything is up to date.
Is there any solution to this issue?
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
Hi Tove,
I have two suggested answers that came from the support team for this. Please make sure you keep a copy of the original package before you do this.
ROOT CAUSE
Attributes with different "Internal (API) Name" but same "External (UI) Name" are created for TD Entry and TD Term on WorldServer side.
RESOLUTION
1. Change the WorldServer package file extension from *.wsxz to *.zip.
2. Extract the file.
3. Open xcs.xml file on any text editor.
4. Find the element 'TD_Entry_Note' and 'TD_Term_Note', you will see the value of their dataCatId is the same "Note".
5. Change a value of the above elements' attribute 'dataCatId' to any different name.
6. Save and close the file.
7. Compress all of the extracted files to a zip file.
8. Change the zip file name extension to *.wsxz.
9. Open it in Studio.
Please note that you might need to do the above steps to revert those two elements' dataCatId value back to original state in order to upload the return package back to WorldServer(that means both of two value for 'dataCatId' should be "Note").
IMPORTANT: The element and the dataCatId might differ from the above description.
To prevent this issue to happen, you should set different “External (UI) Name” and “Internal (UI) Name” for TD Entry and TD Term, then create a new project or re-export the same project to a new WSXZ Package. If you are unsure which TD Entry and TD Term are causing the issue, you'll need to send us an export of all TD Entry and TD Term Attributes so we can review them to find the ones with the same name.
This one is really aimed at Studio 2014 and 2011 in conjunction with WorldServer 10.1, 10.2, 10.3 and 10.4 but it's worth considering I think if the first solution doesn't help.
ROOT CAUSE
SDL Trados Studio does not support the conversion of the Termbase TBX file included in the Studio package exported from WorldServer if the language code is "x-es-XL" for Spanish (Latin America)
RESOLUTION
1- Rename the *.WSXZ Studio package to *.ZIP and extract it to a folder using Winzip or Winrar
2- Open the extracted folder and open the "terminology_data.tbx" in a XML Editor or in Notepad
3- Search for "x-es-XL" and replace it with a recognizable language code format, for instance "es-ES"
4- Save your changes and close the file
5- Repeat steps #2 to #4 for file xcs.xml
6- Select all files in the folder and compress them to a ZIP file
7- Rename the ZIP file to *.wsxz and open it as a package in Studio. The package will open up correctly.
8- Open the project file in the Studio project and translate as usual. You might get an alert related to "culture name" while opening the file. You can ignore it. The translation can still be done without error and the TM and Termbase are recognized just fine.
Here is a small video showing the troubleshooting procedure:
Support created a small Video file showing you the procedure step-by-step. You can download it from here.
.
Perhaps one of these is going to help. If not we'll log a case for you so a support engineer can take a look at your package.
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
Hi Tove,
I have two suggested answers that came from the support team for this. Please make sure you keep a copy of the original package before you do this.
ROOT CAUSE
Attributes with different "Internal (API) Name" but same "External (UI) Name" are created for TD Entry and TD Term on WorldServer side.
RESOLUTION
1. Change the WorldServer package file extension from *.wsxz to *.zip.
2. Extract the file.
3. Open xcs.xml file on any text editor.
4. Find the element 'TD_Entry_Note' and 'TD_Term_Note', you will see the value of their dataCatId is the same "Note".
5. Change a value of the above elements' attribute 'dataCatId' to any different name.
6. Save and close the file.
7. Compress all of the extracted files to a zip file.
8. Change the zip file name extension to *.wsxz.
9. Open it in Studio.
Please note that you might need to do the above steps to revert those two elements' dataCatId value back to original state in order to upload the return package back to WorldServer(that means both of two value for 'dataCatId' should be "Note").
IMPORTANT: The element and the dataCatId might differ from the above description.
To prevent this issue to happen, you should set different “External (UI) Name” and “Internal (UI) Name” for TD Entry and TD Term, then create a new project or re-export the same project to a new WSXZ Package. If you are unsure which TD Entry and TD Term are causing the issue, you'll need to send us an export of all TD Entry and TD Term Attributes so we can review them to find the ones with the same name.
This one is really aimed at Studio 2014 and 2011 in conjunction with WorldServer 10.1, 10.2, 10.3 and 10.4 but it's worth considering I think if the first solution doesn't help.
ROOT CAUSE
SDL Trados Studio does not support the conversion of the Termbase TBX file included in the Studio package exported from WorldServer if the language code is "x-es-XL" for Spanish (Latin America)
RESOLUTION
1- Rename the *.WSXZ Studio package to *.ZIP and extract it to a folder using Winzip or Winrar
2- Open the extracted folder and open the "terminology_data.tbx" in a XML Editor or in Notepad
3- Search for "x-es-XL" and replace it with a recognizable language code format, for instance "es-ES"
4- Save your changes and close the file
5- Repeat steps #2 to #4 for file xcs.xml
6- Select all files in the folder and compress them to a ZIP file
7- Rename the ZIP file to *.wsxz and open it as a package in Studio. The package will open up correctly.
8- Open the project file in the Studio project and translate as usual. You might get an alert related to "culture name" while opening the file. You can ignore it. The translation can still be done without error and the TM and Termbase are recognized just fine.
Here is a small video showing the troubleshooting procedure:
Support created a small Video file showing you the procedure step-by-step. You can download it from here.
.
Perhaps one of these is going to help. If not we'll log a case for you so a support engineer can take a look at your package.
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
Translate
