Salesforce

WorldServer - after moving to a new server and updating the "ftsserver_shared_directory" in all general.properties and FTS configuration files, we still get error "Dependency file... cannot be found. The file will be recorded as <external-file>

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer
Symptoms/Context
After the modification of the IP address of our FTS share, we have noticed that are still issues when saving. For example at the Save target or Save step, when manually saving in Browser Workbench for tasks belonging to projects created before the change, or when importing Return package in tasks belonging to projects created before the change.

The relevant entry in the engine.log can be found below.  XX.XX.XX.XX stands for the OLD IP address, which has now been replaced by the new IP address:

[2022-12-01 12:00:48,295] [WARN ] [FSE daemon 1 (370a08c) on host "wstftspro01n.ADI.WIPO.INT"] [1528] [Sdl.WorldServer.FileTypeSupport.Server.Dal.DatabaseWriter]: Dependency file \\XX.XX.XX.XX\WSCIFSPROD\WSMount\assets\source\ABS\AR-EN\_ABS_AR-EN_20221124_074640\XXXXX-ttad-000001-en-ar.xml cannot be found. The file will be recorded as <external-file>.

Obviously, the directory, folder and file names will vary. We have checked the configuration of all the relevant files as described in this article:

WorldServer - How to change the location of the DependencyFiles folder

and we confirm that all the relevant properties and FTS configuration files have been updated with the new IP address. The rest of the directory has not changed. The DependencyFiles folder or the project folders have not changed either. Why are we still receiving this error for projects created before the change?
Resolution
Resolution 1: Update statement to replace old server names or IP address etc in the BcmDependencyFileProperties table. In the query below, the old IP address is replaced with the new IP address:

Oracle:
update BcmDependencyFileProperties
set currentfilepath = regexp_replace(currentfilepath,'^\\\\10.32.2.9','\\\\10.32.4.93')
where currentfilepath like '\\10.32.2.9%';
commit;


Resolution 2: Manual Workaround for projects in Autoerror. Follow these steps:

1- Download the source file of the Task(s) in Autoerror
2- Export the Task(s) to a WSXZ package
3- Open the WSXZ package in Trados Studio
4- Once the package is opened and the WorldServer project is created in Trados Studio, open the file
5- You will be prompted with an alert asking you 

When opening the file in Studio, you will be prompted with a Dependency file not found alert asking you for some an xml file from a Temp directory with a temp file name:



6- Click Yes and browse to the location where you have stored the source XML file downloaded from WorldServer. Studio will want you to find an xml file with exactly that name. Ignore that, set the search to generic *xml and select the source xml file and click Open:

User-added image

7- The SDLXLIFF file will open correctly in Trados Studio. If you want to double check if all is fine, create a target file (File > Save target as...). If the target file is created without issue, all is good.
8- Now just go to File > Save or click on the Save document icon in Trados Studio to save your SDLXLIFF file. No need to add a manual change to any segment. It is enough to embed the source file.
9- In Trados Studio, select the project and create a WorldServer Return package
10- Import the Return package back into the WorldServer project and into the task in Autoerror. The import will be successful.
11- Complete the Autoerror. The error will be solved and the Task will move to the next step.
 
Root Cause
This issue happens if
  • A migration to a new server has been done
  • The hostname of a the server where the FTS shared directory is stored was changed
  • or the IP address of a the server where the FTS shared directory is stored was changed to a new one.
In all these 3 scenarios, an actual "move" away from the previous directory to a new one has been applied, rather than a change that requires a simple copy action. To fix any errors resulting from this change, an update in the "BcmDependencyFileProperties" table is required. This article provides more details for the DB side, and also provides a manual workaround as alternative to the DB table.
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by