• State Verified Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 435 subscribers
  • Views 9749 views
  • Users 0 members are here
Options

"Object reference not set to an instance of an object"

Per Hybinette Ivert

Hi SDL. I am facing the "Object reference..." error while trying to open a package. This happened after I upgraded to the latest (as of today) version of Studio. It doesn't happen with all packages that are sent to me, but it happens with all the packages for a certain client, and I am not able to work with the text since the error keeps appearing everytime I click a segment. I have already tried re-installing, repairing, following the KB guide etc. Nothing seems to work. What can I do? I'd be happy to provide you with more information if needed, maybe even the work package itself.

/Pelle
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hi Pelle,

    Perhaps let's start with the simple things.  When you come across a package that behaves in this way and you get the error in the editor view as you describe can you try resetting the window layout?  You didn't mention the version of Studio you are using (which is always a good thing to do when you report a problem) but assuming this is the current version go to View -> Reset Window layout.

    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,

    Thank you for the swift reply. As I said, I am using the latest version as of today, but if you do need the exact number it's Studio 2014 SP2 11.2.4378.9. I have already tried resetting the window layout, both from within the file and outside of the file. The other method, i.e. deleting those settings files, did also not work. Since I'm on a tight deadline, I have now reverted back to version SP2 11.2.4322.0, and in this version everything is stable. At least now I'm able to work, but now I have to be careful not to click "Yes" when Studio prompts me to update. Is there anything else I can try (which I will do when my task is finished)?

    Pelle
  • 0 in reply to Per Hybinette Ivert
    Hi Pelle,

    It sounds as though you are already ahead of me with trouble shooting, and if it works with the previous version then this does offer a clue since the only change is CU9. Would you be able to share the package so we can reproduce the issue?

    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

    Yes, here is the package causing the trouble:

    edit: link removed
  • 0 in reply to Per Hybinette Ivert
    Thanks Pelle, I think this is because your files are custom xml files from a GroupShare server. I saw this reported this week and I think you might be able to resolve this if your customer sends you the filetype setting they used for the project and then you can import this into the filetypes list of your Project Settings. I also think there may be a fix available while we wait for this to be resolved in the software properly, but I can't confirm this until tomorrow. So in the meantime if you are able try asking your client for the filetype settings file(s) used in the project.

    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 Pelle,

    ok - here's a workaround you can apply on your own.  The problem is a new one and support confirmed another workaround which I just verified with your package.  You can create a dummy filetype using the same name as the one used by your client.  So if I switch to Tag ID mode in Studio (the one where the tags have numbers instead of text) then I see this at the top of the translation:

    So I created a new XML filetype in the Project Settings using the same name like this... no specific settings are needed just get the name right and then click through the rest:

    Now everything works as expected with no error message.  This problem will be fixed in a future update.

    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
    Thank you for your assistance, Paul. I fiddled with the settings and couldn't get it to work at first, but finally I realized that the name had to be entered in "File type identifier" and not just in "File type name". Now it works, so I am able to work with these packages using the most up-to-date version of Studio.

    Have a nice weekend, and thanks again!

    Pelle
Reply
  • 0 in reply to Paul
    Thank you for your assistance, Paul. I fiddled with the settings and couldn't get it to work at first, but finally I realized that the name had to be entered in "File type identifier" and not just in "File type name". Now it works, so I am able to work with these packages using the most up-to-date version of Studio.

    Have a nice weekend, and thanks again!

    Pelle
Children
No Data