In a Microsoft Exchange Server 2003 organization or in a Microsoft Exchange 2000 Server organization, when you use a Microsoft Outlook client to try to connect to a global catalog server that is running Microsoft Windows 2000 Server, you may experience any combination of the following symptoms:
- When you click a folder shortcut on the Microsoft Outlook Bar, you receive the following error message:
- The Outlook clients cannot resolve e-mail addresses when you create a Microsoft Outlook profile. Additionally, you receive the following error message:
The name could not be resolved. Network problems are preventing connection to the Microsoft Exchange Server Computer. Contact your system administrator if this condition persists.
- When you open Microsoft Outlook, you receive the following error message:
Unable to expand the folder. The set of folders could not be opened. The information store could not be opened.
- The following event is logged in the event log in the Event Viewer:
Event Type: Error
Event Source: MSExchangeSA
Event Category: (11)
Event ID: 9176
Computer: SERVERNAME
Description:
NSPI Proxy can contact Global Catalog fully qualified domain name of server but it does not support the NSPI service. After a Domain Controller is promoted to a Global Catalog, the Global Catalog must be rebooted to support MAPI Clients. Reboot fully qualified domain name of server as soon as possible.
- When you import a personal folders (.pst) file by using Exmerge.exe, you receive an error message that is similar to the following error message:
[14:46:12] Merging data from file 'L:\EXMERGEDATA\PSTFILE.PST' to mailbox 'mailbox'
('alias') on server 'SERVER'.
[14:46:12] Error extracting information from server DN ''
(CMapiSession::GetInfoFromProfile)
[14:46:12] Errors encountered. Copy process aborted for mailbox 'mailbox' ('alias').
↑ Back to the top
This issue may occur if a Microsoft Windows 2000 Server domain controller is not restarted after the domain controller is promoted to a global catalog server in an Exchange Server 2003 organization or in an Exchange 2000 Server organization. Microsoft Exchange tries to use the domain controller as a global catalog server, and the global catalog server appears online to client computers. When users try to create an Exchange profile and to connect to a Windows 2000 Server domain controller on the global catalog port 3268, they receive the event in the event log that is mentioned in the "Symptoms" section.
This issue can also occur if the IP address of the global catalog server is changed , but the global catalog server is not restarted.
This issue does not occur on a global catalog server that is running Microsoft Windows Server 2003.
↑ Back to the top
The NSPI service on a global catalog server does not dynamically bind. When you promote a domain controller to a global catalog server, the SRV records are written to DNS to advertise the service as available on this server. However, the service is not available until the new global catalog server is rebooted. The Microsoft Exchange System Attendant service requires the NSPI service in order to start.
Similarly, when an IP address change occurs in Windows 2000, services and protocols are dynamically unbound from the network adaptor and then rebound using the new IP address. This also occurs for the NSPI service, but then cannot be dynamically re-bind. A reboot is required.
↑ Back to the top
To resolve this issue, restart the Windows 2000 Server domain controller after the domain controller is promoted to a global catalog server.
↑ Back to the top
For more information about how to promote a domain controller to a global catalog server, click the following article numbers to view the articles in the Microsoft Knowledge Base:
304403�
Exchange considerations for promoting a domain controller to a global catalog server
311874�
Error 1712 is generated when you promote a domain controller to a global catalog server
↑ Back to the top