Troubleshooting Phone Book Update Problems

This article describes possible problems that may prevent phone book updates from occurring properly.

This article assumes that you are using a profile generated with the Connection Manager Administration Kit (CMAK) and are using Connection Point Services, but cannot get the phone book to update.

There are several possible reasons why phone book updates are not downloaded to the client. In CMAK, you must click to select the Automatically download Phone book updates check box in the Set Up Connect Actions screen in the CMAK Wizard. You must also specify the name of the phone book to be downloaded and the Connection Point server name in the Specify Phonebook Files and Updates screen in the Connection Manager Wizard.

On the phone book server side, the problem is often with permissions. The minimum permissions required are:

• FTP pbsdata: requires Write permissions when you post
• WWW pbserver: requires Read and Execute
• WWW pbsdata: requires Read and Write

The same permissions are required on an NTFS partition.

It is also possible that the phone book is not being posted correctly. Verify that the Application log in Event Viewer shows "Event 30006" for Source Phone Book Service. The details are: "A new phone book was detected."

To test that the phone book server is set up correctly for updates, browse to the following test address (URL), where servername is the name of your phone book server and PBname is the name of the phone book: This should generate a prompt to open or save the phone book .cab file.

NOTE: This URL is all one line. It has been wrapped in the article for readability purposes.

You can enable logging on the client side by modifying the .cms file. Edit the "0=cmdl32.exe %profile%" line in the [Connect Actions] section and add the following text: After editing, the section should appear as follows: If the 00000000.tmp file generated after making a connection is empty, the URL was not found. If you receive a "Cannot find service on server, bad request (405)" error message, the phone book name was not found. Check to make sure the permissions are correct.

This can also occur if the phone book name contains an illegal character such as "&", "?", or "!".