System Centre Email Connector Error 'SMCMDB Subscription Write Action Module'

Rogret Mogane 0 Reputation points
2024-05-27T06:59:03.27+00:00

We are experiencing this issue on SCSM email connector to Exchange Online. This is not a new deployment. The SCSM service manager user account got locked-out in AD and after trying various options of unlocking with no success we created a new service account with the required access and privilages. We were able to recover the Service Manager to a working state however the email connector is not able to either send notifications and recieve/download new emails from Exchange Online mailbox. See atatched file for the content errors on Event Viewer.

Microsoft System Center
Microsoft System Center
A suite of Microsoft systems management products that offer solutions for managing datacenter resources, private clouds, and client devices.
883 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Rogret Mogane 0 Reputation points
    2024-05-27T08:40:26.6033333+00:00

    EventID 33614, SMCMDB Subscription Write Action Module

    The database subscription is unable to trigger the Windows workflow because of Data Access service errors.

    The following errors were encountered:

    Exception message: Cannot connect to the System Center Management service, please make sure that the service is running. See inner exception for details.

    One or more subscriptions were affected by this.

    Subscription name: ExchangeConnector.915c1cf2085b4567a0b929ad189ddb97

    Instance name: Microsoft.SystemCenter.SubscriptionWorkflowTarget

    Instance ID: {A2A24426-1C31-3A8F-EA39-D316A83C8EF9}

    Management group: SABS-SCSM

    EventID 26319, OpsMgr SDK Service

    An exception was thrown while processing SubmitTasks for session ID uuid:03cd6490-7781-48b1-94d4-34ec19d70c0c;id=2.

    Exception message: The creator of this fault did not specify a Reason.

    Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.HealthServiceUnavailableException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.HealthServiceUnavailableException: Cannot connect to the System Center Management service, please make sure that the service is running. See inner exception for details. ---> System.Runtime.Remoting.RemotingException: Failed to connect to an IPC Port: Access is denied.

    Server stack trace:

    at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel, Int32 timeout)

    at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel level, Int32 timeout)

    at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)

    at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

    Exception rethrown at [0]:

    at System.Runtime.Remoting.Proxies....).

    0 comments No comments