Erik

Please upgrade Studio to the latest CU5 and see whether this helps (you are not on the latest 2019).  You should see the small orange notification in the top right.  If you still get this error after that try a reset:

Rename this folder (just add _old to the end or something, it's not important what you rename it to) and restart Studio:

c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0

So the path would become this:

c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0_old

If you can't find this folder then you need to unhide your hidden files/folders:

www.howtogeek.com/.../

Hi Paul – Thanks for the tips. I'm currently on 15.2.0.1041, and when I check for an update, none is offered. 1041 is the latest available via the download section of My SDL as well.  I'll try the reset tip next and update you shortly.

I'm going to reboot again and see if the update client detects the newer version.

SDL Trados Studio 2019 SR2 - 15.2.5.2145

If you can't see it you can manually take it from here:

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0027380

Scroll to the bottom for the FTP details.

For MultiTerm...

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0027380

You should update this too.

OK, rebooting seems to have worked to get the apps to detect the updates. I've updated both Studio and Multiterm. Now, when I press the "New Project" button, I get this error and cannot actually even start a new project:

Here's the error XML:

/cfs-file/__key/communityserver-discussions-components-files/90/sdlerror_2D00_20191218_2D00_14h53m37s.sdlerror.xml

Erik

Did you try the reset?

Also... it might be worth deleting your default project template as this may be the cause of this error:

c:\Users\[USERNAME]\Documents\Studio 2019\Project Templates\Default.sdltpl

But if that doesn't help please log a support case.  

gateway.sdl.com/liveagentlicensing

You have two options:

1. Submit a case using a webform
2. Use live chat to get a licence reset

You want to use the first option and make sure that you refer to this thread so the teams can see what you have tried already.

I get this error even after renaming the 15.0.0.0 file to 15.0.0.0_old and doing the initial setup again.

Thank again for your detailed and ongoing help! I'll try a new project template next.

Hi Paul – It looks like nixing the default template did the trick. I'm going to try to use it on a client project coming in tomorrow, and I'll post again here and flag that as the answer if all goes well. Thanks again for your help!!

Just following up that replacing the default template actually worked, which is easy enough to set back up. Thanks again, Paul, for your quick and knowledgeable help!

Just following up that replacing the default template actually worked, which is easy enough to set back up. Thanks again, Paul, for your quick and knowledgeable help!