Cisco Email Reporting Plugin Failed to report this message

[bryantste]

When trying to report a message as spam the latest reporting plugin displays the message " Failed to report this message."  I've uninstalled the older version and installed the latest CiscoEmailReporting-1-0-0-041.exe.  I'm running Outlook 2016.  I have attached the latest log as well as the diagnostic.

From the log:

06/27/2017 03:02:00 PM -05 WARN [ork.Configuration.ComponentConfiguration] LogConfig: Logging is initialized.
06/27/2017 03:02:01 PM -05 WARN [ailReporting.Framework.PluginRegistrator] GetAssemblyList: Start searching for plugins in C:\Program Files (x86)\Cisco\Cisco Email Reporting Plug-In
06/27/2017 03:02:01 PM -05 WARN [ailReporting.Framework.PluginRegistrator] GetPlugins: Plugin has detected 2 assemblies in executing folder
06/27/2017 03:02:01 PM -05 WARN [Framework.MsOutlook.Connect ] InitalizeAddin: Outlook version = '16.0.0.7766'
06/27/2017 03:02:15 PM -05 ERROR [Reporting.MsOutlook.OutlookComponent ] ReportSingleMessage: In ReportSingleMessage
System.Runtime.InteropServices.COMException (0x8000FFFF): Access violation at address 00007FFA526AE79C in module 'OUTLMIME.DLL'. Read of address 0000000000000002
at Redemption.ISafeMailItem.SaveAs(String Path, Object Type)
at Cisco.EmailReporting.Reporting.MsOutlook.SpamReporter.ReportSingleMessage(OutlookMailItem item, OutlookReportType type, RDOSession session)
06/27/2017 03:06:50 PM -05 WARN [Framework.Controls.AdditionalConfigPanel] LoadSettings: Current logging configuration: logging level - WARN; Log file path - C:\ProgramData\Cisco\Cisco Email Reporting Plug-In\bryants\CiscoEmailReporting.log
06/27/2017 03:07:03 PM -05 ERROR [Reporting.MsOutlook.OutlookComponent ] ReportSingleMessage: In ReportSingleMessage
System.Runtime.InteropServices.COMException (0x8000FFFF): Access violation at address 00007FFA526AE79C in module 'OUTLMIME.DLL'. Read of address 0000000000000002
at Redemption.ISafeMailItem.SaveAs(String Path, Object Type)
at Cisco.EmailReporting.Reporting.MsOutlook.SpamReporter.ReportSingleMessage(OutlookMailItem item, OutlookReportType type, RDOSession session)
06/27/2017 03:07:50 PM -05 ERROR [Reporting.MsOutlook.OutlookComponent ] ReportSingleMessage: In ReportSingleMessage
System.Runtime.InteropServices.COMException (0x8000FFFF): Access violation at address 00007FFA526AE79C in module 'OUTLMIME.DLL'. Read of address 0000000000000002
at Redemption.ISafeMailItem.SaveAs(String Path, Object Type)
at Cisco.EmailReporting.Reporting.MsOutlook.SpamReporter.ReportSingleMessage(OutlookMailItem item, OutlookReportType type, RDOSession session)
06/27/2017 03:15:46 PM -05 WARN [Framework.Controls.AdditionalConfigPanel] LoadSettings: Current logging configuration: logging level - WARN; Log file path - C:\ProgramData\Cisco\Cisco Email Reporting Plug-In\bryants\CiscoEmailReporting.log
06/27/2017 03:32:50 PM -05 ERROR [Reporting.MsOutlook.OutlookComponent ] ReportSingleMessage: In ReportSingleMessage
System.Runtime.InteropServices.COMException (0x8000FFFF): Access violation at address 00007FFA526AE79C in module 'OUTLMIME.DLL'. Read of address 0000000000000002
at Redemption.ISafeMailItem.SaveAs(String Path, Object Type)
at Cisco.EmailReporting.Reporting.MsOutlook.SpamReporter.ReportSingleMessage(OutlookMailItem item, OutlookReportType type, RDOSession session)

[Libin Varghese]

Hi,

I see you are already working with Dennis on a TAC case. I would have recommended opening a TAC case as well to narrow down if it was an issue with the plugin version or workstation.

- Libin V

[mroberts]

I have loaded the email reporting version 1.1.0.114 and receive the same error running WIN 10 and Office 2016, was there a solution to this issue?

Thanks

[Mathew Huynh]

Hello mroberts,

It seems the issue was resolved by a re-install from what I gathered.

Are you seeing the same issue on your side?

There is one thing i would like to note with the Cisco Outlook Plugins - you need to ensure any other security plugins is not enabled as well.

I would like to ask if you're having issues on the plugin- to disable any other add-ins on outlook and re-open outlook and see if the plugin properly starts.

Regards,

Matthew