Error: "Object reference not set to instance of an object" when working with Word documents containing tables

Hi Paul,

I'm experiencing a big problem when trying to work with Word documents containing tables, since Studio 2011 does not allow me to open the xliff file and the famous error message "Object reference not set to instance of an object" pops out. Today I got the error message when trying to open a .xliff file prepared by a fellow translator (who can work on it without any problem) based on a word document containing tables, once again.

It is really driving me crazy and not allowing me to work... It happened 3 times in 10 days, with 3 different word documents (all of them containing tables) coming from 3 different clients. Do you have any idea of the origin of the problem and how can I solve it so that I can properly work again? 

Thank you very much in advance.

Francesco

Parents
  • Hello Francesco,

    I received your files and can open them all, and save the target, in both Studio 2011 and Studio 2014.  I think the problem must be local to your installation, especially when you consider your fellow translator also has no problem.  The files you are translating are simple so I'm feeling confident we don't have a filetype issue here.

    First of all can you confirm you are using the latest version of Studio 2011.  It should be Studio 2011 SP2R - 10.4.3123.2 which you can see in the Help -> About SDL Trados Studio window found in the toolbar for Studio 2011.  If you don't have this version installed then I would recommend you do this first of all.  It will be a free upgrade so there's no reason for not doing this.  You'll find the latest SP2R release in your MySDL Account.  Then allow the automatic update to update to the latest patch.

    If you do have this version installed already then please try running a repair installation from the Windows Control Panel.

    1. From the Start menu on your computer, choose Settings > Control Panel.
    2. In the Control Panel, select Add or Remove Programs or Programs and Features.
    3. Select SDL Trados Studio 2011 SP2 from the list of programs and click Click here for support information. The Support Info dialog box is displayed.
    4. Click the Repair button. This starts the Windows Installer which runs the repair process.
    5. When the process is complete, click Finish

    Now try again.  If this still doesn't help please log a support case so an Engineer can take a look at the problem on your machine.  

    Go to the Knowledgebase and then go to the tab called Solution Finder.  Now go here;

    Download & Installation Problems
    - I use SDL Trados Studio and/or SDL MultiTerm 2009, 2011 or 2014
    -- The installation went fine but now I get an error message etc
    --- The problem occurs in (pick the appropriate tool/s)
    ---- None of the articles resolved my problem (if they didn’t!)

    Follow the route for your problem and if there is no answer that helps by the time you get to the end you'll be presented with a form to contact support. Complete all the fields in the form making sure your email address is entered correctly or nobody will be able to get back in touch with you.

    Also use the Chrome browser to log the case if you have it; you'll get more success in completing the form.

    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

  • Hello Paul,

    thank you for your reply.

    After checking and confirming that I was well using the last version of Studio 2011 (Studio 2011 SP2R - 10.4.3123.2), I ran the repair installation as you suggested me but the problem was still there.

    I then checked the KB and tried 3 out of the 4 suggested solutions in the kb (article #4457.) but, before uninstalling Studio and installing it again, I made a last attempt that worked for me in the past (luckily I had noted it somewhere):

    Windows Vista/7:

    C:\Users\[User_Name]\AppData\Local\SDL: delete/rename the SDL Trados Studio and ProjectApi folder

    C:\Users\[User_Name]\AppData\Roaming\SDL: delete/rename the SDL Trados Studio folder

    C:\Users\[User_Name]\Documents\Studio 2011: rename the Studio 2011 folder to Studio 2011_Old

    Well, luckily it worked once again, BUT, I wonder if it is normal that every 3-4 months I have to "repair" Studio loosing all my settings, since I cannot work with Word documents containing tables. For this reason I logged a support case, hoping somebody can explain me the origin of this problem.

    Last week I bought the 2014 upgrade but I have not installed yet since I am going to change my PC so I will install it directly in the new machine. I really hope not to regret my purchase.

    Regards,

    Francesco

  • Hi Paul,

    here is the answer I got from the SDL Support Team:

    "The error that you are receiving it is a very common one and it can be generated by various situation, even from the moment you start Studio or opening a general file or while working on a project. The issue is generated in the corruption of Studio's base settings files once a new update is installed and the best and fastest solution is resetting them to default once this happens. Normally with 2014 and after installing all the updates you should not have to face this problem anymore."

    So it seems the problem is not locally related to my machine, but rather to a corruption of settings caused by the installation of update releases. That explains why the problem is cyclical. I really hope "not to have to face this problem anymore" once I install the 2014 version.

    Regards,

    Francesco

Reply
  • Hi Paul,

    here is the answer I got from the SDL Support Team:

    "The error that you are receiving it is a very common one and it can be generated by various situation, even from the moment you start Studio or opening a general file or while working on a project. The issue is generated in the corruption of Studio's base settings files once a new update is installed and the best and fastest solution is resetting them to default once this happens. Normally with 2014 and after installing all the updates you should not have to face this problem anymore."

    So it seems the problem is not locally related to my machine, but rather to a corruption of settings caused by the installation of update releases. That explains why the problem is cyclical. I really hope "not to have to face this problem anymore" once I install the 2014 version.

    Regards,

    Francesco

Children
No Data