Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Unable to send notifications and reports in ScanMail for Exchange (SMEX) installed in an Exchange 2010 mailbox server role

    • Updated:
    • 24 Nov 2016
    • Product/Version:
    • ScanMail for Exchange 10.0
    • ScanMail for Exchange 10.2
    • ScanMail for Exchange 11.0
    • Platform:
    • Windows 2008 Enterprise
    • Windows 2008 Standard
You cannot send notifications and reports in SMEX that is installed in an Exchange 2010 mailbox server role.
When you check the SMEX_Master.log, the following log appears:
2012/03/05 15:45:45 -0500 [1104 : 6836] [                   unknown][ [                   NotificationEWS.cs( 0)] [DEBUG]
2012/03/05 15:45:45 -0500 [1104 : 6836] [                   unknown][ [                   NotificationEWS.cs( 0)] [DEBUG]
2012/03/05 15:45:45 -0500 [1104 : 6836] [[                   unknown][ [                   NotificationEWS.cs( 0)] [DEBUG] Before Send()
2012/03/05 15:45:46 -0500 [1104 : 6836] [                   unknown][ [                   NotificationEWS.cs( 0)] [ERROR] Failed to call NotificationEWS::Send(), Error Description:The account does not have permission to impersonate the requested user.
2012/03/05 15:45:46 -0500 [1104 : 6836] [[                   unknown][ [                   NotificationEWS.cs( 0)] [ERROR] at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ProcessWebException(WebException webException)
     at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.InternalExecute()
     at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
     at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalCreateItems(IEnumerable`1 items,
FolderId parentFolderId, Nullable`1 messageDisposition, Nullable`1 sendInvitationsMode, ServiceErrorHandling errorHandling)
     at Microsoft.Exchange.WebServices.Data.Item.InternalCreate(FolderId parentFolderId, Nullable`1 messageDisposition, Nullable`1 sendInvitationsMode)
     at Microsoft.Exchange.WebServices.Data.EmailMessage.InternalSend(FolderId parentFolderId, MessageDisposition messageDisposition)
     at TrendMicro.SMEX.Utilities.NotificationEWS.Send()
In Exchange 2010, the Collaboration Data Objects for Exchange (CDOEX) is no longer available. An alternative had to be implemented and the Exchange Web Services (EWS) is used for Mailbox Server Role Alert and Notification mechanism.
The Exchange 2010 Combo box uses Collaboration Data Objects (CDO).
When sending notifications via EWS, SMEX performs the following tasks:
  1. Find a Client Access Servers (CAS) to use to send notifications.
    This is done by using the Get-ClientAccessServer cmdlet to return all the registered CAS in a domain. SMEX only gets the last server on the list. Consequently, if this server is unavailable, the notification will fail.
  2. Connect to the specific CAS and resolve the sender mailbox.
    This is accomplished by using the email address defined in the Sender settings. You can access the settings by going to Administration > Notification Settings > Sender Settings. By default, this is set to administrator@do.not.reply. If no mailbox is resolved, the notification will fail.
  3. Impersonate the sender.
    By default, it is not possible to impersonate anybody in Exchange. However, this can be done by running the New-ManagementRoleAssignment cmdlet and allowing all members of the Exchange Servers group the ability to impersonate any mail user on the domain.
  4. Compose the email and send out the notification.
    This is done by using an internal notification EWS function that stimulates the behavior of CDO’s CreateMHTMLBody() function. In this case, sending the notifications and reports will fail in the process of impersonating the sender.
To fix this issue:
  1. Open the Exchange Management Shell. 
  2. Run the following command:
    New-ManagementRoleAssignment -Role ApplicationImpersonation -SecurityGroup "Exchange Servers" -name "SmexImpersonate"
Configure; Troubleshoot
Solution Id:
Did this article help you?

Thank you for your feedback!

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.