Zainals Bahrain

Had few errors with exchange server lately , after examing the Event viewer log i got the following errors :

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2103

Date: 5/2/2007
Time: 8:49:47 AM
User: N/A
Computer: exchange server
Description:
Process MAD.EXE (PID=1792). All Global Catalog Servers in use are not responding:
yourserver.domain.com ( Domain controller )

Event Type: Error
Event Source: MSExchangeSA
Event Category: RFR Interface
Event ID: 9074
Date: 5/2/2007
Time: 8:49:04 AM
User: N/A
Computer: exchange server
Description:
The Directory Service Referral interface failed to service a client request. RFRI is returning the error code:[0x3f0].

Event Type: Error
Event Source: MSExchangeSA
Event Category: NSPI Proxy
Event ID: 9176
Date: 5/2/2007
Time: 8:49:04 AM
User: N/A
Computer: exchange server
Description:
NSPI Proxy can contact Global Catalog yourserver.domain.com 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 yourserver.domain.com as soon as possible.

Now there are many causes to such errors , in my scenario ; after examining the exchange server , i noticed that the Global Catalog server is not listed under GC domain controllers list in exchange server …

possible solution 1:

to add the GC do the following steps :
Start your exchange system manager –> Expand Administrative groups –> Expan First Administrative Group –> Expand servers –> right click your exchange server then click properties –> Click on Directory Acess TAB –>
*Make sure all domain controllers are listed under ( Show > all domain controllers ) if not then untick Auto discover servers & add them Manually

*Make sure you have your Configuration domain controller listed under ( show > configuration domain controller) if not then untick Auto discover servers & add them Manually .

*Make sure you have your domain controller(s) listed under (show > domain controllers) if not then untick Auto discover servers & add them Manually .

*Make sure you have your GLOBAL CATALOG servers listed under ( show > global catalog servers) if not then untick Auto discover servers & add them Manually .

Now the last is important , simply because exchange servers depends on Global catalog servers .

How do i know which server is the Global Catalog

possible solution 2:

Check your exchange TCP/IP > DNS settings , make sure that its pointing to your internal DNS server ( most likely the domain controller ) . you may also want to be sure that your Local DNS server is using itself to resolve queries …

possible solution 3:
none of your domain controller is a global catalog , maybe because the GC died somewhere in between & no body shifted the GC nor the FSMO roles …

How do i know which server is the Global Catalog

in some previous post i explained more about what happens when the Primary domain controller fails …

possible solution 4:
Make sure that “file and print sharing for microsoft networks” are enabled on both Exchange Server and your local DNS (Domain Controller) that will probably be used by exchange admin to connect and retrieve the policy from the domain controller …
you can examine this by right click your network adapter > properties > check whether file and print sharing for microsoft networks is ticked , if not then tick it/enable it …

ohh ya , don’t forget that REBOOTING is the first solution to any microsoft error eyh ?
if you are rebooting both DC and Exchange Reboot the DC first till it starts its services , then the Exchange otherwise exchange services will hung waiting for dependencies to start .

hope this post is useful , please do post a comment if this was such an ass saver …