OpenSpan - error when attempting to use send Method on OutlookMail component
I am able to create and save an email using the methods for the OutlookMail Component. However I am unable to send the email that is created.
Any ideas?
1) Exception Information
*********************************************
Exception Type: OpenSpan.Automation.AutomationException
EventLink: OpenSpan.Automation.EventLink
ThrowingLink: OpenSpan.Automation.EventLink
MachineName:
CreatedDateTime: 11/2/2016 8:43:13 PM
AppDomainName: "OpenSpan.Runtime.exe"
ThreadIdentityName: ""
WindowsIdentityName:
AdditionalInformation: NameValueCollection with 0 items
Message: "Error executing link in Automation: Automation1 - From: Automation1.microsoftOutlookMail1.Properties To: Automation1.microsoftOutlookMail1.Send()
Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))"
Data: IDictionary (System.Collections.ListDictionaryInternal) with 0 items
TargetSite: Void Execute(System.Object, OpenSpan.Automation.ExecutionEventArgs)
HelpLink: NULL
Source: "OpenSpan.Automation"
StackTrace Information
*********************************************
at OpenSpan.Automation.EventLink.Execute(Object sender, ExecutionEventArgs e)
at OpenSpan.Automation.EventLink.OnReceiveEvent(Object sender, ExecutionEventArgs e)
at OpenSpan.Automation.ConnectableWorker.DoWork(Object sender, ExecutionEventArgs executionArgs)
I am able to create and save an email using the methods for the OutlookMail Component. However I am unable to send the email that is created.
Any ideas?
1) Exception Information
*********************************************
Exception Type: OpenSpan.Automation.AutomationException
EventLink: OpenSpan.Automation.EventLink
ThrowingLink: OpenSpan.Automation.EventLink
MachineName:
CreatedDateTime: 11/2/2016 8:43:13 PM
AppDomainName: "OpenSpan.Runtime.exe"
ThreadIdentityName: ""
WindowsIdentityName:
AdditionalInformation: NameValueCollection with 0 items
Message: "Error executing link in Automation: Automation1 - From: Automation1.microsoftOutlookMail1.Properties To: Automation1.microsoftOutlookMail1.Send()
Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))"
Data: IDictionary (System.Collections.ListDictionaryInternal) with 0 items
TargetSite: Void Execute(System.Object, OpenSpan.Automation.ExecutionEventArgs)
HelpLink: NULL
Source: "OpenSpan.Automation"
StackTrace Information
*********************************************
at OpenSpan.Automation.EventLink.Execute(Object sender, ExecutionEventArgs e)
at OpenSpan.Automation.EventLink.OnReceiveEvent(Object sender, ExecutionEventArgs e)
at OpenSpan.Automation.ConnectableWorker.DoWork(Object sender, ExecutionEventArgs executionArgs)
2) Exception Information
*********************************************
Exception Type: System.Runtime.InteropServices.COMException
ErrorCode: -2147467260
Message: "Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))"
Data: IDictionary (System.Collections.ListDictionaryInternal) with 0 items
TargetSite: Void Send()
HelpLink: NULL
Source: ""
StackTrace Information
*********************************************
at Microsoft.Office.Interop.Outlook._MailItem.Send()
at OpenSpan.Office.MicrosoftOutlookMail.Send()
***Updated by Moderator: Marissa to move from Pega Academy to Product Support; update categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
US
Ken,
Are you certain of the following?
When installing Pega Studio, you specified the correct version of Outlook that is installed on to your machine during the install wizard. If not, please re-install Pega Studio and indicate the correct version of Outlook during the install
You are creating a new outlook email and adding the to, subject, and body properties prior to calling the send method. Below is an autx example that was used locally that worked.
EY
US
Thank you for that information I tried the approach suggest and unfortunately no success. I have instead put a save at the end of my automation instead of a send and it successfully works. Please let me know if further information is needed to help resolve the issue.
Pegasystems Inc.
US
Ken,
When installing v8, did you make sure to indicate what version of Office that was installed on your machine on OpenSpan install wizard?
Also can you verify that Office.dll is listed as one of your references in the Solution Explorer?
EY
US
Please also note I am able to create a new email add the necessary contents of the email then save it. I am able to see the saved email in my drafts. The send functionality appears to be the only issue.
Pegasystems Inc.
US
I have no problem with sending an email as was indicated in the sample automation. Outlook does have to be running first however.
EY
US
Thank you for the information. Let me ensure outlook is running when I am experiencing the issue. I was under the assumption that it should be running considering when I do save instead of send I see the message appear in my drafts folder. I will update you soon as I test.
Tata Consultancy Services
US
Hi Ken,
Did you manage to get resolution to this issue ? Can you pls let me know what was the issue.
I'm getting the same error while sending mail.
Thanks.
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
We have also sent you a private message opening up a communication channel in case you have any further questions.
Pegasystems Inc.
US
IAG - Wesfarmers
AU
We have had this interop issue a few times, generally it was the result of an upgrade from 2007 to Office 2016, essentially the interop registry key would duplicate and throw things out. The easiest fix I had was to complete a repair on Office in 'Programs and Features'. If that fails you can manually remove the registry key for the duplicate entry.
Here is a post on the Visual Studio forums explaining the repair and manual key edit fix: