I get the error “Compression Error [rc=0]- program will be terminated” while running the BOT in unattended mode for SAP Automation. The SAP screen terminates post the compression error popup. Has anyone faced this issue in SAP Automation? Request to please share any solutions for this issue.
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Meet us and our users on our Community Slack and ask your question there.
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
I am facing the same issue when accessing table records in SAP using transaction SE16N. Additionally, I encounter the same error when trying to create a Z program.
Has anyone found a solution for this? Any help would be greatly appreciated.
Yes, I’ve encountered a very similar issue in SAP automation projects using UiPath, where SAP GUI crashes unexpectedly with errors such as:
“Compression Error [rc=0] - program will be terminated”
or an access violation dump like 0xC0000005 related to the sapfewdp.dll module.
Root Cause:
This issue occurs when the Enter key and F4 key are pressed with very little time gap, especially in input fields with F4 help when using SAP GUI’s Amodal F4 control.
Solution:
SAP has documented this behavior in the following official Note:
Update your SAP GUI to a patch level that includes the fix described in the note.
You can find the relevant patch info in the note or check Note 1053737 for estimated delivery dates of upcoming patches.
Introduce a short delay between pressing Enter and F4 in your automation — for example, 300–500 ms.In UiPath, you can add a Delay activity or set the DelayBefore property in Click, Type Into, or similar activities to introduce this pause.
Optional Workaround:
If the error happens inconsistently, you might also try disabling the Amodal F4 control in SAP GUI:
Go to SAP GUI Options → Interaction Design → Visualization → Disable: “Use modal F4 help instead of amodal”
Hope this helps resolve your issue. Let me know if you need a sample of how to implement the delay in UiPath!