• State Not Answered
  • Replies 1 reply
  • Subscribers 392 subscribers
  • Views 73 views
  • Users 0 members are here
Options
Related

Trados API Extraction Failure: File Version Could Not Be Identified: New Case Comment

Dpto. Tecnico Linguaserve

Hello:

We are launching a process from the Trados API to read the contents of an SDLXLIFF file, and it is returning an error that we are unable to identify:

Error while extracting data from 8950d65b-9b65-4160-9389-410ee8109862: An error occurred while trying to determine the file version.
at Sdl.ProjectAutomation.FileBased.FileBasedProject..ctor(String projectFilePath)
at ApiTAO.Tasks.FileExtractionData.FileExtractionDataTask.ExtractData(String projectPath, String fileId)

We are unable to determine the cause of the error because, apparently, everything in the SDLXLIFF file looks correct.

How can we get more information about the possible issue? Could you help us?
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi  , 

    A few important points:

    • The error is thrown when constructing Sdl.ProjectAutomation.FileBased.FileBasedProject, i.e. while trying to read the project metadata and determine the project/version. This is often unrelated to what “looks OK” inside the SDLXLIFF.
    • The stack trace includes ApiTAO, which I don’t recognize, what is this?. Also, this looks like it may be a standalone project automation process running outside Studio, so the execution context and referenced assemblies/versions matter.

    To get started, could you please share:

    • A minimal reproducible package:
      • ideally the full project folder including the .sdlproj and the SDLXLIFF that triggers the issue (not just the SDLXLIFF).
    • Your Trados Studio version/build and the version used to create the project.
    • The exact input values you pass (the projectPath and fileId), and confirm whether projectPath points to the .sdlproj.
    • The full exception output (ex.ToString()), including inner exceptions.
    • A small code snippet / repro project showing how you instantiate FileBasedProject and how you resolve/load the Trados assemblies (especially if running as a service or on a server).

    If you prefer to send this information privately, please send a link where I can download the files to phartnett@rws.com

    Patrick Andrew Hartnett | Developer Experience | Team Lead | RWS Group

Reply
  • 0

    Hi  , 

    A few important points:

    • The error is thrown when constructing Sdl.ProjectAutomation.FileBased.FileBasedProject, i.e. while trying to read the project metadata and determine the project/version. This is often unrelated to what “looks OK” inside the SDLXLIFF.
    • The stack trace includes ApiTAO, which I don’t recognize, what is this?. Also, this looks like it may be a standalone project automation process running outside Studio, so the execution context and referenced assemblies/versions matter.

    To get started, could you please share:

    • A minimal reproducible package:
      • ideally the full project folder including the .sdlproj and the SDLXLIFF that triggers the issue (not just the SDLXLIFF).
    • Your Trados Studio version/build and the version used to create the project.
    • The exact input values you pass (the projectPath and fileId), and confirm whether projectPath points to the .sdlproj.
    • The full exception output (ex.ToString()), including inner exceptions.
    • A small code snippet / repro project showing how you instantiate FileBasedProject and how you resolve/load the Trados assemblies (especially if running as a service or on a server).

    If you prefer to send this information privately, please send a link where I can download the files to phartnett@rws.com

    Patrick Andrew Hartnett | Developer Experience | Team Lead | RWS Group

Children
No Data