Error in Export to Excel smart service - No such file or directory

Hi,
I am using Export SQL to Excel node and I am getting below error in one of the environment
'There is a problem with task “Export SQL to Excel” in the process “APP_Scheduled Extract”. The following error was raised by the Export to Excel function: java.io.IOException: No such file or directory'.

The same model is working fine in environment 1 and not working in environment 2. Both environments are on premise and both have same version of plugin.
Could you please let me know what is causing the issue here.

OriginalPostID-258562



  Discussion posts and replies are publicly visible

Parents
  • The issue could be related to how apache POI library is managing java.io.tmpdir.
    The Export SQL to Excel smart service makes use of apache POI library to create files. This plugin works based on the assumption that the system environment is only utilized by Appian product. If there is any other Java applications/scripts utilizing apache POI in the same server then restarting of this application/script in the same system will cause this POI to remove default poifiles directory under the defined java tempdir, which only gets created during the JVM startup and deleted on JVM shutdown.
    If there is such an application/script utilizing Apache POI, then it would be best to isolate these two conflicting applications to its own tempdir. This can be set to each JVM startup script.
    e.g. -Djava.io.tmpdir=/<NEW_TEMP>, where <NEW_TEMP> is persistent directory accessible by appian user. Or you can apply similar concept to isolate other Java applications/script to use its own tempdir.
Reply
  • The issue could be related to how apache POI library is managing java.io.tmpdir.
    The Export SQL to Excel smart service makes use of apache POI library to create files. This plugin works based on the assumption that the system environment is only utilized by Appian product. If there is any other Java applications/scripts utilizing apache POI in the same server then restarting of this application/script in the same system will cause this POI to remove default poifiles directory under the defined java tempdir, which only gets created during the JVM startup and deleted on JVM shutdown.
    If there is such an application/script utilizing Apache POI, then it would be best to isolate these two conflicting applications to its own tempdir. This can be set to each JVM startup script.
    e.g. -Djava.io.tmpdir=/<NEW_TEMP>, where <NEW_TEMP> is persistent directory accessible by appian user. Or you can apply similar concept to isolate other Java applications/script to use its own tempdir.
Children
No Data