Detecting language please wait for.......
I am using SDL Trados Studio 2017 SR1 - 14.1.10018.54792
When I am working with files merged on the fly in review mode, I get the error message "Object reference not set to an instance of an object" when I try to save them. Also, when I export multiple files from the same project for bilingual review, import the changes and then try to work on the merged files with reviewed changes, I also get the same error message.
This problem only started to occur after I applied an update in November/December 2019. Strangely, according to the release notes, this update was supposed to fix precisely this problem.
Full details of the error message below:
<SDLErrorDetails time="30/12/2019 15:10:37"><ErrorMessage>Object reference not set to an instance of an object.</ErrorMessage><Exception><Type>System.NullReferenceException, mscorlib, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type><HelpLink/><Source>Sdl.TranslationStudio.Api</Source><HResult>-2147467261</HResult><StackTrace><![CDATA[
]]></StackTrace></Exception><Environment><ProductName>SDL Trados Studio</ProductName><ProductVersion>18.104.22.168</ProductVersion><EntryAssemblyFileVersion>14.1.10018.54792</EntryAssemblyFileVersion><OperatingSystem>Microsoft Windows 10 Home</OperatingSystem><ServicePack>NULL</ServicePack><OperatingSystemLanguage>2057</OperatingSystemLanguage><CodePage>1252</CodePage><LoggedOnUser>LENOVO-PC\Daisy Waites</LoggedOnUser><DotNetFrameWork>4.0.30319.42000</DotNetFrameWork><ComputerName>LENOVO-PC</ComputerName><ConnectedToNetwork>True</ConnectedToNetwork><PhysicalMemory>8286484 MB</PhysicalMemory></Environment></SDLErrorDetails>
No, I don't think so. Firstly, this problem only started when I applied an update to Studio in November/December 2019. Secondly, it does not only relate to files exported for external review. I have just…
I have exactly the same problem - unable to save edits to multiple files since the update.
Hi Emma Daisy Waites
Thank you. I can reproduce the problem following your steps with Studio 2017, and can also do this with my own made up files. I'll log this with the support team so they investigate…
Emma Daisy Waites
Maybe the same problem as here?
No, I don't think so. Firstly, this problem only started when I applied an update to Studio in November/December 2019. Secondly, it does not only relate to files exported for external review. I have just created a dummy project, pseudo-translated the files, and then opened them (merged on the fly) in Studio in Review mode (not in Word). As soon as I inserted a comment in the merged files, I got the error message mentioned above.
Can you share the files you merged and give me the steps you went through? You can send them to firstname.lastname@example.org
I tested this with the process you describe in 2017 and 2019 and cannot cause an error so maybe it would be helpful to work with your files, using your steps.
I have just emailed you the files.
I am sorry to hear this, but at least I am not alone. Did the problem seem to start when you inserted a comment?
Not that I can remember. I just went to work on a set of files in the usual way and then found I couldn't save. Ditto for editing. For cross-file consistency I ended up having to run F8 on the files, take screenshots of my edits with tracked changes, close the files again and then add the edits to each file. I couldn't even run a bilingual preview because of course Trados need to (save and) close the file to do so. I assumed it was the specific files, but since I came back to work after Christmas it's happening on every project with multiple files (which in my case is most), hence my search on here yesterday.
I am using the same version as you. I updated shortly before Christmas.
Yes, working with multiple files is going to be unpleasant. With my dummy test project, the problem seemed to start when I inserted a comment. I'm still waiting to hear back from Paul.
Did you receive the files that I emailed you?
Thank you. I can reproduce the problem following your steps with Studio 2017, and can also do this with my own made up files. I'll log this with the support team so they investigate and submit to development.
I also tested with Studio 2019 and this works fine, so if you have access to that version it might be helpful.
We had the same problem as you can see here: https://community.sdl.com/product-groups/translationproductivity/f/studio/28204/cannot-save-multiple-files-in-editor-studio-2017-cu18/90382#90382
Solution in Studio 2017 CU18 is to delete the comments and then Studio can save virtually merged files w/ no issues.
Question to SDL: why this happened only since the last update and it doesn't occur in CU17 or in Studio 2019?
Hello NLG GmbH,
I really think you should log a support ticket- the support team can then identify whether this is a bug or not and take steps where necessary to rectify this.
Steven Whale I think that Paul already did that, see a few posts above.
Anyway, you can reproduce the case easily at your side
Hi Paul, Is there a solution yet to this problem? I use Studio 2017 and did the latest update last week. Whenever I try to open multiple files in one go (even small ones) I keep getting the same error message "Object reference" and cannot save an xliff or doc file. It is very frustrating because I have many cross-file repetitions and I cannot use the autopropagate between files anymore nor review multiple files. I am referring to Word files, not excel. And yes, my files have comments.
I think you should raise a new thread and not tack your question on the back of this one.The reasons for your problem could be something else and if you share your stack trace we can check it better.