Hey @ElisandroM,
When you send an outgoing file by BatchFacility "BPBATCH.exe" and the EPOUT file is generated without content, but it works when started manually by the Interface (EPWIN400), it indicates there might be a discrepancy in the execution environment or configuration between the batch and manual processes. Here are some steps to troubleshoot and resolve the issue:
1. Check Configuration: Ensure that the BatchFacility (BPBATCH.exe) configuration is consistent with the manual process configuration used by EPWIN400. Look for any environment variables, permissions, or settings that might differ.
2. Log Files: Review the log files generated by BPBATCH.exe for any errors or warnings that could provide insights into why the EPOUT file is empty.
3. Permissions: Verify that the BatchFacility process has the necessary permissions to access all required resources and files.
Hey @fazakascsaba,
Thank you for sharing your automated solution for handling uploads/downloads. For those looking to automate the Edit Package process, @fazakascsaba has developed a solution that can eliminate the need for interactive starts:
- Automated Solution for Edit Package
If anyone needs guidance on implementing this script, @fazakascsaba has offered to assist.
Hey @Robas,
You mentioned the "Batch Utilities" functionality in Edit Package, which allows configuring automations such as downloading/uploading files from/to VISA via EAS or DEX. This feature could indeed help @ElisandroM and others facing similar issues. Configuring Batch Utilities might ensure consistent execution settings and resolve the problem with the EPOUT file generation.
Hey @jorge683,
As of now, the community has provided several potential solutions to address the issue with the EPOUT file generation and to automate the Edit Package process. Here is a summary of the suggestions:
1. Troubleshoot BatchFacility (BPBATCH.exe) Configuration: Ensure that the configuration is consistent with the manual process.
2. Review Log Files: Check for any errors or warnings in the logs.
3. Check Permissions: Make sure BatchFacility has the necessary permissions.
4. Automated Solution by fazakascsaba: Consider using the PowerShell script provided by fazakascsaba to automate the process.
5. Batch Utilities: Explore the "Batch Utilities" functionality in Edit Package for configuring automations.
By following these steps and utilizing the shared resources, you should be able to resolve the issue and achieve effective automation for your Edit Package processes.
Feel free to reach out for further guidance or support as needed!
Thanks,
Diana
Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.
