Trados hangs when trying to add RTF file using API

Hi!

I'm trying to add RTF file to project. While converting it to translatable format with:

project.RunAutomaticTask(new Guid[] { fileGuid }, AutomaticTaskTemplateIds.ConvertToTranslatableFormat);

Trados just hangs. In the log file I can see:

INFO  2014-01-24 03:01:44 ConversionTask                 – ProcessFile: c:\Project Folder\TRUNK_2_aa [EN]-[IT] 2014_145_4\en-GB\test.rtf
INFO  2014-01-24 03:01:44 ConversionTask                 – ProcessFile: getting filter manager
INFO  2014-01-24 03:01:44 ConversionTask                 – ProcessFile: getting converter

Using Windows 8 Task Manager I can see that Trados spawns new Microsoft Word process, which is all the time doing something using CPU.

The problem doesn't occur while creating project using SDL Trados GUI. Then, RTF files are converted properly.

The problem occured on both SDL Trados 2011 and SDL Trados 2014. Microsoft Word version is 2010.

Thanks for help!
Parents
  • Hi,

    Open the options in Word and add the location where you store your projects (including subfolders) as Trusted Location.

    File --> Options --> Trust Center --> Trust Center Settings... --> Trusted Locations

    I wrote a command-line tool. When I invoke that directly, then it can process RTF files.

    I hope this works for you! Please let me know.

    However, I am still having another (related) problem. When I send an RTF-file via a webservice (POST), receive it and then invoke the command line tool, I still get the problem that you mention. When I kill the processes (Winword and my service), and remove the proj-folder that Studio created, then I can invoke my command line tool. The tool then converts the RTF without any issue. Does anyone have a clue?

    Kind regards,

    Henk Boxma

  • Hi,

    It looks like that Studio is using DCOM when it converts RTF. When you convert other Office-documents, then the Winword process is not started. Microsoft writes the following:

    "Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment."

    This may be the reason that RTF conversions do not work with the Studio Automation framework.

    Kind regards,

    Henk

  • Hi,

    I found it after days of trial and error and here is my answer for free :-)

    You need to do the following:

    1. Create a folder named "Desktop" in C:\Windows\SysWOW64\config\systemprofile".

    2. Set the identify of Word to "The interactive user" (see also http://www.verydoc.com/others/configure%20office%20applications%20to%20run%20under%20the%20interactive%20user%20account.htm)

    1. Start DCOMCNFG. 

    2. Select DCOM Config --> Microsoft Word 97 - 2003 Document

    3. Right click to get the properties

    4. Identity tab: Select "The interactive user"

    3. Set the folder where you store your projects as Trusted location in Word (also for  Excel and Powerpoint if you need to convert those).

    Hope this helps!

    Thanks,

    Henk

Reply
  • Hi,

    I found it after days of trial and error and here is my answer for free :-)

    You need to do the following:

    1. Create a folder named "Desktop" in C:\Windows\SysWOW64\config\systemprofile".

    2. Set the identify of Word to "The interactive user" (see also http://www.verydoc.com/others/configure%20office%20applications%20to%20run%20under%20the%20interactive%20user%20account.htm)

    1. Start DCOMCNFG. 

    2. Select DCOM Config --> Microsoft Word 97 - 2003 Document

    3. Right click to get the properties

    4. Identity tab: Select "The interactive user"

    3. Set the folder where you store your projects as Trusted location in Word (also for  Excel and Powerpoint if you need to convert those).

    Hope this helps!

    Thanks,

    Henk

Children
No Data