Hi, has this issue been resolved in the meantime? A team mate of mine has the same issue (error log below) in Studio 2017 SR2 CU 17. 

Otherwise could you also please open a support ticket for us? She can't close Studio either for fear of losing hours of work.

<SDLErrorDetails time="03/08/2022 09:06:51">
<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.AlignmentEditor</Source>
<HResult>-2147467261</HResult>
<StackTrace><![CDATA[ at Sdl.TranslationStudio.AlignmentEditor.Jobs.SaveAlignmentJobRequest.SaveAlignment(SdlAlignPackage package)
at Sdl.TranslationStudio.AlignmentEditor.Jobs.SaveAlignmentJobRequest.ExecuteJob(IJobExecutionContext context)
at Sdl.TranslationStudio.AlignmentEditor.Jobs.AlignmentJobRequest.Execute(IJobExecutionContext context)]]></StackTrace>
</Exception>
<Environment>
<ProductName>SDL Trados Studio</ProductName>
<ProductVersion>14.0.0.0</ProductVersion>
<EntryAssemblyFileVersion>14.1.10017.54688</EntryAssemblyFileVersion>
<OperatingSystem>Microsoft Windows 10 Enterprise</OperatingSystem>
<ServicePack>NULL</ServicePack>
<OperatingSystemLanguage>1033</OperatingSystemLanguage>
<CodePage>1252</CodePage>
<LoggedOnUser>DESEY\frdoc</LoggedOnUser>
<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
<ComputerName>DE4008518W1</ComputerName>
<ConnectedToNetwork>True</ConnectedToNetwork>
<PhysicalMemory>32834620 MB</PhysicalMemory>
</Environment>
</SDLErrorDetails>

Paul Ceronio 

Paul Ceronio said:

Hi, has this issue been resolved in the meantime? A team mate of mine has the same issue (error log below) in Studio 2017 SR2 CU 17. 

Otherwise could you also please open a support ticket for us?

The 2017 version is long out of support.  I suggest you at least update it as you are not on the last version:

Trados Studio 2017 SR1 - 14.1.10018.54792
MultiTerm 2017 SR1 - 14.2.8.55461

Then if yo still have a problem please open a new thread as we can't create a case for you when you piggy back on someone else's thread.

Paul Ceronio 

Paul Ceronio said:

Hi, has this issue been resolved in the meantime? A team mate of mine has the same issue (error log below) in Studio 2017 SR2 CU 17. 

Otherwise could you also please open a support ticket for us?

The 2017 version is long out of support.  I suggest you at least update it as you are not on the last version:

Trados Studio 2017 SR1 - 14.1.10018.54792
MultiTerm 2017 SR1 - 14.2.8.55461

Then if yo still have a problem please open a new thread as we can't create a case for you when you piggy back on someone else's thread.

Hi Paul,

Thanks for the advice. We are in the process of upgrading to Studio 2021, but in a company like ours, it takes ages to jump though all the hoops.

Paul Ceronio 

Paul Ceronio said:

We are in the process of upgrading to Studio 2021, but in a company like ours, it takes ages to jump though all the hoops.

I know the problem!  And you're in the process of upgrading to a version that is also old... but at least it's still supported!