The other day I was asked to install the Business Contact Manager (BCM) Update for Outlook 2003, an application I knew nothing about and up until that time, had not even heard of. After installing the Application and enabling Cached Exchange Mode, which required editing a registry entry, I attempted to share my BCM database and promptly received the error "There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)". Damn I hate it when I get those HRESULT: 0x800706D9 errors...

Anyways, after clicking through the error, I was able to add a user and then received another error, "An error occured while applying changes. Your changes have not been applied successfully.' Now there's a useful error message if I've ever seen one. Googling along, I stumbled upon a site which suggested starting the Windows Firewa//Internet Connection Sharing (ICS) service. This worked and I was then able to successfully share my BCM DB.

I did read a little tid-bit that says only the administrator of a particular machine is capable of sharing a database(s). This may pose an issue to some people attempting to setup this application. If anybody could confirm or deny this with a comment, I'd appreciate it.

The registry edit for enabling the Cached Exchange Mode has been copied below:

Enabling/Disabling Cached Exchange Mode through the Registry

Cached Exchange Mode is new in Outlook 2003. If makes a local copy of the Exchange Mailbox. The benefits of enabling this is reducing network traffic, faster responds time of the Outlook client (especially with large attachments), being able to use the Junk E-mail Filter and being able to work off-line.

When you create a new profile in Outlook 2003 Cached Exchange mode is enabled by default.
When you upgrade from a previous Outlook version with an Exchange mailbox to Outlook 2003 Cached Exchange mode is disabled by default.

This makes it really hard to determine and control remotely whether your clients have Cached Exchange Mode enabled.

Enabling/Disabling Cached Exchange Mode can be controlled though the registry. This allows you to enable/disable it with a simple logon script to create a standard in your organization without the need of forcing the recreation of the entire profile at start-up or visit each client.

Cached Exchange Mode is controlled by the following key;
[HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\<ProfileName>\13dbb0c8aa05101a9bb000aa002fc45a]

00036601 (REG_BINARY)

enabled value; 84 01 00 00
enabled with Public Folders/Favorites: 84 05 00 00
disabled value; 04 00 00 00

Source: http://www.howto-outlook.com/howto/cachedmoderegkey.htm