Discussion Locked

Where is my Global Address List?

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

On my Small Business Server 2000, the Exchange Server had problems. The Microsoft Tech person had me do a complete manual deletion and restoration. Now everything is working again but the Global Address List is empty when viewed by the Outlook clients. If someone tries to use the Find Names command, an error message pops up and says "Exchange Server is not configured to use detail templates in your language (English). See your system administrator."
I have checked the detail templates in English and in the preview mode it does show all the Users correctly.
Any ideas how to get the list to display again?

10 replies

by estebandelatorre

You have to install templates (upon different langauges queried by clients) onto you exchange server. Is a very easy process.
Templates came in the outlook 98 or 2000 distribution cdrom under a template directory of each language.
You may look at your templates under the site name, configuration,addresing, detail templates, you should have at least one template loaded. Need to load some more upon the different languages of OS or outlook installed.

Hope it helps

by estebandelatorre

From "Tools" select directory import, choose the .csv file from the outlook cd rom (usually template.csv) and import the file

by bigjellosheriff

Yes, I can access the list from the server. It just doesn't show up on the Outlook 2000 clients. If I use OWA, I can find everyone on the list.

by estebandelatorre

Ok! That's confirm my previous answer.
As you told me, you rebuild all, the server plus the exchange site no?
If you were sucessfull on browsing the address list from outlook clients (with the old server instalation), you may have used a differentlanguage for the OS server software, exchange software or perhaps different country code selected.
The reason why you can access it from the server is because the outlook client and exchange server has the same language. The OWA interface expoldes the server resources only.
Verify that the country code of the os server software is equal to one of those well known workstations first.
If this could not solve the problem you will need to install langauges templates
In order for a domestic (U.S.) Exchange Server computer to accommodate non- U.S. English clients, EACH language must have files and templates specific to it's nationality installed on the server.
The user interface and administration of the server are not affected by these changes.
In order for the foreign client to be able to communicate with the server, the Template.csv file and all associated files must be imported using the Exchange Administrator.

With the release of Exchange Server 5.0 and Exchange Server 5.5, these languages were moved to the corresponding non-U.S. English client CD-ROM. They may be found in the \tpl folder.

Read the comment for a datail procedure

by estebandelatorre

The following is a procedure for importing the Template.csv file and all associated files, for all versions:

1.- Click Directory Import on the Tools menu.
2.- Click Import File, browse, and select the Template.csv for the appropriate language.
3.- Click Open. All necessary files will be copied from the source to the Exchange Server computer.

Verify that the files were installed properly by checking for the language in the following leaf objects in the Exchange Administrator program:
"\configuration\addressing\details templates"
"\configuration\addressing\one-off address templates".

If the client requires the support of special fonts or double byte characters not included in the non-U.S. English standard set (for example, Japanese), the code page for that country must also be installed. The foreign language code pages must be loaded before the following proceedures are performed.
There is also an issue related to Windows NT code pages, in the netx comment!!

by bigjellosheriff

Again my thanks, but my system is Small Business Server 2000 (Windows Server 2000, Exchange Server 2000, etc.) and the server and clients are all US English. I'm afraid these solutions just don't apply.
I have found and fixed the problem. Please accept my thanks for your time.

This discussion is closed to new replies.