• State Suggested Answer
  • Replies 20 replies
  • Answers 4 answers
  • Subscribers 436 subscribers
  • Views 18722 views
  • Users 0 members are here
Options
Related

"The file was not created by supported version of Microsoft Excel application and will not be processed"

Jennifer Hocken

Error message when adding new file to Studio 2014 SP2: "The file was not created by supported version of Microsoft Excel application and will not be processed". Experienced this with Word and Excel files received from clients as well as simple files created by myself. Possibly related to latest Microsoft update? Anyone else experience same issue?
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hello
    I also update office 365 and start to get error messages when created projects in Studio 2014 SP2. I solved it by saving all files xlsx and docx in the previous microsoft version : *.xls and *.doc.
    It works for all files except for the excel files of 2 customers (meanwhile the conversion of the word file works) : even converting files in *.xls format I get this error message "pre-scanning error : microsoft office 2003 or later must be installed for processing XLS files". Files appear in the project as "reference". When I click to change the usage, I get this message "The files usage was not changed to translatable, because no matching file type via Project Settings... have you an idea to solve this problem with my actual version of Studio ?
    Thank you for your help
  • 0 in reply to Fabienne RYNNE
    Hi Fabienne,

    The only way to solve this problem is to upgrade Studio to Studio 2015. The new filetype support for these files doesn't exist in Studio 2014.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    Why won't SDL upgrade Trados 2014 to accept the newer versions of Office documents? Is this yet another example of SDL choosing to not upgrade a previous version to support newer file formats in order to push more users to upgrade to a newer version? A workaround is to save the files to the newest version your Trados supports. Time-consuming and perhaps not acceptable to our clients but less expensive than upgrading Trados.
  • 0 in reply to Glen Farley

    Hi Glen,

    Unknown said:
    Why won't SDL upgrade Trados 2014 to accept the newer versions of Office documents?

    The policy we generally adopt is that we support back two major versions (2015/2017).  Adding proper support for the newer formats of all the filetypes we support is not trivial work and given the changes we make to the software in general each time we release it is simply not practical to try and keep supporting new filetypes in old versions of the software.  It's not just Office is it?  It's every single filetype we support.

    The easiest way, and most sensible in my opinion, is to take a support and maintenance contract and then you get all the latest versions of the software at no additional cost to your support.  Given how readily people upgrade their versions of office (less business critical in my opinion) and their hardware, I think ensuring that the software they use for their business is kept upto date seems a very sensible thing to do.

    Why won't you upgrade?

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    Hi Paul. I think the Trados versions are too expensive and that more improvements should come as upgrades to existing versions baked into the purchase price. I have had to lay out several hundred (thousand?) pounds upgrading Trados in 2007, 2009, 2011, 2013 and 2014 often because SDL did not upgrade older versions to keep pace with MS Office versions or chose not to correct bugs or performance issues until later versions or stopped support after 2-3 years. On the other side I am still using MS Office 2010 with absolutely no problems and at a fraction of the cost. It is safe to say that adding Trados file support for MS Word 2016 alone and maybe one or two more formats would save the vast majority of users time-wasting workarounds and, as I said, expensive upgrades.
  • 0 in reply to Glen Farley

    Hi Glen,

    I think, that if you had a support & maintenance contract since 2009 for example, that you will have shelled out around a thousand pounds in total and would have also had 2015 and 2017 already.  You would have also had access to support whenever/if you needed it.

    I don't think we are likely to change our policy of maintaining only two major versions at a time, and this kind of situation could happen again in the future... in fact it's almost certainly going to... unless Microsoft and every other vendor keeps their formats exactly the same and then we wouldn't be having this conversation anyway.  Perhaps the best policy is to treat this tool as if you need it for your business, and budget the maintenance every year.  Taken on a monthly basis I reckon most people spend more on enjoying meals out in the month.

    I don't mean to make light of this topic, but I do wonder why it comes up like this when it is such a fundamental part of doing business.  Don't people think think this way?

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    Hi Paul,

    You are correct - Trados is an essential part of our translation businesses. Another way to look at it is that we are dependent on it - that it is reliable, time-saving and reasonably-priced. When it stops being these things every couple of years it is natural that we resent it. Since rates for most language pairs have been decreasing for several years as competition (both human and machine) has increased and bureaus have squeezed freelancers more and more, every thousand pounds spent is keenly felt.
  • 0 in reply to Glen Farley
    Hi Glen,

    You're right, things get tougher all round. We try our best to add things into each new release that will hopefully allow you to get more from the tools and the resources you use, and hopefully be able to compensate for lower rates and competition. I don't think it's only us who are responsible for low rates, and we are up against a lot of competition too, so we are trying our best.

    I suppose the best solution is to try and find the work in places where the competition is not so keen, and find other ways to generate revenue than the word count alone. I think the complexity of the tools these days opens up all kind of opportunities for those who know how to use them well. Easy for me to say this I know, and much harder to put into practice. But I attend conferences every year and listen to many translators sharing how they do just this. All we can do is try to support it.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    Thanks Paul. And thanks for all the support you personally provide (I see your many posts on several forums.)

    All the best in 2017.
Reply Children