Additional information: When I open my TM to view it there are very few segments, which leads me to believe that my translations (of which there are 5 years' worth) are not being saved into the TM where I thought they were being saved, but some place else unknown to me. Can anyone tell me how to proceed?

Hello Kelsie Pettit,

There could be a number of reasons why you are receiving this error- It is a good idea to post the full error stack and this gives us a better insight into the possible causes.

If for instance, Studio wasn't closed down properly, it is possible the AVAST cleanup has permanently deleted essential temp files. 

The following Gateway article may also be helpful.

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0029080

When you translate and confirm the segments, these are stored in the TM that you are using for the project.

However you must have UPDATE enabled for this to happen

Studio will not save the translations to any other location other than the TM's within the project.

I have successfully repopulated the translation using the project TM. However, I am still thrown the same error message when attempting to preview or Save Target As. Does the file stack help reveal the problem?

Hi Kelsie Pettit ,

Thanks, this is really helpful.

The error does indeed indicate an error with the temporary files as suspected.

When working with Studio, temporary files are created whilst working and are needed until you save the file and close Studio. If these temp files are deleted, then this will cause issues. It's unlikely you can retrieve the temp files after such a deep clean unfortunately.

You should, however, be able to recreate the project using the original source files- I would copy these and give them a slightly different name.

Now recreate the project (using a slightly different name) and if you can find the TM that you used and which hopefully was updated, you can run a BatchTask- Pretranslate.

Hi Kelsie Pettit ,

Was just replying as you sent this last message.

To test the file- Use the Transate Single file option- open the file in the Editor and then immediately (do not translate anything) Save Target As- if you have issues at this stage, then the file is most likely corrupted.

You can take the original file and resave it (again use a slightly different name) and run this through Studio (single file) once again.

I would also recommend updating top the latest Studio version (Help>Check for updates) and also ensure your PC is completely up to date.

https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/3392/how-to-part-1-trouble-shoot-unexplained-errors-and-unwanted-behaviour-in-studio-multiterm

Hi Steven,

I've reloaded the project that was sent to me by the client and repopuated the translation, but still get the same error when I try to preview/Save Target As.

Hi again Steven,

How do I use the translate single file option with project files to run this test? The client sent me a Trados project file.

This also seems to be affecting my old projects. Here is the error I receive when attempting to preview an old translation. Is this the same problem?

<SDLErrorDetails time="6/10/2020 12:35:10 PM">
  <ErrorMessage>The system cannot find the file specified</ErrorMessage>
  <Exception>
    <Type>System.ComponentModel.Win32Exception, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <NativeErrorCode>2</NativeErrorCode>
    <ErrorCode>-2147467259</ErrorCode>
    <HelpLink />
    <Source>System</Source>
    <HResult>-2147467259</HResult>
    <StackTrace><![CDATA[   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at Sdl.FileTypeSupport.Framework.PreviewControls.MsOfficeExternalPreviewApplication.LaunchApplicationForFile(TempFileManager managedTempFile)
   at Sdl.FileTypeSupport.Framework.PreviewControls.GenericExteralPreviewApplication.Launch()
   at Sdl.TranslationStudio.Editor.Previews.ViewPreviewManager.ShowApplicationPreview(IManagedPreview preview)
   at Sdl.TranslationStudio.Editor.Previews.ViewPreviewManager.JobRequest_PreviewGenerated(ITranslatableDocument document, IManagedPreview activePreviewType, PreviewTempFileGenerator tempFileGenerator, GenerateType generateType)
   at Sdl.TranslationStudio.Editor.Previews.GeneratePreviewJobRequest.AfterExecute(IJob job)
   at Sdl.Desktop.Platform.Implementation.Services.Job.FinalizeJob()
   at Sdl.Desktop.Platform.Implementation.Services.JobService.ExecuteJobWithProgress(IExecutableJob job)
   at Sdl.Desktop.Platform.Implementation.Services.JobService.ScheduleJob(IJobRequest jobRequest)
   at Sdl.TranslationStudio.Editor.Previews.ViewPreviewManager.GeneratePreview(PreviewSetInfo previewSetInfo, GenerateType generateType)
   at Sdl.TranslationStudio.Editor.Previews.PreviewManager.GeneratePreview(GenerateType generateType)
   at Sdl.TranslationStudio.Editor.Previews.PreviewManager.RegeneratePreview(GenerateType generateType)
   at Sdl.TranslationStudio.Editor.Previews.AbstractExternalPreviewAction.GenerateExternalPreview(GenerateType type)
   at Sdl.TranslationStudio.Editor.Previews.ExternalPreviewTargetAction.Execute()
   at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass30_0.<ExecuteAction>b__0()
   at Sdl.Desktop.Logger.Log.Resources(Object message, Action action)
   at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
   at Sdl.Desktop.Platform.WinForms.IgCommandBarAction.Execute()
   at Sdl.Desktop.Platform.WinForms.IgCommandBarAction._lazyButtonTool_ToolClick(Object sender, ToolClickEventArgs e)
   at Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick(ToolClickEventArgs e)
   at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnToolClick(ToolClickEventArgs e)
   at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.FireEvent(ToolbarEventIds id, EventArgs e)
   at Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick()
   at Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.DoClickProcessing(MouseEventArgs e)
   at Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.OnMouseUp(MouseEventArgs e)
   at Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)
   at Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)
   at Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e)
   at Infragistics.Win.UltraWinToolbars.UltraToolbarsDockArea.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>15.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>15.2.6.2831</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>LAPTOP-1108AHKM\kelsi</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>LAPTOP-1108AHKM</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8243596 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Hi Kelsie Pettit, ,

Yes-the errors are identical and are both originating from the temp file manager.

I don't mind having a look at the package- you can send it to me if you wish- (swhale@sdl.com)

You can look at the files within the package by simply copying and saving the .sdlppx and renaming this from.sdlppx to .zip

Now you can unzip the package and look at the files.

I, however, do recommend you update everything as suggested here as I firmly believe that AVAST cleanup may have caused this.

https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/3393/how-to-part-2-trouble-shoot-unexplained-errors-and-unwanted-behavior-in-studiomultiterm 

Hi Steven. Thanks for your continued help! Which package would you like to see? As this error seems to be affecting all of my old translations, I'm not sure which file to send you. Are you referring to the original project file that triggered this thread?

Hi Steven,

I seems that the problem may run deeper than Trados, since none of my Office applications will open. Interestingly, my version of Studio 2015 (which I kept on my machine just in case) now no longer opens either. I have posted on a Microsoft support forum to see if they can help.

Meantime, I have worked through all the steps on the update page that you sent me and the problem persists. Barring any Microsoft issues, do you have any more advice?

I have more information. Microsoft says this is a known issue and there will be a fix soon. I can Save Target As to Word from Trados, and then open my file using Office online. This is inconvenient but an acceptable workaround in the meantime to enable me to review documents in Office.

However, the fact that my old version of Studio no longer opens is interesting (and a bit worrying).

I have more information. Microsoft says this is a known issue and there will be a fix soon. I can Save Target As to Word from Trados, and then open my file using Office online. This is inconvenient but an acceptable workaround in the meantime to enable me to review documents in Office.

However, the fact that my old version of Studio no longer opens is interesting (and a bit worrying).