Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » schema   (RSS)

How to resolve the EWS ErrorNoPublicFolderServerAvailable error.

If you are using Exchange Web Services (EWS) against Exchange 2007 SP1, you may run into an issue where you are getting the ErrorNoPublicFolderServerAvailable and the error message says it’s not a proper error code. This error appears if you have set

Santa, I want it all - WebDAV and the full-meal-deal - allprops.

So, your trying to get "all properties" using WebDAV. Well, hate to break it to you, but there is no way unless you know what every property is and specify it. You will find the same limitation in other messaging APIs - just pick any of them. Now, you

Broken Exchange Schema - WebDAV allprops, sinks and/or exoledb fail to return properties

Not getting all the properties you would expect from an WebDAV ALLPROPS or from an Event sink? Well, it could be that the Exchange schema is broken. The Problem: If you find that your application is no longer retrieving a full list of properties, it may

Dynamic list of properties versus explicit properties

With messaging APIs, you can retrieve a list of properties dynamicly or by specific property name. For example with WebDAV, ALLPROPS will return a set of properties on a item. There are issues with trying to get a full list of properties. First of all,

Exchange Protocol Documentation

Microsoft released preliminary protocol documentation for Exchange 2007 (as well as Microsoft Office 2007 and SharePoint Server) as part of Microsoft's Interoperability Principles. The Exchange protocols are now publicly available on the Open Protocol

Exchange Protocol Documentation

Microsoft released preliminary protocol documentation for Exchange 2007 (as well as Microsoft Office 2007 and SharePoint Server) as part of Microsoft's Interoperability Principles. The Exchange protocols are now publicly available on the Open Protocol
 
Page view tracker