Description:
TIBCO Adapter for Files(FA) throws the following error after deployment and stops.

"Startup error. SDK Error: Repository Path  caused a repository exception. NodeNotFoundException
  Node = /tibco/private/adapter/Adapter/ADF/<Adapter-InstanceName> RepoException node does not exist".

where Node indicates a missing node name which is usually an adapter instance name in the deployment generated DAT file.

Symptoms:
Error seen in log file and FA stops.
Cause:
When TIBCO Adapter for Files (FA) is deployed, the administrator/tra generate .tra, .sh and .DAT files are used to start the adapter. If the DAT file does not have the mentioned Node, then the file adapter will throw the error. A reason for the missing reference in the DAT file is that it is missing the TIBCOadaptermappers.jar  and  designerobjectrepomapper.jar files under the  <tibco-home>\tra\5.8\lib\repository_mappers folder on the primary admin.

Workaround:
==========
If multple environments exist then a working DAT from a working environment to a non working environment can be tried. Contact TIBCO Support for more details. For most adapters, the above two files are needed on the machine on which the deployment is triggered. If the deployment is triggered from the Admin GUI, then the two files are needed on the Admin machine to avoid the exception. If the deployment is done using AppManage, then the two files are needed on the machine on which the AppManage command is executed.

"Startup error. SDK Error: Repository Pathcaused a repository exception. NodeNotFoundExceptionNode = /tibco/private/adapter/Adapter/ADF/;Adapter-InstanceName; RepoException node does not exist".