locked
Exchange Connector 3.0 - Connector fails to process email when message has users CC'd in RRS feed

  • Question

  • Hi,

    I've discovered an interesting problem that we didn't experience with SCSM 2010 and the original Exchange connector.

    We have migrated to SCSM 2012 and Exchange Connector 3.0 in the past week.  I've found a problem where the Exchange Connector stops processing emails in the workflow account mailbox where users that don't exist in the CMDB that are also cc'd into the email message.

    We get the following error message logged in the Operations Manager Event Log each time the connector runs:

    A Windows Workflow Foundation workflow failed during execution.

    Workflow Type: Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow

    Workflow Identifier: 747428bb-d6e5-12e1-f8db-1b06d606df72

    Exception Type: System.Security.SecurityException

    Exception Message: The source was not found, but some or all event logs could not be searched.  Inaccessible logs: Security.

    Exception Stack: at System.Diagnostics.EventLog.FindSourceRegistration(String source, String machineName, Boolean readOnly)

       at System.Diagnostics.EventLog.SourceExists(String source, String machineName)

       at System.Diagnostics.EventLog.VerifyAndCreateSource(String sourceName, String currentMachineName)

       at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)

       at System.Diagnostics.EventLog.WriteEntry(String message)

       at Microsoft.SystemCenter.ExchangeConnector.TraceListener.Trace(String traceType, String traceMessage)

       at Microsoft.SystemCenter.ExchangeConnector.ExchangeInbox.logMessage(String message, Int32 level)

       at Microsoft.SystemCenter.ExchangeConnector.ExchangeInbox.ProcessMail()

       at Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow.Execute(ActivityExecutionContext executionContext)

       at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)

       at System.Workflow.ComponentModel.CompositeActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)

       at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(Activity activity, ActivityExecutionContext executionContext)

       at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)

       at System.Workflow.Runtime.Scheduler.Run()

    We don't use impersonation and for testing I added the workflow account as a local administrator on the SCSM server and as an SCSM Administrator.  We didn't experience this issue with previous versions as they didn't add cc'd users as related items to the IR.  Has anyone else come across this problem, or is there a way of disabling this new feature?

    Thanks,

    Tim

    Monday, December 10, 2012 10:40 AM

All replies