Error message: Object reference not set to an instance of an object

Question

Hi, 
 I am getting an error message (Object reference not set to an instance of an object) when trying to generate a target translation in Studio 2014. 
 I have already tried some of the solutions mentioned in the forum but none worked... 
 Any ideas? 
 
 Here is what I have tried already&hellip;.. 
 If Studio starts, but shows the error message Object reference not set to an instance of an object when you switch between different dialogs and views:

Open Studio. 
 Activate the view where the error occurs (for example the Editor view). 
 Click View > Reset Window Layout . 
 Click OK to confirm resetting the window layout.

If the error message still appears after following the steps above, follow the instructions under Solution 2 below. 
 
 Solution 2

Rename the setting files and run a repair installation 
 
 Close all SDL applications. 
 Go to the following folder: 
 
 SDL Trados Studio 2011 
 
 Windows XP : C:\Documents and Settings\[USER_NAME]\Application Data\SDL\SDL Trados Studio\10.0.0.0 
 Windows Vista/7/8 : C:\Users\[USER_NAME]\AppData\Roaming\SDL\SDL Trados Studio\10.0.0.0

SDL Trados Studio 2014 
 
 Windows XP : C:\Documents and Settings\[USER_NAME]\Application Data\SDL\SDL Trados Studio\11.0.0.0 
 Windows Vista/7/8 : C:\Users\[USER_NAME]\AppData\Roaming\SDL\SDL Trados Studio\11.0.0.0

Rename the following XML files (for example, add an underscore before/after the filename):
 
 BaseSettings.xml 
 Plugincache.xml 
 UserSettings.xml

NOTE: If you do not find this folder, make sure that these files are not hidden. See KB article # 3330 : Show hidden files and folders on Windows operating systems.

Run a repair installation 
 
 Open the Control Panel :
 
 Windows Vista/7 : Start > Control Panel > Programs > Programs and Features . 
 Windows 8 : Right-click on the screen at bottom-left corner and choose Control Panel > Uninstall a Program .

Click to highlight the damaged SDL Trados Studio version and click Repair . 
 Restart Studio.

Walter Blaser · Answer

Clothilde This may be caused by the document itself and not necessarily by the software. Did you run a Verify (F8) on this document to make sure that the translation does not contain any tag errors? What happens when you try to do a preview, do you get the same error? Try to open the source file and do a preview without translating any of the segments (make sure that the right-hand column is empty or run the batch task "Pseudo-Translate). If this preview also fails, then this means that the document is incompatible with Studio and needs to be modified (source). If this preview works fine, it means that the error has been introduced with your translation and you need to verify that you don't have any tag errors. Should the document be incompatible with Studio (case 1), report again and we'll arrange to have a look at your document. Walter

Alison Field · Answer

Hi Rutger, 
 I took a look online and found the following: 
 Settings > Apps > Apps & Features 
 In recent versions of Windows 10, this page has been substantially beefed up and now includes listings for not just Store apps but also desktop apps installed through the Store or via an installer. 
 The fastest way to this Settings page is to right-click Start (or press Windows key + X) and then click Apps & Features from the top of the Quick Links menu.

Click any app to expand its listing and expose the Uninstall button. (That option isn't available for some apps that are included with Windows.) Click Advanced Options to open a separate pane that lets you repair or reset a Store app. If you ever find an app that's misbehaving, always try one or both of these options before taking the drastic step of uninstalling and reinstalling it. 
 windows-10-tip-Apps & Features 
 So you should be able to use the above method. 
 All the best 
 Ali

Alison Field · Answer

Hi Rutger H. Cornets de Groot 
 I've just noticed I have the same way of accessing apps as I described to you and in the image you shared in your last post. 
 So... do you also have this link on that same page? 
 
 If you do, you should be able to access the 'Legacy' Programs and Features page that I shared in my first post. 
 Hope this works! 
 All the best 
 Ali

Paul · Answer

Unknown said: Unfortunately, it did not fix my problem, which is to make the MyMemory plugin work; it throws the error message when I try to use it... 
 Rutger H. Cornets de Groot 
 The MyMemory error is probably out of your control and ours. They had a fire in the service tunnel to their data centre damaging cables which their main connectivity provider is working hard to restore. Once they sort that out the MyMemory plugin will just work.

Paul · Answer

Unknown said: This is a programming error message, intended for programmers, not for users. The developers should take care of it and I believe it is an exercise in futility following instructions like "reset", "reinstall", "reboot". 
 
 I don't agree with you at all... at least not 100%. Yes, the details in the error stack are intended for developers, but there is often information in the error stack which can be read to see where the likely source of the problem is. In this case, as I saw a stack for the same problem from another users, the words MyMemory are clearly written throughout the message and this is at least a good indication that the course of action would be to contact the MyMemory team and ask them about the issue. 
 In addition to that the error messages do have a link to the a couple of resources that can be searched automatically and sometimes this can also be helpful because the solution you get to can be helpful. 
 It's not always like that and sometimes the message have nothing helpful in there at all, sometimes nothing useful for a developer either. But checking them is not an exercise in futility. 
 Certainly I welcome the input from Alison Field who seems to be available to help anyone all the time and her experience means her help is almost always on the nail! 
 Thank you Ali!

Trados Studio > 2. Trados Studio

Error message: Object reference not set to an instance of an object

Solution 2

Rename the setting files and run a repair installation

Run a repair installation

Top Replies