Error message "The process cannot access the file 'WorldServer[temp file reference].ldb' because it is being used by another process" when opening a WorldServer (.wsxz) file in Studio 2022 Freelance.

I am using Trados Studio 2022 SR2 - 17.2.11.19134 and work with an agency that distributes project files through WorldServer.
As long as the WorldServer Package Converter plug-in is installed, this has always worked fine.
Maybe apart from the fact that a new plug-in version always trials behind a new Studio version, but that's a different matter.

Last week I downloaded a new package and wanted to open it in Studio, which resulted in this error:

Error message in Trados Studio: 'Preparing Package for Import... The process cannot access the file WorldServer_scrambled.ldb' because it is being used by another process.

Every time I try again, the 'scrambled' part of the file name changes, so it seems to be a temporary file that is being created for some reason.

This looked quite identical to this case: https://gateway.sdl.com/CommunityKnowledge?articleName=000001559 
And more in general to this one: https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/16861/the-process-cannot-access-the-file-because-it-is-being-used-by-another-process

The first issue suggest that the problem is caused at the WorldServer dispatch end, but the outsourcing agency has not changed anything on their end, and no other linguist has a similar problem with new project packages.

The second issue seemed to carry a potential solution, because the properties of the .wszx file indicated indeed that the file was downloaded and could be hazardous.
I removed that status from the file, but unfortunately that did not help.
To compare I tried to open older wszx files from previous projects. At the time I could open those without a problem in Studio, but now these give the same error message.

So, at the dispatch side, the process for creating and downloading WorldServer packages has not changed.
And on the receiving end, my local Studio instance has not changed either.
But whereas about two weeks ago I was able to open a wszx package just fine, today Studio throws this error.

Looking back, the only thing that changed in the 'supply chain', was the fact that I installed a new Windows version (Windows 11, version 24H2)
That seems to be too much of a coincidence to to be at least part of the problem, but I would not know where to start or what to look for.

The actual package does not seem to be the source, since older packages give the same result. 
It seems to be this temporary .ldb file, but I don't know what the location/path is, and whether this is on my local environment, or the WorldServer cloud environment?
I'm not sure if this is relevant, but I am using OneDrive as well.

I do have a workaround by asking the agency to supply me with 'standard' (sdlppx) packages, and that works.
But the WorldServer is a much smoother and faster proces (if it works), and I would very much like to get that working again.

Any help, suggestions, advice or other forms of compassion would greatly be appreciated.



Generated Image Alt-Text
[edited by: RWS Community AI at 2:27 PM (GMT 0) on 19 Dec 2024]
emoji
Parents Reply Children
No Data