Hi Paul

I migrated over to a new PC today with installing Studio 2019 SR2 for the first time and all of a sudden this problem crops up on every single project, although the anti virus is set to not remove temporary windows files. However, when working on the projects in Studio 2017, I do not seem to encounter these problems. Any suggestions? Today was not too bad as we were talking smallish projects, but when the next big project with 100 files or so beckons, this will be a major issue. I have researched this online and so far no satisfactory solutions seem to exist. Thanks! for your suggestions

Alexandra

Alexandra Beisl

Does this happen with new projects you create or only existing projects?

You have 2017 and 2019 installed on the same new computer and the projects that won't open in 2019 will open in 2017?

Dear Paul

thanks for your message. I have both 2017 and 2019 installed on the new computer. On the old computer from which I migrated, I only had Studio 2017 and never came acerror.xlsxross this problem. Anti Virus is set up NOT to delete temporary windows files. I cannot say 100% if 2017 on the new computer would have behaved differently, as I only set up the project there new to see if it behaved and then quickly finished it (re-creating a problem between two different software versions is always tricky at the best of times, as all sorts of things could influence it in the background). But today I had a new issue in 2019 when running a verification report which I have never come across in 2017 (see file attached). Now correct me, if I am wrong: But isn't 2019 supposed to be more stable than 2017, especially 2019 SR2, which I am running? But so far it has only caused me problems, so I am tempted to switch back to 2017 entirely, which is not the idea really.

Thanks

Alexandra

Beside the anti-virus, do you use or have installed any optimization software? For example from the manufacturer of your PC? These tools tend to do the same - deleting content from tmp folder.

Issues with Studio on a fresh installed, clean new PC are likely caused by another software, interfering with Studio. This might be the anti virus, but also programs for PC optimization (which IMO do nothing but providing money to their vendors), not fully actualized drivers and so on. There can be so many reasons, that a diagnostic via forum is not possible. Also add-ons for Studio may cause problems.

Hi Jerzy

Not that I am aware of. What do you mean by Add Ons for Studio?

Thanks!

Alexandra

There are different plugins for Studio in Appstore of SDL. We've seen here a case, where a big number of installed plugins has caused problems with Studio.

As for the cleaning programs - if you have HP, Dell or any other brand, there might very well be a software running in the background you may not be aware of. In my case this is Dell Precision Optimizer. Luckily, this one does not delete anything. But nonetheless the same (dependancy not found) has happened to me some times now. I suppose it was due to a fast close of Studio, before it was able to store sometimes quite big files. In the end it was just a simple click on yes to recover the dependancy, so I did not care much about this error. Would this be the only one in your case, I would simply ignore it. If you have other problems, though, it would be good to get rid of these.

Jerzy Czopik said:

There are different plugins for Studio in Appstore of SDL. We've seen here a case, where a big number of installed plugins has caused problems with Studio.

Only really likely if you migrated plugins from 2017 by copying them into the plugin folder for 2019... not sensible.  You need to download the 2019 version and install again.  But this is unlikely to be responsible for a file not found error.  Problems in verification are more likely to be the result if settings in a specific plugin rather than the number you have installed.

I feel as though we're straying around issues now and not narrowing down the cause of one at a time.

The dependency file not found error seems to be due to the sdlxliff being created without embedding the sourcefile into it and now the only way to get at this file is by retrieving it from the Plunet server... which you probably don't have access to.

Jerzy Czopik said:

There are different plugins for Studio in Appstore of SDL. We've seen here a case, where a big number of installed plugins has caused problems with Studio.

Only really likely if you migrated plugins from 2017 by copying them into the plugin folder for 2019... not sensible.  You need to download the 2019 version and install again.  But this is unlikely to be responsible for a file not found error.  Problems in verification are more likely to be the result if settings in a specific plugin rather than the number you have installed.

I feel as though we're straying around issues now and not narrowing down the cause of one at a time.

The dependency file not found error seems to be due to the sdlxliff being created without embedding the sourcefile into it and now the only way to get at this file is by retrieving it from the Plunet server... which you probably don't have access to.

There are absolutely no Studio plugins on the new Laptop. Not sure why the source file won't be embedded on creating the Xliff  and not sure what the Plunet server would be. However, it seems any of those problems should crop up in 2017 as well, if they were product independent, which has, however, not been the case . Thanks!

Any source bigger than 20 MB won't be embedded. If the file has not been created by yourself, you can check, if the problem has already existed before you've started to work. In that case your Studio is not guilty at all.

To make sure the error has been there before you started, simply open the file in the folder with the source language, which should be in your package folder on your PC. Just use "single document" method. If the error appears, the error is caused by your customer. If the error does NOT appear, use File - Advanced Save - Save source as to get the source file. Then you can add the file to your translation file when the error pops up again.