This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The process cannot access the file ... because it is being used by another process!

SDL Trados Studio 2017 SR1 - 14.1.6413.8
During the past 2 weeks, when trying to open files for translation I often get the message:

 

The process cannot access the file ... because it is being used by another process

If I try a few times, it eventually opens

If I try and open multiple files (say 10) at a time I always get the message.

The issue does not go away after shutting Studio, it does not go away after reboot/shutdown, and it happens on all projects from many different customers

HELP!

SDLERROR XML Attached

<SDLErrorDetails time="04/02/18 8:10:07 AM">
  <ErrorMessage>The process cannot access the file 'C:\Users\jaddess\AppData\Local\Temp\hrlfu5fq.xz3\ijdhyo4t.ijp.ttx' because it is being used by another process.</ErrorMessage>
  <Exception>
    <Type>System.IO.IOException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>mscorlib</Source>
    <HResult>-2147024864</HResult>
    <StackTrace><![CDATA[   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
   at System.IO.File.OpenFile(String path, FileAccess access, SafeFileHandle& handle)
   at System.IO.File.SetLastWriteTimeUtc(String path, DateTime lastWriteTimeUtc)
   at Sdl.FileTypeSupport.Framework.Core.Settings.FileSerializer.UnzipFile(Stream zipStream)
   at Sdl.FileTypeSupport.Framework.Core.Settings.FileSerializer.UnzipExternalFile(String filePath)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.AddEmbeddedFile(internalfile internalFileElement, IDependencyFileProperties file)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.OnDependencyFiles(XmlElement dependencyFiles)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.<ContinueScanning>b__c(ISdlXliffStreamContentHandler handler)
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.ContinueScanning()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ContinueParsing()
   at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.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.TranslatableDocument.Load(IJobExecutionContext context)
   at Sdl.Desktop.Platform.Services.JobRequest.Execute(IJobExecutionContext context)
   at Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__3()
   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.6413.8</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1255</CodePage>
    <LoggedOnUser>COUGER-2018\jaddess</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>COUGER-2018</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16695772 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>




[locked by: Steven Whale at 2:17 PM (GMT 0) on 26 Feb 2020]
Parents Reply
  • The point is that there is no universal recipe... it always depends on multiple factors, the main one being WHY is the file locked by the antimalware... which is basically impossible to tell if you are not the programmer of the actual antimalware.
    It could(!) help if you whitelist the actual Studio executable... if by doing this the particular antimalware excludes ALSO FILES created by that executable... which is not something what can be told universally.

    Definitely, excluding the entire TEMP folder is bad and short-sighted idea.
    Not mentioning that telling the users to exclude "this particular folder" is also wrong... the TEMP and TMP folder locations and names can be redefined in the OS and the folders may be located somewhere else and be named completely differently.
Children
No Data