• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 435 subscribers
  • Views 1272 views
  • Users 0 members are here
Options

"The specified path is invalid" error in "Backup Translation Memory" in Fragment Alignment Support, on Mac OSX.

Rachel McLaughlin

Any help much appreciated.

Mac OSX 10.13 running Parallels Desktop running SDL Trados Studio 2019. 

Fragment Matches delivers no results.

Attempted fix: Project Settings->Translation Memory->Fragment Alignment->Fragment Alignment Status->toggle from ON to OFF then back ON->pop-up Fragment Alignment Support "Do you want to proceed?"->Yes->pop-up Fragment Alignment Support: first step, "Backup Translation Memory", fails, with message "The specified path is invalid"->View Log File:

-----------------------------------------------

Backup Translation Memory (22/5/19 12:33:40 am)

-----------------------------------------------

Backup location: \\Mac\Home\Documents\Studio 2019\Translation Memories\MSS_March19.sdltm.000.bak

Process failed (22/5/19 12:33:41 am)

System.IO.IOException: The specified path is invalid.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

   at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost)

   at System.IO.FileInfo.CopyTo(String destFileName, Boolean overwrite)

   at Sdl.TranslationStudio.Common.Helpers.FileService.CopyTo(String existingFilePath, String newFilePath, Boolean overwrite)

   at Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoryAutomation.Jobs.BackupTranslationMemoryJobRequest.Execute(IJobExecutionContext context)

-----------------------------------------------------------

Update translation memories finished. (22/5/19 12:33:41 am)

-----------------------------------------------------------
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Greetings,

    Fellow Mac and Parallels user here. I have seen a similar error caused by Parallels file paths. (Specifically, I cannot upgrade TMs at present due to a current bug in 2019 probably related to this.)

    As a recourse, try moving your TM (or other files you are using) to a "local" location in your virtual machine, somewhere like C:\Example.

    Studio has had problems with this in the past, and I hope it is fixed in an update. FYI, Studio 2017 seems not to be affected.

    Best wishes,

    MMM