MAPIEx 2.0.6 Exception cause Automate.exe terminated

[Anonymous]

use MAPIEx 2.0.6 VBO  send mail  cause  Automate.exe  terminated   System : win10 pro version : 1803 OS:17134.48  outlook 2013 bp version : 6.2.1   detail error msg as attachment .  please help.     Automate.exe Framework version: v4.0.30319 description: Processing  terminated  System.AccessViolationException    æ–¼ BluePrism.WindowsAutomation.MAPIEx.NetMAPI.MAPILogout(IntPtr)    æ–¼ BluePrism.WindowsAutomation.MAPIEx.NetMAPI.Logout()    æ–¼ BluePrism.WindowsAutomation.MAPIEx.NetMAPI.Dispose(Boolean)    æ–¼ BluePrism.WindowsAutomation.MAPIEx.NetMAPI.Dispose()    æ–¼ Blue_Prism_MAPIEx.SendMail_Code(System.String, System.String, System.String, System.String, System.String, System.String, System.String, Boolean ByRef, System.String ByRef)     例外狀況資訊: System.Reflection.TargetInvocationException    æ–¼ System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)    æ–¼ System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])    æ–¼ System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)    æ–¼ BluePrism.AutomateProcessCore.clsCompilerRunner.Execute(BluePrism.AutomateProcessCore.Stages.clsCodeStage, BluePrism.AutomateProcessCore.clsArgumentList, BluePrism.AutomateProcessCore.clsArgumentList, System.String ByRef)    æ–¼ BluePrism.AutomateProcessCore.Stages.clsCodeStage.Execute(System.Guid ByRef)    æ–¼ BluePrism.AutomateProcessCore.clsProcess.RunStep(BluePrism.AutomateProcessCore.clsProcessBreakpointInfo ByRef, Boolean)    æ–¼ BluePrism.AutomateProcessCore.clsProcess.RunAction(RunActions, BluePrism.AutomateProcessCore.clsProcessBreakpointInfo ByRef, Boolean)    æ–¼ BluePrism.AutomateProcessCore.clsVBO.DoDoAction(System.String, BluePrism.AutomateProcessCore.clsProcessStage, BluePrism.AutomateProcessCore.clsArgumentList, BluePrism.AutomateProcessCore.clsArgumentList ByRef)    æ–¼ BluePrism.AutomateProcessCore.clsBusinessObject.DoAction(System.String, BluePrism.AutomateProcessCore.clsProcessStage, BluePrism.AutomateProcessCore.clsArgumentList, BluePrism.AutomateProcessCore.clsArgumentList ByRef)    æ–¼ BluePrism.AutomateProcessCore.Stages.clsActionStage.Execute(System.Guid ByRef)    æ–¼ BluePrism.AutomateProcessCore.clsProcess.RunStep(BluePrism.AutomateProcessCore.clsProcessBreakpointInfo ByRef, Boolean)    æ–¼ BluePrism.AutomateProcessCore.clsProcess.RunAction(RunActions, BluePrism.AutomateProcessCore.clsProcessBreakpointInfo ByRef, Boolean)    æ–¼ BluePrism.AutomateProcessCore.clsVBO.DoDoAction(System.String, BluePrism.AutomateProcessCore.clsProcessStage, BluePrism.AutomateProcessCore.clsArgumentList, BluePrism.AutomateProcessCore.clsArgumentList ByRef)    æ–¼ BluePrism.AutomateProcessCore.clsBusinessObject.DoAction(System.String, BluePrism.AutomateProcessCore.clsProcessStage, BluePrism.AutomateProcessCore.clsArgumentList, BluePrism.AutomateProcessCore.clsArgumentList ByRef)    æ–¼ BluePrism.AutomateProcessCore.Stages.clsActionStage.Execute(System.Guid ByRef)    æ–¼ BluePrism.AutomateProcessCore.clsProcess.RunStep(BluePrism.AutomateProcessCore.clsProcessBreakpointInfo ByRef, Boolean)    æ–¼ BluePrism.AutomateProcessCore.clsProcess.RunAction(RunActions, BluePrism.AutomateProcessCore.clsProcessBreakpointInfo ByRef, Boolean)    æ–¼ BluePrism.AutomateProcessCore.clsProcess.RunAction(RunActions)    æ–¼ BluePrism.AutomateAppCore.clsListener+clsRunnerRecord.RunnerMethod()    æ–¼ System.Threading.ThreadHelper.ThreadStart_Context(System.Object)    æ–¼ System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)    æ–¼ System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)    æ–¼ System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)    æ–¼ System.Threading.ThreadHelper.ThreadStart()    

[AlexeyGanshin]

Hi. Use new object for email from BP 6.3

[CHIH_HANHuang]

I can't find the new Mail VBO.

[david.l.morris]

The new Outlook VBO comes with the install of BP 6.3. When you install 6.3, it will be placed in the VBO folder in the installation directory of Blue Prism. It will also place a .dll file in the Blue Prism folder too, which it must have in order to function.

[AniketGour]

Hi ,   We are facing the same issue, please let us know if using latest object 6.3 helps resolve the issue. The other observation we had was the blue prism start crashing with this error (event log) after some security updates for MS Office were installed on the machine, not sure if this is the trigger for such behavior  

[david.l.morris]

The MS Outlook VBO works flawlessly as far as I have seen. For a while I tested the MAPIEx VBO success rate and it was between 60-90% success rate on sending emails. So far, I have not seen a single failure in sending emails with the MS Outlook VBO.   Three things to be aware of (at least): (Sending emails) You'll need to change the line feed/carriage return characters in the email body to use instead. (Sending emails) You'll need to make sure that email addresses that are passed in to the Send Mail action do not contain trailing semicolons or an error will be thrown. (Getting emails) The input parameters where you put in an email address for the Sender (etc.) will not always resolve into the same thing. It will sometimes show the Display Name of the contact from the GAL and sometimes the email address. Just be aware of this for when you start testing getting emails. (all actions) Though the MAPIEx VBO could choose the mail profile to use, the Outlook VBO doesn't take an input parameter for this so it uses whatever is marked as the default profile. I'm sure there is more to be discovered in the differences when moving from the MAPIEx VBO to the Outlook VBO, but this is what I and others have discovered thus far. Anyone have anything to add? (Oh also, the DateTime inputs require UTC, if that isn't obvious to anyone) Dave