Esker Upload is Still Running... Ticket

When you see the "Esker upload is still running..." ticket in Freshdesk, it means Esker is trying to run its upload process (as it does every 2 min.) but there is another Esker process still running. Most of the time this is a timing issue where the last process does not complete in under 2 min for the next job to start.

If the "Esker upload still running" ticket comes in every 2 min. then there is a problem and we need to check that the Esker process is not aborted or orphaned. 

Check if Esker upload job is orphaned or aborted: 

1. Connect to UNIX (erpprod2.hagerco.com) 
2. Run the command "ps -ef | grep esker" to list all the Esker processes running. 
3. If only 1 entry is returned, there is nothing running. If there are a few listings displayed, you can use the "ptree" command to list the child processes of the process ID (PID) listed in step 2.
4. If any of the child processes are orphaned, escalate your user account to ROOT and kill off the PIDs to the cron job at the top of the tree. 
5. Reprocess the Esker CSV file if needed.
   • Using PuTTY, log in to G2 (erpprod2.hagerco.com). Navigate to /g2/prod/userdata/scripts/esker/eskerdone and look for the CSV file for the Esker order.
     • Use the command: ls -Al OrderCSV'EskerNumber.csv (Ex.  ls -Al OrderCSV1000678741175949460.csv)

   • Move the CSV file to the Esker Temp directory. (UNIX command 'mv' is used to move files)

     • mv  OrderCSV1000678741175949460.csv ../eskertemp

   • There is a cron job that looks for Esker orders in the eskertemp directory every 2 minutes. Once the file is moved, the cron job will grab the CSV file and reprocess the file.  You can run the select statements from step 1 to verify that the Esker order now has a SO number created.