Getting tons of topology discovery errors.
From: loupgarou (anonymous_at_discussions.microsoft.com)
Date: 08/27/04
- Next message: Josh Sawyer: "2 Domains on 1 Exchange 5.5 server"
- Previous message: Howard: "Exchange 2003 and an IMAP source?"
- Next in thread: loupgarou: "Getting tons of topology discovery errors."
- Reply: loupgarou: "Getting tons of topology discovery errors."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Aug 2004 19:37:16 -0700
This server is a new one with mailboxes migrated from
exchange 5.5
-- it runs fine but encounters errors (somehow loses contact with the PDC) "Process IISIPMED1BBF5E-ED6A-4E8B-89F2-14AE04CFD1CC - AP ""EXCHANGEAPPLICATIONPOOL (PID=1968). Topology Discovery failed, error 0xffffffff. Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. "Process MAD.EXE (PID=272). All Domain Controller Servers in use are not responding: PDC.xxx.com.sg bdc.xxx.com.sg "Process MAD.EXE (PID=272). Topology Discovery failed, error 0xffffffff. "DSACCESS returned an error '0x80004005' on DS notification. Microsoft Exchange System Attendant will re- set DS notification later. "Process STORE.EXE (PID=2160). Topology Discovery failed, error 0xffffffff. "NSPI Proxy can contact Global Catalog INSIGHTPDC.xxx.com.sg 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 PDC.xxx.com.sg as soon as possible. "NSPI Proxy cannot contact any Global Catalog that supports the NSPI Service. New clients will be refused until a Global Catalog is available. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients. "Referral Interface cannot contact any Global Catalog that supports the NSPI Service. Clients making RFR requests will fail to connect until a Global Catalog becomes available again. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients. "LDAP Bind was unsuccessful on directory bdc.xxx.com.sg for distinguished name ''. Directory returned error:[0x51] Server Down. "The Win32 API call 'DsGetDCNameW' returned error code [0x54b] The specified domain either does not exist or could not be contacted. The service could not be initialized. Make sure that the operating system was installed properly. "Background thread FDoUpdateCatalog halted on database ""First Storage Group\Public Folder Store (EXCHANGE2003)"" due to error code 0x80004005. "Process INETINFO.EXE (PID=1528). All the DS Servers in domain are not responding. "Unexpected error An operations error occurred. Facility: LDAP Provider ID no: 80072020 Microsoft Exchange System Attendant occurred. Process EMSMTA.EXE (PID=2868). All the DS Servers in domain are not responding. "The Directory Service Referral interface failed to service a client request. RFRI is returning the error code: [0x3f0]. "LDAP Bind was unsuccessful on directory PDC.xxx.com.sg for distinguished name ''. Directory returned error:[0x51] Server Down. DC=xxx,DC=com,DC=sg "Unexpected error An operations error occurred. Facility: LDAP Provider ID no: 80072020 Microsoft Exchange System Attendant occurred. -------------- the fact that it can work 70%? of the time indicates that configuration should be ok, somehow its bugged out or losing contact with the pdc.. my other bdc doesn't report any problems at all when this is happened. I've swapped network cables incase its a cable problem, but to no effect what do you suggest I do? make the exchange server a bdc as well?
- Next message: Josh Sawyer: "2 Domains on 1 Exchange 5.5 server"
- Previous message: Howard: "Exchange 2003 and an IMAP source?"
- Next in thread: loupgarou: "Getting tons of topology discovery errors."
- Reply: loupgarou: "Getting tons of topology discovery errors."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
