Pretty much all of our processes that we run on a daily basis open SAP GUI from our company’s Intranet page. When opening the file for SAP GUI, Internet Explorer sometimes crashes with the following error:
The above screenshot is from our exception handler within the robot which takes a screenshot of the screen at the time of error.
We have been unable to recreate the error in order to generate a selector to manually close this every time it pops up however we have determined that this error is under the process name “WerFault.exe” and that it is not exclusive to Internet Explorer.
We are trying to figure out a way to close this error as we believe it is interfering with subsequent automations. Our two ideas are as follows:
Generate a selector for the close button to close the window.
Determine whether or not the process is a system protected process so that we can kill the process.
Any help with the issue would be massively appreciated with regards to a selector or information about the error.
I recommanded to cmd ‘sc stop WerSvc’ to administrator privileges. or run eventvwr (Windows Log-Application) and check the log at the time of the error.
We are getting quite frequent WeFault.exe application error with SAP (WerFault not being able to start) and if we disable Windows error reporting, it changes to DDE Server Window: explorer.exe - System Warning. Unkown Hard Error. This happens when SAP GUI is running and robot is performing some activity. But it is not a specific activity, can be e.g. starting a transaction, running a report etc. Any ideas where to begin troubleshooting / solving? Strage thing is that it started quite recently and at least on three different machines so it is not a machine specific thing like corrupted OS / files system…
Thanks, we did try with disabling the error reporting service already a while ago. But that just changed the error “Unkown Hard Error”
So one error changes to a different one.
I think we might have a corrupted file system. No idea how that has happened all of a sudden to at least three machines (with common denominator of UiPath version upgrade done about the time when the problems started)…