URGENT! Error when importing Studio package "Error creating object with name 'FileTypeInformation" Thread poster: Peter Sass
|
|---|
Peter Sass
Germany
Local time: 00:01
Member
English to German
+ ...
When trying to import a SDL Trados Studio Project Package (.sdlppx format) in Studio 2009 SP1, the import process fails and I get this error message (followed by unintelligible details):
Error creating object with name 'FileTypeInformation'
defined in 'file [C:\Documents and settings\.....\Temp\...\File Types\SDLXLIFF.sdlfiletype]' : Initialization of object failed : Cannot resolve type [Sdl.FileTypeSupport.Framework.IntegrationApi.IconDescriptor, Sdl.FileTypeSupport.Framewor... See more When trying to import a SDL Trados Studio Project Package (.sdlppx format) in Studio 2009 SP1, the import process fails and I get this error message (followed by unintelligible details):
Error creating object with name 'FileTypeInformation'
defined in 'file [C:\Documents and settings\.....\Temp\...\File Types\SDLXLIFF.sdlfiletype]' : Initialization of object failed : Cannot resolve type [Sdl.FileTypeSupport.Framework.IntegrationApi.IconDescriptor, Sdl.FileTypeSupport.Framework.Core] for object with name '(inner object)' defined in file [C:\Documents and settings\....\Temp\...\File Types\SDLXLIFF.sdlfiletype].
The folders 'TM' and 'File Types' are created in the process, but no further project files (esp. the HTML files to translate).
Unfortunately, the SDL Knowledge Base is no help with this as usual. I have already installed the cumulative update 3 patch containing a hotfix for another error with 'Opening third-party XLIFF files', but to no avail.
Could this be simply be related to an error in the agency's files?
But then I've recently received a package from them containing the same type of (HTML) files which I could import without any problem (I've already tried replacing the SDLXLIFF.sdlfiletype with the one of the previous project, but this didn't make any difference).
Or could the SDLXLIFF.sdlfiletype file be faulty in some way?
Or might it be a compatibility issue between Studio SP1 and SP2 package files?
I'd really appreciate any help or hint on this!
[Bearbeitet am 2010-04-06 18:54 GMT] ▲ Collapse
| | | | | Same problem but with Word files | Apr 7, 2010 |
I myself get the same problem with Word files - every time that I try to open a Word file with Trados Studio (independently of whether I create a package or simply try to open a file without creating a package, I also get the same error:
Error creating object with name 'FileTypeInformation' defined in 'file [D:\Traducciones\TRADOS\20090407\File Types\SDLXLIFF.sdlfiletype]' : Initialization of object failed : Cannot resolve type [Sdl.FileTypeSupport.Framework.IntegrationApi.IconDescr... See more I myself get the same problem with Word files - every time that I try to open a Word file with Trados Studio (independently of whether I create a package or simply try to open a file without creating a package, I also get the same error:
Error creating object with name 'FileTypeInformation' defined in 'file [D:\Traducciones\TRADOS\20090407\File Types\SDLXLIFF.sdlfiletype]' : Initialization of object failed : Cannot resolve type [Sdl.FileTypeSupport.Framework.IntegrationApi.IconDescriptor, Sdl.FileTypeSupport.Framework.Core] for object with name '(inner object)' defined in file [D:\Traducciones\TRADOS\20090407\File Types\SDLXLIFF.sdlfiletype]
I join Peter in his plea for some ideas, the whole bloody package is now useless (I can't edit any kind of file) & if you want support from Trados you have to pay for it!
[Editado a las 2010-04-07 19:34 GMT] ▲ Collapse
| | | | Peter Sass
Germany
Local time: 00:01
Member
English to German
+ ...
TOPIC STARTER | What does it mean? | Apr 8, 2010 |
I guess the idea of creating error messages that are intelligble to average computer users is not one that SDL programmers are particularly engaged in. Rather they tend to think out new and more mysteries, i.e. the most uncommon and idiosyncratic error wordings, so that every SDL user will have his or her very own error message!
Well, now we're two with this one, but that's OK.
On the other hand, they also produce mass product errors which only may not fully correspond to bas... See more I guess the idea of creating error messages that are intelligble to average computer users is not one that SDL programmers are particularly engaged in. Rather they tend to think out new and more mysteries, i.e. the most uncommon and idiosyncratic error wordings, so that every SDL user will have his or her very own error message!
Well, now we're two with this one, but that's OK.
On the other hand, they also produce mass product errors which only may not fully correspond to basic logic. For instance, the notorious 'Object reference not set to an instance of an object' tends to appear in the most diverse contexts (needless to say, nobody has ever revealed what the 'object error' is to mean).
So you surely have my sympathy, Ramon, but I'm not too optimistic about solving this mystery too soon I'm afraid. In my case it seems that the issue may be related to an incompatibility of different Trados versions used (see here).
At least I can reassure you that I will let you know once I get handed over a crumb of the SDL knowledge of rule - also follow the other thread.
Best wishes (in all respect)
[Bearbeitet am 2010-04-08 01:19 GMT] ▲ Collapse
| | | | Ehab Tantawy 
Local time: 01:01
Member (2006)
English to Arabic
+ ...
| Upgrade to SP2!! | Apr 29, 2010 |
Hi Peter,
I hope this message finds you well.
I faced the same problem this week but the client told me if I am using SDL Trados SP1 or SP2, and the problem was that he created the SDLPPX package using SP2 version and I was using SP1.
You have to upgrade to SP2 to be able to to lmport the package to your SDL Studio or he/she has to send a SP1 created package to you to be able to open it.
I hope this helps.
Best Regards,
... See more Hi Peter,
I hope this message finds you well.
I faced the same problem this week but the client told me if I am using SDL Trados SP1 or SP2, and the problem was that he created the SDLPPX package using SP2 version and I was using SP1.
You have to upgrade to SP2 to be able to to lmport the package to your SDL Studio or he/she has to send a SP1 created package to you to be able to open it.
I hope this helps.
Best Regards,
Ehab ▲ Collapse
| | |
|
|
|
Peter Sass
Germany
Local time: 00:01
Member
English to German
+ ...
TOPIC STARTER
Thank you Ehab for your advice. I have also found out about this incompatibility between SP1 and SP2 by now - see http://www.proz.com/forum/sdl_trados_support/162164-studio_sp1_and_sp2_incompatibility.html.
It is a complete nuisance, though, as a 'Service Pack' (such as the Windows OS ones) would usually not involve any format chang... See more Thank you Ehab for your advice. I have also found out about this incompatibility between SP1 and SP2 by now - see http://www.proz.com/forum/sdl_trados_support/162164-studio_sp1_and_sp2_incompatibility.html.
It is a complete nuisance, though, as a 'Service Pack' (such as the Windows OS ones) would usually not involve any format changes - they should have rather called SP2 a 'new version' and be honest about the sole reason for the format change: forcing customers to switch and pay for another 'upgrade'.
It is also annoying that SDL nowhere informs about the incompatibility. Therefore, I lost a large project + a client recently, because a client freaked out about not finding the cause for the file problem instantly, which we both didn't have a clue about at first given the absolutely cryptic error messages (he also didn't get ANY response from SDL despite having a support contract).
Thank you SDL, for damaging my business!
[Bearbeitet am 2010-04-29 19:39 GMT] ▲ Collapse
| | | | | Sorry, but no... but you gave me an idea. | Apr 29, 2010 |
You have to upgrade to SP2 to be able to to lmport the package to your SDL Studio or he/she has to send a SP1 created package to you to be able to open it.
Ehab, thank you for the suggestion, but that's not it. It's not that I cannot import a package, it's that I can't even load a simple Word file.
However, I believe you have put me on the right track: A few days before this started happening I actually upgraded to SP2 - apparently the #$%& programmers from SDL have messed up with something that prevents the correct execution. I'll uninstall everything, run a registry cleaner (I don't trust the uninstall routine given how sloppy those guys are) and then re-install the whole thing again.
Thanks for the help!
| | | | Ehab Tantawy
Local time: 01:01
Member (2006)
English to Arabic
+ ...
| Great Ramon!!!!! | Apr 29, 2010 |
Ramon Somoza wrote:
However, I believe you have put me on the right track
Thanks for the help!
I am very happy to hear that.
With the best of luck for all translators who do their best to reach to the best performance and the best professionalism.
Our trials and interests to solve such like problems means that we are keen to make clients satisfied and that we are walking on the right path in our industry.
Warmest Regards,
Ehab
| | | | | Eternal Beta Testers! | Jul 31, 2010 |
Dear colleagues, after n issues related which demand a valuable time from professionals that have to struggle with software problems caused by a producer like SDL, maybe it's time to send them to hell, or suing SDL with a class action for all damages they cause to us.
I feel like a permanent beta-tester, even if I spend lots of money to buy products SDL sells as revolutionary. A revolutionary product is the one which you simply install and open, and work with smoothly, not one that imposes... See more Dear colleagues, after n issues related which demand a valuable time from professionals that have to struggle with software problems caused by a producer like SDL, maybe it's time to send them to hell, or suing SDL with a class action for all damages they cause to us.
I feel like a permanent beta-tester, even if I spend lots of money to buy products SDL sells as revolutionary. A revolutionary product is the one which you simply install and open, and work with smoothly, not one that imposes to install firstly SDL 2007, and then install the new program...
I'd like to open a post to calculate how many hours we loose to solve problems caused by a poor software supplier as SDL. ▲ Collapse
| | |
|
|
|
Emma Goldsmith
Spain
Local time: 00:01
Member (2004)
Spanish to English
| off topic: about generalised moans | Jul 31, 2010 |
Gilberto Allesina wrote:
maybe it's time to send them to hell, or suing SDL with a class action
@ Gilberto,
While a generalised moan probably helps you to let off steam, it isn't very constructive for those of us who are reading your comments.
If you have a specific problem, why not open a new post about it?
Although I do agree I have lost many hours getting to grips with a very advanced piece of software, I must admit I have gained many more from increased productivity, so please count me out of your class action.
| | | | | Speaking as a real Beta tester... | Jul 31, 2010 |
Gilberto Allesina wrote:
Dear colleagues, after n issues related which demand a valuable time from professionals that have to struggle with software problems caused by a producer like SDL, maybe it's time to send them to hell, or suing SDL with a class action for all damages they cause to us.
I feel like a permanent beta-tester, even if I spend lots of money to buy products SDL sells as revolutionary. A revolutionary product is the one which you simply install and open, and work with smoothly, not one that imposes to install firstly SDL 2007, and then install the new program...
I'd like to open a post to calculate how many hours we loose to solve problems caused by a poor software supplier as SDL.
... I can't but second Emma's post. I agree that the first release of Studio in June 2009 was indeed riddled with bugs, but the two SP fixed most of them. There are always things to improve, but as far as I can tell, SDL are working on those really hard (FYI, SP3 is on its way). BTW, who forced you to purchase Studio in the first place, Gilberto?
[Upraveno: 2010-07-31 17:44 GMT]
| | | | Walter Blaser
Switzerland
Local time: 00:01
French to German
+ ...
| Is there any flawless software? | Aug 1, 2010 |
n issues related which demand a valuable time from professionals that have to struggle with software problems caused by a producer like SDL, maybe it's time to send them to hell, or suing SDL with a class action for all damages they cause to us
Gilberto
As Emma, I can very well understand your frustration when you are using a piece of software that does not do what you want it to do. On the other hand, your suggestion is not going to solve any problems.
A revolutionary product is the one which you simply install and open, and work with smoothly, not one that imposes to install firstly SDL 2007, and then install the new program...
I guess your expectations are probably too optimistic.
Although every software editor strives to release a software that is bugfree, this goal can not be realistically achieved today due to the immense variety of third-party software that might be installed on your PC next to his software. There are so many interdependencies that every PC out there is different. There are no two PCs that are alike, except as long as only the OS has been installed on them. This makes it impossible for software developers to test 'all' possible situations before they release a product or it would take such a time that they would never release the product. So, it is always a trade-off between stability of the new release and marketing considerations to get the product to the market. As Stanislav mentioned, SDL goes through different stages of beta testing before they release their new software. Being one of them, I can tell you that SDL very carefully addresses all our bug reports and makes the necessary changes until the product is 'stable enough' to be released. Obviously, this does not mean that this software will run without any errors on all the thousands of PCs on which it is going to be installed. Also keep in mind that many of the errors that do occur are very specific to the configuration of the PC on which they occur and often cannot be reproduced elsewhere, not to speak about the errors which are caused by wrong usage or lack of knowledge.
I have used a large number of software programs from different editors in the past years and I often faced such situations, not only with SDL. So, they are not worse than other software suppliers in this respect.
Also, do not forget that this is a brand-new software generation, completely rewritten from scratch, which may explain that there are maybe a little more bugs to be found than in a new release of a proven software where only few changes have been made.
To sum up, I want to say that - as a heavy daily user of Studio - I have faced a few problems, some of them even made me loose a lot of time, but at the end I join Emma in saying that the productivity gain is bigger. It takes some time and effort to get familiar with Studio and to master all its features (it is much more comprehensive than the 2007 version), but once you are used to it, you would never want to go back.
Walter
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » URGENT! Error when importing Studio package "Error creating object with name 'FileTypeInformation" | Wordfast Pro | Translation Memory Software for Any Platform
Exclusive discount for ProZ.com users!
Save over 13% when purchasing Wordfast Pro through ProZ.com. Wordfast is the world's #1 provider of platform-independent Translation Memory software. Consistently ranked the most user-friendly and highest value
Buy now! » |
| | 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... | | | | | |
Login to reply/comment 
Translation news related to SDL Trados
