Hello Gabriele Weyland-Tschentscher ,

I think it would be important to take a look at the xliffs.

It appears, if I'm not mistaken that your company has a current valid SMA contract so I would suggest logging a support ticket and our support team can take a look at this for you.

Ok, here is what I tried so far:

I created a project with the internal studio settings without using any template.

I added a groupshare tm.

I added two docx-files and created the project

I opened two xliff files at once and added a comment. I tried to save.

The following error orccured: "Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt"

I deleted the comment and I was able to save.

I tried it with doc-files as well. Same error same behaviour.

I deleted the tm from the settings and converted the word files to xliff with board ressources/filters.

The same error occured.

It must have something to do with studio itself, rather than with groupshare or any xliff filter.

Any idea?

Thank you in advance

Regards,

Judith

Hello Gabriele Weyland-Tschentscher ,

If the problem was directly related to Studio, I would expect to see a lot of similar cases being raised which isn't the case ,

It does appear that the error is somehow connected to 'comments'

Are you merging the files?

If you add only one file (as a test project) do the same problems occur?

You mentioned the above error - 

Gabriele Weyland-Tschentscher said:

"Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt"

this is however very generic- please post the full error stack

Hi Steven, please find attached the full error message as reuested:

Thank you very much for your help!!

Regards

Judith

<?xml version="1.0"?>

-<SDLErrorDetails time="28.01.2021 13:33:33">

<ErrorMessage>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.TranslationStudio.Api</Source>

<HResult>-2147467261</HResult>


-<StackTrace>

-<![CDATA[   at Sdl.TranslationStudio.Api.Common.SdlxliffXmlDocumentHelper.RemoveUnwantedCommentDefinitions(XDocument childDocument, XmlNamespaceManager nsManager)
   at Sdl.TranslationStudio.Api.Common.SdlxliffXmlDocumentHelper.TransferDocumentInfo(XDocument mergedDocument, XDocument childDocument, XmlNamespaceManager nsManager)
   at Sdl.TranslationStudio.Api.Common.MergedFileChildrenPersister.CreateChildFilesDocuments(XmlNamespaceManager nsManager)
   at Sdl.TranslationStudio.Api.Common.MergedFileChildrenPersister.SaveChildFiles(String outputFile, String[] bilingualFilePaths)
   at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.SaveBilingualImpl(String[] bilingualFilePaths, Boolean copy, IJobExecutionContext context, Boolean isAutoSaved)
   at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.Save(IJobExecutionContext context)
   at Sdl.TranslationStudio.Api.Editor.AbstractInternalDocument.SaveJobRequest.Execute(IJobExecutionContext context)
   at Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__46_0()
   at Sdl.Desktop.Platform.Implementation.Services.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>14.0.0.0</ProductVersion>

<EntryAssemblyFileVersion>14.1.10018.54792</EntryAssemblyFileVersion>

<OperatingSystem>Microsoft Windows 10</OperatingSystem>

<ServicePack>NULL</ServicePack>

<OperatingSystemLanguage>1031</OperatingSystemLanguage>

<CodePage>1252</CodePage>

<LoggedOnUser>translator</LoggedOnUser>

<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>

<ComputerName>SYS2019</ComputerName>

<ConnectedToNetwork>True</ConnectedToNetwork>

<PhysicalMemory>33553368 MB</PhysicalMemory>

</Environment>

</SDLErrorDetails>

Hello Gabriele Weyland-Tschentscher ,

Thanks for this- very useful.

As I suspected, this is because the files have been virtually merged as is most likely caused when one of the files has embedded content without any text at the beginning of the file.

Unfortunately I cannot provide a timescale when there will be a fix available for this ( although this has already been logged).

The only workaround at this time is to work with the files without virtually merging them.

Hi Steven,

Thanks for your analysis so far. What do you mean with "embedded content without any text at the beginnen of the file". Is that something we could get rid of in advance by prepping the word file?

Regards,

Judith

Hello Gabriele Weyland-Tschentscher,

If you indeed have the original source file, then you should be able to manipulate the file by either removing the embedded content or adding in extra text (beginning and end of each file) which will create a 'bookmark' that Studio recognises and then should split the virtually merged files again

I would of course recommend saving a copy of the originals first, before testing if this works for you.

Hello Gabriele Weyland-Tschentscher,

If you indeed have the original source file, then you should be able to manipulate the file by either removing the embedded content or adding in extra text (beginning and end of each file) which will create a 'bookmark' that Studio recognises and then should split the virtually merged files again

I would of course recommend saving a copy of the originals first, before testing if this works for you.

Hi Steven, do you mean the word or the xliff file?

Regards

Judith

Hello Gabriele Weyland-Tschentscher ,

The source word file - as this is where problem will originate from.