Article ID: 973307 - Last Review: November 19, 2009 - Revision: 1.0

An application that uses Exchange Web Services returns an exception on an Exchange Server 2007 server

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

Expand all | Collapse all

SYMPTOMS

On an Exchange Server 2007 server, the following response codes are not present in Exchange Web Services:

ErrorNoPublicFolderServerAvailable
ErrorNoApplicableProxyCASServersAvailable
ErrorProxyServiceDiscoveryFailed

This causes applications that use Exchange Web Services to fail.

For example, you obtain the following error when you perform a FindFolder function call on public folders:

Exception Type - System.InvalidOperationException
Exception Message - Instance validation error: 'ErrorNoPublicFolderServerAvailable' is not a valid value for ResponseCodeType

Back to the top

CAUSE

This issue occurs because the response codes are included in the ResponseCodeType.cs file, but are not present in the Messages.xsd schema file.

Back to the top

To resolve this problem, install Update Rollup 1 for Exchange 2007 Service Pack 2.

For more information about Update Rollup 1 for Exchange 2007 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

971534 (http://support.microsoft.com/kb/971534/ ) Description of Update Rollup 1 for Exchange Server 2007 Service Pack 2

Back to the top