ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Symantec Email Submission Client (SESC) debug logs contain error message "The folder save operation failed due to invalid property values." when Microsoft Exchange Client Access Server (CAS) send duplicate notifications

book

Article ID: 156732

calendar_today

Updated On:

Products

Mail Security for Microsoft Exchange Messaging Gateway

Issue/Introduction

The SESC debug logs contain the following error message:

[::]2012-07-09 15:11:51,847, [17], ERROR, Symantec.Submission.Exchange.Client.ExchangeMailbox, Failed to rename folder of user: [email protected][::]
Microsoft.Exchange.WebServices.Data.ServiceResponseException: The folder save operation failed due to invalid property values.
   at Microsoft.Exchange.WebServices.Data.ServiceResponse.InternalThrowIfNecessary()
   at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
   at Microsoft.Exchange.WebServices.Data.Folder.Update()
   at Symantec.Submission.Exchange.Client.ExchangeMailbox.CheckAndUpdate(String folderId, String expectedName)

See the following article for details on SESC debug logs: How to Obtain Debug logs for Symantec Email Submission Client (SESC).

Conditions

  • The Exchange CAS server sent multiple notifications for the same event.  SESC processes the same event in parallel causing most to fail.

1. Search the SESC debug logs for multiple events for the user.  This is an example where the CAS server sent multiple "folder rename" events to SESC:

[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-09 15:11:50,534, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]

2. Search the SESC debug logs for a successful folder rename event:

   [::]2012-07-09 15:11:51,628, [13], INFO , Symantec.Submission.Exchange.Client.ExchangeMailbox, Folder renamed for user [email protected][::]

3. Then search the SESC debug logs for subsequent failures trying to rename the folder:

[::]2012-07-09 15:11:51,847, [17], ERROR, Symantec.Submission.Exchange.Client.ExchangeMailbox, Failed to rename folder of user: [email protected][::]
[::]2012-07-09 15:11:51,847, [14], ERROR, Symantec.Submission.Exchange.Client.ExchangeMailbox, Failed to rename folder of user: [email protected][::]
[::]2012-07-09 15:11:51,940, [19], ERROR, Symantec.Submission.Exchange.Client.ExchangeMailbox, Failed to rename folder of user: [email protected][::]
[::]2012-07-09 15:11:52,050, [11], ERROR, Symantec.Submission.Exchange.Client.ExchangeMailbox, Failed to rename folder of user: [email protected][::]
[::]2012-07-09 15:11:52,159, [16], ERROR, Symantec.Submission.Exchange.Client.ExchangeMailbox, Failed to rename folder of user: [email protected][::]
[::]2012-07-09 15:11:52,253, [15], ERROR, Symantec.Submission.Exchange.Client.ExchangeMailbox, Failed to rename folder of user: [email protected][::]
[::]2012-07-09 15:11:52,378, [18], ERROR, Symantec.Submission.Exchange.Client.ExchangeMailbox, Failed to rename folder of user: [email protected][::]
[::]2012-07-09 15:11:52,487, [20], ERROR, Symantec.Submission.Exchange.Client.ExchangeMailbox, Failed to rename folder of user: [email protected][::]



Here is another example where the Exchange CAS server sent multiple "item submission" notifications and SESC processes them in parallel causing some to fail.

[::]2012-07-10 16:18:55,509, [45], INFO , Symantec.Submission.Service.NotificationHandler, ITEM_SUBMISSION. User: [email protected] ID: AAMkAGNhMzk1OGRjLTZhNzQtNGU1Mi1iMzNiLThlY2IwZDVkY2Y2YQBGAAAAAABrzHmQnI8+SJ8kvr5aeZSUBwBhajpjwOJrRJcK5YF2WBhcAAmxQMVMAABJ4xEiMdHlQL6dnZAvpam7AAAAGQ4KAAA=[::]
[::]2012-07-10 16:18:55,509, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-10 16:18:55,509, [45], INFO , Symantec.Submission.Service.NotificationHandler, ITEM_SUBMISSION. User: [email protected] ID: AAMkAGNhMzk1OGRjLTZhNzQtNGU1Mi1iMzNiLThlY2IwZDVkY2Y2YQBGAAAAAABrzHmQnI8+SJ8kvr5aeZSUBwBhajpjwOJrRJcK5YF2WBhcAAmxQMVMAABJ4xEiMdHlQL6dnZAvpam7AAAAGQ4LAAA=[::]
[::]2012-07-10 16:18:55,509, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-10 16:18:55,509, [45], INFO , Symantec.Submission.Service.NotificationHandler, ITEM_SUBMISSION. User: [email protected] ID: AAMkAGNhMzk1OGRjLTZhNzQtNGU1Mi1iMzNiLThlY2IwZDVkY2Y2YQBGAAAAAABrzHmQnI8+SJ8kvr5aeZSUBwBhajpjwOJrRJcK5YF2WBhcAAmxQMVMAABJ4xEiMdHlQL6dnZAvpam7AAAAGQ4MAAA=[::]
[::]2012-07-10 16:18:55,509, [45], INFO , Symantec.Submission.Service.NotificationHandler, FOLDER_SUBMISSION. User: [email protected] [::]
[::]2012-07-10 16:18:55,509, [45], INFO , Symantec.Submission.Service.NotificationHandler, ITEM_SUBMISSION. User: [email protected] ID: AAMkAGNhMzk1OGRjLTZhNzQtNGU1Mi1iMzNiLThlY2IwZDVkY2Y2YQBGAAAAAABrzHmQnI8+SJ8kvr5aeZSUBwBhajpjwOJrRJcK5YF2WBhcAAmxQMVMAABJ4xEiMdHlQL6dnZAvpam7AAAAGQ4NAAA=[::]
[::]2012-07-10 16:18:55,509, [13], DEBUG, Symantec.Submission.Exchange.Client.ExchangeItem, Copying message. Source -> Dest / [email protected] -> [email protected][::]
[::]2012-07-10 16:18:55,509, [14], DEBUG, Symantec.Submission.Exchange.Client.ExchangeItem, Copying message. Source -> Dest / [email protected] -> [email protected][::]
[::]2012-07-10 16:18:55,509, [18], DEBUG, Symantec.Submission.Exchange.Client.ExchangeItem, Copying message. Source -> Dest / [email protected] -> [email protected][::]
[::]2012-07-10 16:18:55,509, [19], DEBUG, Symantec.Submission.Exchange.Client.ExchangeItem, Copying message. Source -> Dest / [email protected] -> [email protected][::]
[::]2012-07-10 16:18:56,025, [13], ERROR, Symantec.Submission.Exchange.Client.ExchangeItem, Microsoft.Exchange.WebServices.Data.ServiceResponseException: The specified object was not found in the store.
   at Microsoft.Exchange.WebServices.Data.ServiceResponse.InternalThrowIfNecessary()
   at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
   at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalBindToItems(IEnumerable`1 itemIds, PropertySet propertySet, ServiceErrorHandling errorHandling)
   at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToItem(ItemId itemId, PropertySet propertySet)
   at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToItem[TItem](ItemId itemId, PropertySet propertySet)
   at Symantec.Submission.Exchange.Client.ExchangeItem.GetMimeContent(ExchangeVersion exchangeVersion)[::]
[::]2012-07-10 16:18:56,025, [13], DEBUG, Symantec.Submission.Exchange.Client.ExchangeItem, Empty mime content. Nothing to copy![::]
[::]2012-07-10 16:18:56,056, [14], ERROR, Symantec.Submission.Exchange.Client.ExchangeItem, Microsoft.Exchange.WebServices.Data.ServiceResponseException: The specified object was not found in the store.
   at Microsoft.Exchange.WebServices.Data.ServiceResponse.InternalThrowIfNecessary()
   at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
   at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalBindToItems(IEnumerable`1 itemIds, PropertySet propertySet, ServiceErrorHandling errorHandling)
   at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToItem(ItemId itemId, PropertySet propertySet)
   at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToItem[TItem](ItemId itemId, PropertySet propertySet)
   at Symantec.Submission.Exchange.Client.ExchangeItem.GetMimeContent(ExchangeVersion exchangeVersion)[::]

Notice the message ID for each message is the same.  Notice that there are multiple threads copying the same message.  This results in some of the threads failing because the item is no longer present.

Cause

SESC processes notifications from the Exchange CAS server in parallel.  If the Exchange CAS server sends duplicate notifications then SESC attempts to process then all at the same time (in parallel).  Most of the requests from SESC to the CAS server for the folder rename will fail because the folder has already been renamed.

Resolution

Symantec is aware of this issue.  This article is updated as more information is available.  Subscribe to this article to receive updates.

Workaround

Ignore the error messages.  There is no impact on functionality.