Handling and Displaying Service-Provider Errors

Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

A version of this page is also available for

Windows Embedded CE 6.0 R3

4/8/2010

If an object cannot be read from or written to the service provider on the desktop (due to GetPacketor SetPacketcall failures, for example), ActiveSync marks the object as "unresolved" and does not display error messages. Error messages are displayed only when the user later selects "Resolve Items."

The service provider can control when errors are displayed, through the use of two sub-flags that indicate when the provider is allowed to display errors. Control is not automatic; the provider must be written to handle the flags correctly.

	Copy Code
#define BSF_SHOW_FATAL_ERRORS ((UINT)0x00000004) // Errors that block synchronization should be displayed immediately. #define BSF_SHOW_RESOLVE_ERRORS ((UINT)0x00000008) // Errors should be displayed only during the "resolve items" phase.

Copy Code

#define BSF_SHOW_FATAL_ERRORS ((UINT)0x00000004)
// Errors that block synchronization should be displayed
immediately.
#define BSF_SHOW_RESOLVE_ERRORS ((UINT)0x00000008)
// Errors should be displayed only during the "resolve items"
phase.

These sub-flags are set by ActiveSync in the uParamparameter for RSC_BEGIN_SYNC during IReplStore::ReportStatuscalls. When BSF_SHOW_FATAL_ERRORS is set, any serious failure (for example, loss of network connectivity) that keeps the service provider from continuing should be displayed. When BSF_SHOW_RESOLVE_ERRORS is set, any per-object errors should be displayed, typically during GetPacketand SetPacketcalls.

If neither flag is set, no errors should be shown. If RSC_REMOTE_SYNC is set, no blocking user interface should be shown.

See Also

Concepts