Description of Issue: 
Scribe® Online Agent cannot access FTP location specified in the TEXT Connector and receives an error: ApplicationException: Directory >remote directory path here< not found.  

This issue was reported by a customer whose connection was previously working.  They had recently renewed a windows Certificate for the FTPS location. When attempting to validate the location in the Text file source connection, a certificate window would appear in TIBCO Scribe® Online asking the user to accept or reject the certificate. The user would click accept and then the error (ApplicationException: Directory >remote directory path here< not found) would appear. In the connection window next to the validate button it would state "please validate your location" which had just been attempted, leading us to believe the certificate was not properly accepted and the location could not be validated. 

The FTP Connection was failing to connect with Error: ApplicationException: Directory >remote directory path here< not found.

TIBCO Scribe® Online

Troubleshooting the issue:

• Install an on-premise agent
• Enabled verbose logging for the on-premise agent in order to obtain additional information.
  • To enable verbose logging click on the agent being used from the agent section. When the Edit Agent window appears, check all boxes under agent logging to enable verbose logging.
• Test the connection again in the connection using the new agent. (The test should have the same outcome).
• Examine the agent logs and look for similar entries as seen below. 

 

1. The first log entry seen in the above image is for the FTP Certificate data Issuer which is sending the new certificate. 
2. The second log entry in the above image is for the FTP: Catch FtpsFingerprintInfoException being received by the agent. It states, Message: Invalid Certificate: UsertrustedRoot - A Certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. 

From the above information it appears that the certificate issued is not a trusted certificate. 

Resolution: Customer resolved this issue by generating a new certificate.