Studio fails to convert xls to translatable format Thread poster: FarkasAndras
|
It sounds familiar, doesn't it? Trados failing to import or export Office files... We see variations on this theme all the time, but I haven't come across this particular flavour so far, so I'm stumped. Studio fails to import my xls files, with the error "Exception has been thrown by the target of an invocation." Type: System.Reflection.TargetInvocationException, mscorlib. I have Win7, Office 2003 and Studio FL 2009 with all but the most recent update installed. <... See more It sounds familiar, doesn't it? Trados failing to import or export Office files... We see variations on this theme all the time, but I haven't come across this particular flavour so far, so I'm stumped. Studio fails to import my xls files, with the error "Exception has been thrown by the target of an invocation." Type: System.Reflection.TargetInvocationException, mscorlib. I have Win7, Office 2003 and Studio FL 2009 with all but the most recent update installed. Here's one of the offending files (with the actual text obfuscated for non-disclosure). And the error log. I can translate the files and generate the target xls files by generating a ttx with tageditor, but I want Studio to actually work without taking detours into obsolete software. Any tips? ▲ Collapse | | |
Susanne Rieg (X) Local time: 12:22 English to German + ... Imports fine in Studio 2011 | Feb 9, 2012 |
Downloaded your file and had no problem importing it. Maybe there was some offensive (:-) text in it that you obfuscated? Sanne | | |
Test file was ok in 2009 and 2011 | Feb 9, 2012 |
Hi Farkas, I tested your file successfully with these versions: SDL Trados Studio 2011 SP1 – 10.1.2861.1 SDL Trados Studio 2009 SP3 – 9.1.2307.8 I also checked your error log but this didn't really point me to anything obvious I'm afraid. Regards Paul | | |
FarkasAndras Local time: 12:22 English to Hungarian + ... TOPIC STARTER Not the abababa | Feb 9, 2012 |
Susanne Rieg wrote: Downloaded your file and had no problem importing it. Maybe there was some offensive (:-) text in it that you obfuscated? Sanne Interesting. After nuking the text, I of course tested the file in Studio and got the same error. I just tested it again to make sure, and I still get the error on the abababab file. It must be something at least partly specific to my environment then. Do any of you have office 2003 or do you both use 2007 or 2010? The error message does mention InteropServices so it might be the Office interop stuff that's screwing up. | |
|
|
Susanne Rieg (X) Local time: 12:22 English to German + ... |
FarkasAndras Local time: 12:22 English to Hungarian + ... TOPIC STARTER
SDL Support wrote: Hi Farkas, I tested your file successfully with these versions: SDL Trados Studio 2011 SP1 – 10.1.2861.1 SDL Trados Studio 2009 SP3 – 9.1.2307.8 I also checked your error log but this didn't really point me to anything obvious I'm afraid. Regards Paul My version is: SDL Trados Studio 2009 SP3 – 9.1.2297.8 I might update when I'm done with the files I'm working on right now, but it seems very unlikely that it will help. | | |
Probably not... | Feb 9, 2012 |
Hi Farkas, The error log shows it seems to be trying to access Excel 11 (2003) while it should maybe access Excel 12 (2007) but does not for some reason. Is it possible to change the default version of Office that gets used perhaps? I've never done this but it seems possible. Maybe this article will help? http://support.microsoft.com/kb/928091/ ... See more Hi Farkas, The error log shows it seems to be trying to access Excel 11 (2003) while it should maybe access Excel 12 (2007) but does not for some reason. Is it possible to change the default version of Office that gets used perhaps? I've never done this but it seems possible. Maybe this article will help? http://support.microsoft.com/kb/928091/ I don't know if this will resolve the issue but it's worth a shot. Regards Paul ▲ Collapse | | |
FarkasAndras Local time: 12:22 English to Hungarian + ... TOPIC STARTER
SDL Support wrote: The error log shows it seems to be trying to access Excel 11 (2003) while it should maybe access Excel 12 (2007) but does not for some reason. I'd imagine it's using Excel 11 because that's what I have. As stated above, I use Office 2003, and I don't have Office 2007. So unless Studio comes bundled with some Office 2007/2010 interop stuff, it has no choice but 2003. The interesting thing is that there's an xlsx file in the project, and that imports fine while all the xls files fail. | | |