• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2266
  • Last Modified:

Exchange 2013 delivery report: Specified Cast Is Not Valid

We have an installation of Exchange 2013 CU2 in place at a customer site. Operating system is Server 2012 standard.

They regularly use the delivery report from the ECP. When they either run a search, or when the click on a message from the search results the commonly get and error which simply states "Specified Cast Is Not Valid"

This is server is still co-existing with an Exchange 2007 that is not quite ready to be removed for extenuating circumstance.

Any thoughts on what can be done to remedy this?

Thank you.
Doug
0
teamhancock
Asked:
teamhancock
  • 2
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
The error message isn't specific to Exchange. It is a generic error from code.
Therefore it could be a bug, it isn't something I have seen myself. It could also be something about the subject line of the message - containing special characters for example.

CU3 is due soon, I would look at deploying that to begin with. In my view Exchange 2013 is still under active development, so the updates are resolving a lot of bugs.

Simon.
0
 
teamhancockAuthor Commented:
Simon,

Thank you for your feed back. I too agree that Exchange 2013 does not seem to be completely ready for production use.

I have see this error message scattered across all sorts of products and situations, except for Exchange 2013, out on Google.

Do you have any idea how soon CU3 will be out, or if there are any proposed fixes that will be included in CU3?

Thanks again.
0
 
Simon Butler (Sembee)ConsultantCommented:
The cumulative updates are quarterly, so the next one is due soon. Exact date isn't clear and of course the list of updates will not be available until its release. I don't really know much more than that - just keep an eye on the Exchange team blog for news.

Simon.
0
 
teamhancockAuthor Commented:
I opened an incident with MS support and all they could tell me on this was that they think this occurs when the search criteria matches the following situation.

Mailbox being search has received a message from a sender that delivered the mail to the mailbox via a distribution list. When a search is performed on the recipients mailbox for messages sent from the sender, the error will occur, provided that the sender has not actually sent any messages directly to the sender otherwise.

This sure sounds like a bug to me and MS has yet to provide a solution or fix. Even a better error/response would be an improvement in my opinion.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now