Error Messages and Event 9176 Appear When Using Outlook Clients with Exchange 2000 on Windows 2000 (305596)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
This article was previously published under Q305596 SYMPTOMS
When you use Exchange 2000 on a computer that runs Windows 2000, Outlook clients may receive one of the following error messages:
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.
Unable to expand the folder. The set of folders could not be opened. The information store could not be opened.
On the Exchange 2000 server, you might see the following event:
Error Event Source: MSExchangeSA
Event Category: (11)
Event ID: 9176
Description: NSPI Proxy can contact Global Catalog 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 as soon as possible. For more information, click http://search.support.microsoft.com/search/?adv=1.
However, restarting the Global Catalog Server does not resolve the behavior.
CAUSE
This behavior can occur when the Name Service Provider Interface (NSPI) proxy is not supported by the Global Catalog Server.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name Platform
------------------------------------------------------------------
13-Aug-2001 12:05 5.0.2195.4117 355,088 Advapi32.dll
13-Aug-2001 12:05 5.0.2195.3936 135,440 Dnsapi.dll
13-Aug-2001 12:05 5.0.2195.3649 94,992 Dnsrslvr.dll
13-Aug-2001 12:00 5.0.2195.4117 523,024 Instlsa5.dll
13-Aug-2001 12:05 5.0.2195.4117 143,120 Kdcsvc.dll
07-Aug-2001 14:03 5.0.2195.4081 197,392 Kerberos.dll
26-Jun-2001 23:16 5.0.2195.3781 69,456 Ksecdd.sys
10-Aug-2001 17:16 5.0.2195.4117 505,104 Lsasrv.dll 128-bit
10-Aug-2001 17:16 5.0.2195.4117 505,616 Lsasrv.dll 56-bit
10-Aug-2001 17:16 5.0.2195.4117 33,552 Lsass.exe
13-Aug-2001 12:05 5.0.2195.4117 306,448 Netapi32.dll
13-Aug-2001 12:05 5.0.2195.4117 358,160 Netlogon.dll
13-Aug-2001 12:05 5.0.2195.4123 909,584 Ntdsa.dll
13-Aug-2001 12:05 5.0.2195.4101 386,320 Samsrv.dll
13-Aug-2001 12:05 5.0.2195.4117 128,784 Scecli.dll
13-Aug-2001 12:05 5.0.2195.3649 299,792 Scesrv.dll
13-Aug-2001 12:05 5.0.2195.4025 48,400 W32time.dll
02-Aug-2001 00:44 5.0.2195.4025 56,592 W32tm.exe
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type: | Major | Last Reviewed: | 7/17/2006 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbDirServices kbfix kbWin2000PreSP3Fix kbWin2000sp3fix KB305596 |
---|
|