Automate.exe has stopped working
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
30-04-19 03:17 PM
Hi
We have a particular process which occasionally causes the error; 'Automate.exe has stopped working'.
This causes the process to stop and the virtual machine to freeze. The resource shows in the Control Room as 'Not Responding' and must have manual intervention to have the resource come back online.
The error does not always occur at the same stage of the process or when calling the same Business Object/Action.
Has anyone else experienced an issue like this and do you have any hints for avoiding the issue?
Thanks
Chris
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
30-04-19 03:24 PM
Does it happen inside of a specific process only or across several?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
30-04-19 05:06 PM
Check Windows Application Eventlog for .NET Framework crashing. This usually causes Blue Prism to crash and/or freeze making the resources show as not responding or missing status.
Br,
Petri Kaukua
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
13-05-19 09:33 PM
Thanks for the replies. Ben_M31 - it is happening mostly on one particular process, however we have had instances of it occurring on other processes too.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
13-05-19 10:47 PM
Are you using MAPIEx by any chance? This has been the single most cause for crashes that we've seen, outside of memory overflows with large collections.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
13-05-19 11:25 PM
Try the event log of the offending machine for clues, switch on memory logging to look for creep, and review the process for any 'over ambitious' logic such as unfettered polling loops, excess logging, incomplete close down of apps (eg Excel), Db connections left open, multiple instances of large collections etc, etc.
