I am seeing sporadic instances where an AE11 WF executes and the BPATASK.EXE process is not ended. See the attached screenshot where it shows the offending process still active even though AE11 is not executing any task. The condition will remain present until the process is manually killed. New tasks (either scheduled or via a trigger) do not appear to always execute when this occurs. We are currently running BPA 10 in parallel and have not experienced this issue with BPA10, it only appears to be in AE11. I haven't found a way to replicate this issue on demand. It occurs frequently enough to halt our continued migration from BPA 10 to AE11.


Windows Server 2008R2 64 bit
Automate Enterprise 11.0.1.17

Hello,

Would it be possible to set-up a GoToAssist session where we can take a closer look at this issue? If this is possible please send an email over to AutoMate.Support@helpsystems.com with a list of your availability.

Note: Please reference this forum thread in your email.


-------------------------

Ricardo Castaneda | Principal Support Analyst
AutoMate | Division of HelpSystems
HelpSystems, LLC | T: +1.213.738.1700

I will do that. I think I am seeing a pattern of some sorts. The error message below appears to be reporting each time after the BPATASK.EXE process is manually killed. The task name appears to be irrelevant as i have seen the same error now on multiple tasks which are unrelated in steps they are performing. The error message is always the same, regardless of the task name flagged.

"Task 'SEND SMS' running on agent 'USDAPRODAPP001' failed because: Fatal execution exception: The target element corresponds to UI that is no longer available (for example, the parent window has closed).
at MS.Internal.Automation.Misc.ThrowWin32ExceptionsIfError(Int32 errorCode)
at MS.Internal.Automation.Misc.SendMessageTimeout(HWND hwnd, Int32 Msg, IntPtr wParam, IntPtr lParam)
at MS.Internal.Automation.HwndProxyElementProvider.System.Windows.Automation.Provider.IRawElementProviderSimple.GetPropertyValue(Int32 propertyId) (Step -1 in function )"

Hello EJ,

Does the BPATask.exe process tend to get "stuck" during off work hours or overnight execution? If so, there may be an issue with a auto logon attempt that is causing the issue.

We look forward to receiving your meeting request.

-------------------------

Alex Escalante | Support Analyst
AutoMate | Division of HelpSystems
HelpSystems, LLC | T: +1.213.738.1700 | F: +1.213.738.7665

I have sent availability times to Automate support e-mail.

I haven't seen any pattern necessarily with timing. Our server executing these tasks is continually logged in (screen saver/lock screen disabled) so it shouldn't be a logon issue unless I am misunderstanding your statement.

Hello Ej,

A rep will reach out shortly, we will work with you via the Case and update the thread as we address the issue.

-------------------------

Ricardo Castaneda | Principal Support Analyst
AutoMate | Division of HelpSystems
HelpSystems, LLC | T: +1.213.738.1700

Hi

Has this issue been resolved?

I've noticed the same issue after upgrading to AE11.

I still have the issue as of AE11.0.6.11. I was informed the issue had something to do with the way we are using RDP and VNC. However, it only occurs on the server I am running the execution and management servers on. All of my other servers are setup the same way in regards to RDP via console session and VNC to allow for multiple users to access the machine as needed.

Hello EJ,

Different environments can produce different results, however one constant is logging off and/or locking the machine. Which is being done after the user logs in and leaves? Is anyone disconnecting the session?

A disconnected session is one of the most common reasons why the bpatask.exe process gets stuck.

-------------------------

Alex Escalante | Support Analyst
AutoMate | Division of HelpSystems
HelpSystems, LLC | T: +1.213.738.1700 | F: +1.213.738.7665