XML validation error ResponseCodeType

Aspose.Email reported the invalid operation exception “Instance validation error: ‘ErrorConnectionFailedTransientError’ is not a valid value for ResponseCodeType”. This occurred during a call to delete an email. I think it was when our library called IEWSClient deleteItem, though connection failures could be encountered in any operation. Subsequent activity failed with more orderly error reporting of “The mailbox database is temporarily unavailable”. What can you tell us about the ResponseTypeCode problem - is that where the response provided by Exchange does not comply with the XML schema definition?

Here are full exception details:
There is an error in XML document (1, 942).
Target: Deserialize
Source: System.Xml
Inner exception: System.InvalidOperationException: Instance validation error: ‘ErrorConnectionFailedTransientError’ is not a valid value for ResponseCodeType.
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderzByNmgMAmbMchsVpDTcuLGSsJGmT56J2zv5Col0TOcZ2KXsPCdA.Read83_ResponseCodeType(String s)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderzByNmgMAmbMchsVpDTcuLGSsJGmT56J2zv5Col0TOcZ2KXsPCdA.Read383_DeleteItemResponseMessageType(Boolean isNullable, Boolean checkType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderzByNmgMAmbMchsVpDTcuLGSsJGmT56J2zv5Col0TOcZ2KXsPCdA.Read549_ArrayOfResponseMessagesType(Boolean isNullable, Boolean checkType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderzByNmgMAmbMchsVpDTcuLGSsJGmT56J2zv5Col0TOcZ2KXsPCdA.Read585_DeleteItemResponseType(Boolean isNullable, Boolean checkType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderzByNmgMAmbMchsVpDTcuLGSsJGmT56J2zv5Col0TOcZ2KXsPCdA.Read1127_DeleteItemResponse()
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)

Hello @cp60299,

ErrorConnectionFailedTransientError is an error raised by the Exchange server. The server is simply not functioning correctly at the time you sent your request. As the name and description suggest, it’s not a permanent error, and the client is allowed to try again later.

The stack trace also shows that this exception type isn’t handled properly. It’s because ErrorConnectionFailedTransientError isn’t documented in Microsoft’s ResponseCode documentation, which is strange.

Thank you.