Chris Barella 

Chris Barella said:

“failed to save target content: object reference not set to an instance of an object”

It's highly likely that your message appears in a small error popup.  In that popup there is normally a small disk symbol that you can click and then download a file to your desktop that can then be attached to this forum.  That file contains the full error stack and will provide better information related to where the error might be coming from.

If you don't see this, maybe since you are using a batch task to generate the files, there should still be a way to get to this in the UI you see.  Look for horizontal scroll bars that allow you to find off screen links to these error details.

If none of that seems obvious can you share a screenshot of the error you see?

Sure, here you go- 

<SDLErrorDetails time="01/09/2025 13:11:29">
  <ErrorMessage>Failed to save target content: Object reference not set to an instance of an object.</ErrorMessage>
  <Exception>
    <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.FileTypeSupport.Filters.Excel</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.UpdateDocumentFile(XsltArgumentList argsList, XslCompiledTransform xslTransform, XPathNavigator child)
   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.IterateXsltFiles(XsltArgumentList argsList, FileMap rule, XPathNodeIterator iter, Boolean isUpdate, String targetFilePath)
   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.IterateContentType(String xslFileNamesPath, Boolean isUpdate, String filePath, String filterStr, String targetFilePath, Boolean isCalledByRelsTableIteration)
   at Sdl.FileTypeSupport.Filters.Excel.FilterControllerFramework.OfficeController.serviceBackward()
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileParser.DocumentParser.Update()
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileParser.DocumentExtractImpl.Update(DocumentCollection srcCollection, String filename, String tgtFilePath)
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileWriterAndPreviewFileWriter.WriterImpl.EndOfInput()
   at Sdl.FileTypeSupport.Filters.Excel.PlugInFilter.FileWriterAndPreviewFileWriter.ExcelWriter.EndOfInput()
   at Sdl.FileTypeSupport.Framework.Integration.NativeWriterMessagesProxy.EndOfInput()
   at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.CallEndOfInput()
   at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.FileComplete()
   at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
   at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_Visit(TmfcReaderImpl* , FrameworkFileContainerField* field)
   at FrameworkFileContainerField.vv_AcceptFrameworkVisitor(FrameworkFileContainerField* , FrameworkFieldVisitor* visitor)
   at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_VisitStartEndField(TmfcReaderImpl* , StartEndField* startEnd)
   at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.b_VisitNext(TmfcReaderImpl* )
   at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReader.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
   at Sdl.TranslationStudio.Editor.TranslationEditor.SaveMonolingualAsJobRequest.Execute(IJobExecutionContext context)
   at Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__47_0()
   at Sdl.Desktop.Logger.Log.Resources(Object message, Action action)
   at Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>15.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>15.2.8.3007</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 11 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>2057</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>DESKTOP-ELSRQQ0\hp</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>DESKTOP-ELSRQQ0</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>33226972 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

 Chris Barella 

ok - thank you.  So this is not an XLIFF, we are talking about an Excel file, monolingual, and you are working with Trados Studio 2019.

There isn't anything obvious in the stack trace, and the software is too old to be looking for a bug, so the best solution I think would be this:

1. open the original Excel file as a single file project
2. pre-translate from your TM
3. use File -> Save Target As instead of the batch task to create the target file (be careful to rename the target file so you don't overwrite the source)

That may at least get your target file out.  If it doesn't test this:

1. open the original Excel file as a single file project
2. use File -> Save Target As to immediately save the target without translating

If that also fails then the problem is either a bug or a problem with the Excel.  To solve you'll need to divide and conquer.  So take a copy of the Excel source and put it into a new folder.  Then go through this process (it's faster than you might think):

1. split the file into two, save each one so you have file#1, file#2.
2. open the file#1 as a single file project
3. use File -> Save Target As to immediately save the target without translating (save as t_file#1)
4. open the file#2 as a single file project
5. use File -> Save Target As to immediately save the target without translating (save as t_file#2)
6. if they both fail you probably have a more serious problem and you could try saving the file as an xls perhaps?  Then translate that.
7. If one fails then split the one that fails and repeat with the split files.
8. Repeat this until you get down to a single worksheet, or a small part of the worksheet that fails.
9. Remove that part from the original source and process the file again.
10. Hopefully that will work, and then you can manually update the translated file for the small part that failed to process.

If you're struggling I'd be happy to take a look at the file for you if that's acceptable?  You can send the translated SDLXLIFF and the original source Excel to pfilkin at sdl dot com.

Many thanks Paul. Actually, I am wondering whether the fact that it is a trial version (because my licence won't activate) has anything to do with it. I don't think it should but this is software after all... 

I will try the steps outlined and hopefully that will sort it. 

Chris Barella 

Chris Barella said:

Actually, I am wondering whether the fact that it is a trial version (because my licence won't activate) has anything to do with it.

I doubt it... trial versions are normally full Professional versions.  I am curious how you are managing to run a trial version of something that old though?  Might be worth running a 2024 version if you're on a trial.

That's what I had thought - no point in it being a trial if it can't do everything. 

I have no idea why it has reverted to this trial version. 

I can't follow your 1st approach as i can't update my TM from the translated Xliff file (import failed. File could not be processed) So I have an empty TM. I'll follow your other step. 

Chris Barella 

Chris Barella said:

(import failed. File could not be processed)

This could be relevant information too.  Can you look at the sdlxliff with a text editor and make sure it's well formed and not corrupt in some way?  It may be possible to extract the translations another way if it is, but worth checking.

Thanks Paul, to be honest, I'm not really a PM by training and have just picked it up as I have gone along (I have always had experienced PMs to help with this stuff). I was in the middle of sending you an email with the source and Xliff files as I suspect that you will be much faster at resolving this, if I'm not in the way..

Thanks Paul, to be honest, I'm not really a PM by training and have just picked it up as I have gone along (I have always had experienced PMs to help with this stuff). I was in the middle of sending you an email with the source and Xliff files as I suspect that you will be much faster at resolving this, if I'm not in the way..

Chris Barella 

I sent you an email with the target Excel files and a Translation Memory for each file.  There wasn't anything helpful for others I could share here.  Rather it was just a question of solving a few issues and running the processes I described earlier.  So I'll close this thread off as done and suggest the earlier approach as the way forward.

Many thanks Paul, much appreciated.