• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 1730 views
  • Users 0 members are here
Options
Related

programme stuck during translation

Etienne Muylle

I am ding a 10,000 word translation. At segment 124, it refused to jump to the next segment and to type any letter or sign. I switched off the PC, started again, no use. What shoud I do? The message that appears on the screen is : (in Spanish): REFERENCIA A OBJETO NO ESTABLECIDA COMO INSTANCIA DE OBJETO.

 

It is very urgent!!!

Thanks in advance

 

Etienne

 
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    "Object reference not set to an instance of an object". We've all seen that one!
    Paul is hinting at the possibility that this is a look-up problem. My experience is that the message occurs because somewhere in the project set-up there is a reference to an object (i.e. a TM or termbase) but when Studio goes to the specified location, the 'object' is not found.
    In the lower left corner of the error window is an icon you can click to view more detail of the error message. If you find and expand the Stack Trace section, the first couple of lines of the Stack Trace often tell you where in Studio the problem occurred (TM, Multiterm, etc.)

    I don't know why it happens, but it seems that Studio sometimes 'forgets' where the resources for the project are located. Maybe it is related to how many other programs are running or have been run and closed, as if the PC RAM gets 'untidy'.

    If I get this error message, I try the following 'fixes', usually in this order:
    1. In Project Settings, Remove all TMs and termbases from project, then OK to save changes. Ctrl+S to save file/project. Go back into Project Settings and put the TMs and termbases back. Click OK.
    2. Remove TMs and termbases from project, as in (1), then Exit Studio. Relaunch Studio, and put back TMs and termbases, as in (1).
    3.Remove TMs and termbases from project, as in (1), and Exit Studio. Reboot PC, relaunch Studio, and put back TMs and termbases, as in (1).

    Happy hunting!
    Simon
Reply
  • 0
    "Object reference not set to an instance of an object". We've all seen that one!
    Paul is hinting at the possibility that this is a look-up problem. My experience is that the message occurs because somewhere in the project set-up there is a reference to an object (i.e. a TM or termbase) but when Studio goes to the specified location, the 'object' is not found.
    In the lower left corner of the error window is an icon you can click to view more detail of the error message. If you find and expand the Stack Trace section, the first couple of lines of the Stack Trace often tell you where in Studio the problem occurred (TM, Multiterm, etc.)

    I don't know why it happens, but it seems that Studio sometimes 'forgets' where the resources for the project are located. Maybe it is related to how many other programs are running or have been run and closed, as if the PC RAM gets 'untidy'.

    If I get this error message, I try the following 'fixes', usually in this order:
    1. In Project Settings, Remove all TMs and termbases from project, then OK to save changes. Ctrl+S to save file/project. Go back into Project Settings and put the TMs and termbases back. Click OK.
    2. Remove TMs and termbases from project, as in (1), then Exit Studio. Relaunch Studio, and put back TMs and termbases, as in (1).
    3.Remove TMs and termbases from project, as in (1), and Exit Studio. Reboot PC, relaunch Studio, and put back TMs and termbases, as in (1).

    Happy hunting!
    Simon
Children
No Data