Pages in topic: [1 2] > | Here we go again: SDL Trados Studio project failed to load Thread poster: Marinus Vesseur
|
This day was bound to come, wasn't it: SDL Studio will not open my current 8000 Euro project. Error message: "Failed to load project from... there is an error in XML document ...". Not an error of mine, Windows, or the power grid. A built-in SDL Studio error! It made an error in ONE XML file and now the ENTIRE half-finished 80.000 word project cannot be opened. There is no alternative, there is no backup, there is no safety net. For years users have been complaining that the one big SDL policy error is their total disregard for data safety. Trados up until Studio too easily messed things up and your TM could be irretrievably lost just like that (which is still the case with any version of Trados, by the way, so if you haven't switched to Studio: backup, backup, backup your TMs). It would have been so simple to add an integrated backup solution (see the competition), but the program designers just couldn't be bothered. Studio is supposed to be different. This time they took the over-the-top, convoluted approach: a jungle of non-editable Project and Main Memories that are somewhere hidden on your hard disk, but where? Still, that wouldn't be so bad, if it worked RELIABLY. Today I found out that the system isn't even close to foolproof. One little error in an XML file, it could happen any time, out of the blue and through nobody's doing and your project is toast! Okay, not entirely toast. Looking through the posts on the subject in this forum I see that this has happened to some of my colleagues before. Which is reassuring, especially because they are computer geeks, so they found a workaround. Thanks, guys! Even so, how much geekdom is required to be an SDL Studio user? Will several years of technical studies do, or is a degree in software engineering a requirement? Wake up, SDL! You are selling this hypersensitive tool suite at a profit to thousands of not-so-computer-savvy translators. Shouldn't it be designed to keep THEIR needs in mind? Until that happens: SDL Studio NOT recommended for anyone below the level of computer expert! | | | Jerzy Czopik Germany Local time: 13:54 Member (2003) Polish to German + ... Well, there is at least one alternative | Aug 7, 2010 |
I assume you know where your project is stored on your HDD. In the situation you show click OK. Right click the project and select "Remove from list". Close Studio. Locate the "projects.xml" file, which is typically located in "My documents", Projects folder within the SDL Trados Studio. Open it with any text editor. Check, if there is no track of the project you deleted. Go to the folder where your project is located and double click the project file. This will start Stu... See more I assume you know where your project is stored on your HDD. In the situation you show click OK. Right click the project and select "Remove from list". Close Studio. Locate the "projects.xml" file, which is typically located in "My documents", Projects folder within the SDL Trados Studio. Open it with any text editor. Check, if there is no track of the project you deleted. Go to the folder where your project is located and double click the project file. This will start Studio and load the project. You file should open now. As for this statement: a jungle of non-editable Project and Main Memories that are somewhere hidden on your hard disk, but where? - I must admit I assume it is a joke. All those files are located exactly where you put them. Project TMs are always within the project folder, project files are editable and there is no jungle, but a clear structure. And all this structure is quite easy to maintain, if you ask me. When creating a project: place source files in a desired location. Create a new project. Give it a name. The destination folder of this project will get the same name - you can now adapt the path, where the project has to be located. Create the project, add files and change to the project folder. Explore it contents - you will see a directory for source files, for target files, for file settings, for project TMs (if any) and maybe for termbases and main TMs (for example, if you've got this project from a PM). ▲ Collapse | | | Marinus Vesseur Canada Local time: 05:54 English to Dutch + ... TOPIC STARTER Projects.XML wasn't the culprit this time | Aug 7, 2010 |
Thanks, Jerzy. If only SDL products were as reliable as you are. Regrettably it doesn't work. The "Projects.XML" solution didn't do it, I'm afraid. Here's what happens if I try what you suggested: "The selected project could not be opened". The entire error message looks like this: Now what? I wrote the SDL support guys, but they're out of the office for the weekend. | | | Jerzy Czopik Germany Local time: 13:54 Member (2003) Polish to German + ... Recreate the project in another folder | Aug 7, 2010 |
First make a backup of the whole project folder. Now recreate the project with an untranslated original source file in another folder. Copy the SDLXLIFF file from the old project to the new one. Try to open it for translation - if you succeed, close the file again. Use the batch task "Update project translation memory" to get the already translated parts of the file into your project TM. Now reopen the file and translate further. Otherwise you can also try to open the pro... See more First make a backup of the whole project folder. Now recreate the project with an untranslated original source file in another folder. Copy the SDLXLIFF file from the old project to the new one. Try to open it for translation - if you succeed, close the file again. Use the batch task "Update project translation memory" to get the already translated parts of the file into your project TM. Now reopen the file and translate further. Otherwise you can also try to open the project TM from the old folder, export it, import to main TM and retranslate the file from TM - or use directly the PTM from the old project. However you proceed - do not loose temper, I hope you'll get the project running again BTW, if I were in your shoes I would edit the picture above and make the name of your customer illegible there.
[Edited at 2010-08-07 21:34 GMT] ▲ Collapse | |
|
|
Try deleting the projects.xml | Aug 7, 2010 |
Marinus Vesseur wrote: Regrettably it doesn't work. The "Projects.XML" solution didn't do it, I'm afraid. I wrote the SDL support guys, but they're out of the office for the weekend. Hi Marinus, Jerzy's solution to create a new Project will work, but maybe you could try closing Studio and then deleting the projects.xml file altogether. Then restart Studio and use Open Project to manually recreate the projects that were in your list. If that doesn't work try deleting the following files in C:\Documents and Settings\<username>\Application Data\SDL\SDL Trados Studio\9.1.0.0 and restart. If you are using Vista it will be C:\Users\<username>\AppData\Roaming\SDL\SDL Trados Studio\9.1.0.0\. BaseSettings.xml plugincache.xml UserSettings.xml They will be recreated and this often cures a number of problems with corrupted settings files. Regards Paul
[Edited at 2010-08-07 22:57 GMT] | | | Marinus Vesseur Canada Local time: 05:54 English to Dutch + ... TOPIC STARTER
Hey, not completely out of the office, it seems. Thanks for your help. This must be a tougher case, because I tried all the below suggestions, step by step and one at a time, but none of it worked. I still hesitate with Jerzys massive approach, go through a long, risky process that might destroy my files. No offence. Think I'll start backing up my files. SDL Support wrote: .. maybe you could try closing Studio and then deleting the projects.xml file altogether. Then restart Studio and use Open Project to manually recreate the projects that were in your list. If that doesn't work try deleting the following files in C:\Documents and Settings\\Application Data\SDL\SDL Trados Studio\9.1.0.0 and restart. If you are using Vista it will be C:\Users\\AppData\Roaming\SDL\SDL Trados Studio\9.1.0.0\. BaseSettings.xml plugincache.xml UserSettings.xml They will be recreated and this often cures a number of problems with corrupted settings files. Regards Paul
[Edited at 2010-08-07 22:57 GMT] | | | Jerzy Czopik Germany Local time: 13:54 Member (2003) Polish to German + ... If you use copies of the files, nothing will be destroyed | Aug 8, 2010 |
So instead sitting there and waiting for a wonder just copy the relevant files to a new directory and apply my solution. | | | Walter Blaser Switzerland Local time: 13:54 French to German + ... For some reason your project file got corrupted | Aug 8, 2010 |
Marinus Looking at the error message screenshot you included, it looks as if Studio is not able to load your project because the project definition file contains some out of sync information. Did you create the project yourself or did it come in a package? Finding out exactly what has gone wrong will take some time, however there is a workaround and it has already been suggested to you: create a new project and work on that one. Keep in mind that as long a... See more Marinus Looking at the error message screenshot you included, it looks as if Studio is not able to load your project because the project definition file contains some out of sync information. Did you create the project yourself or did it come in a package? Finding out exactly what has gone wrong will take some time, however there is a workaround and it has already been suggested to you: create a new project and work on that one. Keep in mind that as long as you do not delete manually any of the project files, nothing gets lost - contrary to what you try to suggest in your emotional complaints about the poor quality of the software. You can easily create a new project using the files that are still in your project folder (both source and target in original as well as in bilingual (SDLXLIFF) format) and then go on working on this one without losing anything. Walter ▲ Collapse | |
|
|
Finding why... | Aug 8, 2010 |
Walter Blaser wrote: Finding out exactly what has gone wrong will take some time, Finding out what seems easy. The project file is corrupt at the line 15861, column 26. Open the file in a decent text editor, kinda Notepad++ or similar, then use Go to line feauture. Finding out why seems more complex. As far as I see, this kind of error occurs usually when the project files gets truncated because od some Studio internal error. If it's truncated, no luck at all, the only sound way is to recreate the project. If it's an XML structure error, you can always try to repare the file manually but it needs a lot of experience. Cheers GG | | | Marinus Vesseur Canada Local time: 05:54 English to Dutch + ... TOPIC STARTER Guid format corrupted. Fixed it. Problem solved! | Aug 9, 2010 |
Thanks for the tip, Grzegorz. I renamed a copy of the project file (sdlproj) into the same file name, but with an xml suffix. Then I opened it in Notepad++ (free download). Line 15861 looks like this: As even I can see this part looks totally wrong: FileVersion Guid="edb56bc2-9b28-48b2-9c2ENLAPTOP\RIEN LAPTOP" The first error message I had, referred to exactly this Guid format being wrong. I could change it, but into what? If I knew that we'd have a simple fix. I decided to dump the entire section (about five lines) and fix the end of the xml file, where some end tags appeared to be missing. Did that, converted back to sdlproj, opened it in Studio... similar error, this time another line in the project file. Lather, rinse, repeat. After five or six times it worked! Eureka! I did it! Euphoria ensued. Thanks to your tips and some trial and error (with COPIES of the project files) everything is back to normal and I haven't lost client data, basic settings, project settings, program settings, global settings, project TMs, main TMs, temporary files (okay, maybe some of them), MT's, autosuggestive dictionaries and other paraphernalia that appear to be the normal bread-and-butter of the contemporary translator (cynical smirk). But seriously: I can only hope this doesn't happen all too often. Keep your fingers crossed and backup. Grzegorz Gryc wrote: Finding out what seems easy. The project file is corrupt at the line 15861, column 26. Open the file in a decent text editor, kinda Notepad++ or similar, then use Go to line feauture. Cheers GG
[Edited at 2010-08-09 06:17 GMT]
[Edited at 2010-08-09 19:14 GMT] | | | GUID... buffer overflow... | Aug 9, 2010 |
Marinus Vesseur wrote: As even I can see this part looks totally wrong: FileVersion Guid="edb56bc2-9b28-48b2-9c2ENLAPTOP\RIEN LAPTOP" The first error message I had referred to exactly this Guid format being wrong. I could change it, but into what? See if a similiar GUID is present somewhere in the file. If yes, use it. If I knew that we'd have a simple fix. By the way: the project consists of more than 400 smallish TTX files. If I lose the last one, no harm done. I would delete the entire LanguageFile section where the FileVersion parameter is nested. Just guessing. I never analyzed SDLXLIFF files thoroughly. Make a backup before you start to cut off entire sections BTW. Now, we know why it happened. It seems it's a buffer overflow somewhere in the software. Cheers GG
[Edited at 2010-08-09 19:36 GMT] | | | Marinus Vesseur Canada Local time: 05:54 English to Dutch + ... TOPIC STARTER Buffer overflow | Aug 9, 2010 |
Grzegorz Gryc wrote: See if a similiar GUID is present somewhere in the file. If yes, use it. If I only knew what that is. I would delete the entire LanguageFile section where the FileVersion parameter is nested.
That is, more or less, what I did, plus a few corrections at the end of the file and it worked. BTW. Now, we know why it happened. It seems it's a buffer overflow somewhere in the software.
Ah, a buffer overflow. Me 'n the boys would have buffer overflows at the weekends, but the doctor told me to stop. Bad for the liver, he said. Thanks for your help, G. | |
|
|
Paolo Troiani Italy Local time: 13:54 Member (2010) English to Italian + ... Same to me... | Nov 22, 2011 |
Sorry to jump in that late, but I had same problem this morning. >100'000 project corrupted, following error message: "Failed to activate project "project name". Failed to load project "project path". Errore nel documento XML (189,81). Rappresentazione formale di stringa non chiusa. Riga 189, posizione 81. I have already deleted project.xml (made a backup copy on desktop). Closed Studio, located project to be opened and clicked on that. ... See more Sorry to jump in that late, but I had same problem this morning. >100'000 project corrupted, following error message: "Failed to activate project "project name". Failed to load project "project path". Errore nel documento XML (189,81). Rappresentazione formale di stringa non chiusa. Riga 189, posizione 81. I have already deleted project.xml (made a backup copy on desktop). Closed Studio, located project to be opened and clicked on that. Now error message is "the selected project could not be opened" Help please..we are talking about 100'000 word excel file!! ▲ Collapse | | | Paolo Troiani Italy Local time: 13:54 Member (2010) English to Italian + ... Workaround found!! | Nov 24, 2011 |
I had to recreate a project, attaching to it the SDLXLIFF file, the TM and the Termbase. Everything is fine so far, but still, it is a simply unacceptable bug.
[Edited at 2011-11-24 19:16 GMT] | | | same error - Studio 2011 fails to open ANY projects, can't load project list | Oct 17, 2012 |
Today I encountered the same problem as described here, but it is a little more difficult. Studio doesn't load the project list properly. When I ask to show all projects it only show projects finished 6 months ago or earlier. I tried to open other projects than the one with the error message but this also fails - so now what??? thanks in advance for any suggestions br lise | | | Pages in topic: [1 2] > | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Here we go again: SDL Trados Studio project failed to load Protemos translation business management system | Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!
The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.
More info » |
| Anycount & Translation Office 3000 | Translation Office 3000
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |