Connect-FTP permission denied
Hello friends,
I have a scenario where we are using Docx4j (pzGenerateDocument) to dynamically create word documents. pzGenerateDocument creates these word documents in /usr/local/tomcat/work/Catalina/localhost/prweb/StaticContent/global/ServiceExport/<document.docx>. The goal is to send these files to the remote FTP server for which, I planned on using Connect-FTP method. However, when the system is trying to access the file to transfer them, I am seeing permission denied message. Has any one faced this problem?
If any one has any idea to resolve this, please let me know. Any help is greatly appreciated. Our application is hosted in pega cloud. Pega engineers tell us that system has full permissions over that folder.
Hello friends,
I have a scenario where we are using Docx4j (pzGenerateDocument) to dynamically create word documents. pzGenerateDocument creates these word documents in /usr/local/tomcat/work/Catalina/localhost/prweb/StaticContent/global/ServiceExport/<document.docx>. The goal is to send these files to the remote FTP server for which, I planned on using Connect-FTP method. However, when the system is trying to access the file to transfer them, I am seeing permission denied message. Has any one faced this problem?
If any one has any idea to resolve this, please let me know. Any help is greatly appreciated. Our application is hosted in pega cloud. Pega engineers tell us that system has full permissions over that folder.
Caused by: com.pega.pegarules.pub.services.ConnectorException: Error working with local path: '/usr/local/tomcat/work/Catalina/localhost/prweb/StaticContent/global/ServiceExport/Initial_Letter_FHCP__1548034117428.docx', Permission denied
at com.pega.pegarules.integration.engine.internal.connect.ftp.FTPConnectorImpl.invoke(FTPConnectorImpl.java:530) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.invokeFTPConnector(PRServiceUtils.java:3314) ~[printegrint.jar:?]
at com.pegarules.generated.activity.sh_action_createletterpdf_edc05987d0a309e070f8dbc5b92be8fd.step7_circum0(sh_action_createletterpdf_edc05987d0a309e070f8dbc5b92be8fd.java:705) ~[?:?]
at com.pegarules.generated.activity.sh_action_createletterpdf_edc05987d0a309e070f8dbc5b92be8fd.perform(sh_action_createletterpdf_edc05987d0a309e070f8dbc5b92be8fd.java:196) ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3556) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doAction(Executable.java:3286) ~[prprivate.jar:?]
at com.pegarules.generated.activity.ra_action_pyrunrecordexecute_025cb29e81d295d991d37ad8d1e40455.step2_circum0(ra_action_pyrunrecordexecute_025cb29e81d295d991d37ad8d1e40455.java:274) ~[?:?]
at com.pegarules.generated.activity.ra_action_pyrunrecordexecute_025cb29e81d295d991d37ad8d1e40455.perform(ra_action_pyrunrecordexecute_025cb29e81d295d991d37ad8d1e40455.java:88) ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3556) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10878) ~[prprivate.jar:?]
at com.pegarules.generated.activity.ra_action_pzrunrecordexecute_1ec91911c2bc6b1febb6466a70877c6c.step11_circum0(ra_action_pzrunrecordexecute_1ec91911c2bc6b1febb6466a70877c6c.java:1011) ~[?:?]
at com.pegarules.generated.activity.ra_action_pzrunrecordexecute_1ec91911c2bc6b1febb6466a70877c6c.perform(ra_action_pzrunrecordexecute_1ec91911c2bc6b1febb6466a70877c6c.java:246) ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3556) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:646) ~[prprivate.jar:?]
... 51 more
***Moderator Edit-Vidyaranjan: Updated SR details***
***Edited by Moderator Marissa to update platform capability tags****
Accepted Solution
Pegasystems Inc.
IN
Hi Abhinay,
From the related SR notes I'm glad to hear that the issue is fixed at your end.
Resolution notes say- "We determined the issue is with root folder not being available. "
The information will help fellow community users who come across the same concern.
Thanks!
Pegasystems Inc.
US
I have seen this type of issue before and the error can be misleading. Verify that the user being used to make the FTP connection has permission to write where it's attempting to place the file on the server. And note that the location you are specifying is relative to that user's home directory.
Checking the FTP server logs may provide useful information.
Accepted Solution
Pegasystems Inc.
IN
Hi Abhinay,
From the related SR notes I'm glad to hear that the issue is fixed at your end.
Resolution notes say- "We determined the issue is with root folder not being available. "
The information will help fellow community users who come across the same concern.
Thanks!