Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS 
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Exchange won't stay connected.
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login  | |
|
Exchange won't stay connected. - 27.May2008 12:38:54 PM
|
|
|
harrisch
Posts: 1
Joined: 27.May2008
Status: offline
|
Hello all! I am new to the forum and come with some questions. I havea new customer with Exchange that is having lots of problems. They have 2003 enterprise editon server running 4 virtual servers with VMWARE. The server has 4gb memory total and 2 of the 4 is allocated to the exchange server. They state that it locks up multiple times a week. It being the exchange server. They state in outllook they see exchange disconnected and they know it is a problem. They have tried just restarting the exchange services but doesn't always work. Most time they have to restart the exchange and when they do they state that workstations lock up for about 20 minutes. The following errors were listed in the event log. Any help or suggestions would be greatly appreciated.
Event Type: Error
Event Source: MSExchange ADAccess
Event Category: Topology
Event ID: 2103
Date: 5/22/2008
Time: 5:35:51 AM
User: N/A
Computer: DODSON-EXCH
Description:
Process MAD.EXE (PID=208). All Global Catalog Servers in forest DC=,DC=com are not responding:
xxx.com
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9153
Date: 5/22/2008
Time: 5:34:58 AM
User: N/A
Computer: DODSON-EXCH
Description:
Microsoft Exchange System Attendant reported an error '0xc1034a2a' when setting DS notification.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchange ADAccess
Event Category: Topology
Event ID: 2102
Date: 5/22/2008
Time: 5:34:52 AM
User: N/A
Computer: DODSON-EXCH
Description:
Process MAD.EXE (PID=208). All Domain Controller Servers in use are not responding:
xxx.com
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8365
Date: 5/22/2008
Time: 5:31:55 AM
User: N/A
Computer: DODSON-EXCH
Description:
Could not read the Security Descriptor from the Exchange Server object with guid=C0BC8540E8557C4D8F96718900DA9288. As a result the Proxy Address Calculation RPC interface will not be available on the local Exchange Server.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchange ADAccess
Event Category: Topology
Event ID: 2120
Date: 5/22/2008
Time: 5:29:33 AM
User: N/A
Computer: DODSON-EXCH
Description:
Process MAD.EXE (PID=208). Error ERROR_TIMEOUT (0x800705b4) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain xxx.com
The query was for the SRV record for _ldap._tcp.dc._msdcs.xxx.com
. The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses:
24.196.252.60
192.168.2.113
. Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running.
For information about correcting this problem, type in the command line:
hh tcpip.chm::/sag_DNS_tro_dcLocator_messageB.htm
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchange ADAccess
Event Category: Topology
Event ID: 2104
Date: 5/22/2008
Time: 5:29:21 AM
User: N/A
Computer: DODSON-EXCH
Description:
Process MAD.EXE (PID=208). None of the domain controllers in the domain are responding. This event can occur if the domain controllers in local or all domains become unreachable because of network problems. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. Run the Dcdiag command line tool to test domain controller health.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchange ADAccess
Event Category: Topology
Event ID: 2103
Date: 5/22/2008
Time: 5:29:21 AM
User: N/A
Computer: DODSON-EXCH
Description:
Process MAD.EXE (PID=208). All Global Catalog Servers in forest DC=xxx,DC=com are not responding:
xxx.com
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9385
Date: 5/22/2008
Time: 5:27:58 AM
User: N/A
Computer: DODSON-EXCH
Description:
Microsoft Exchange System Attendant failed to read the membership of the universal security group '/dc=com/dc=xxx/ou=Microsoft Exchange Security Groups/cn=Exchange Servers'; the error code was '8007203a'. The problem might be that the Microsoft Exchange System Attendant does not have permission to read the membership of the group.
If this computer is not a member of the group '/dc=com/dc=xxx/ou=Microsoft Exchange Security Groups/cn=Exchange Servers', you should manually stop all Microsoft Exchange services, run the task 'add-ExchangeServerGroupMember,' and then restart all Microsoft Exchange services.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1031
Date: 5/22/2008
Time: 5:27:56 AM
User: N/A
Computer: DODSON-EXCH
Description:
One of the System Attendant's task is blocked.
Function: COffLineABScanTask::Work
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchangeFBPublish
Event Category: General
Event ID: 8197
Date: 5/22/2008
Time: 5:27:21 AM
User: N/A
Computer: DODSON-EXCH
Description:
Error initializing session for virtual machine DODSON-EXCH. The error number is 0x80040934. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchangeFBPublish
Event Category: General
Event ID: 8281
Date: 5/22/2008
Time: 5:27:21 AM
User: N/A
Computer: DODSON-EXCH
Description:
Error searching for public folder servers in the Active Directory for virtual machine DODSON-EXCH. The error number is 0x80040934.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 5/22/2008
Time: 5:34:54 AM
User: N/A
Computer: DODSON-EXCH
Description:
This computer was not able to set up a secure session with a domain controller in domain DODSONENDO due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0 ^..À
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 5/19/2008
Time: 8:51:54 AM
User: N/A
Computer: DODSON-EXCH
Description:
The Microsoft Exchange Information Store service terminated with service-specific error 0 (0x0).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
|
|
|
|
RE: Exchange won't stay connected. - 27.May2008 1:47:13 PM
|
|
|
Sembee
Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline
|
All of those errors mean the same thing - the server cannot find the domain controllers.
The most common reason for that is DNS configuration errors.
Looking through the errors I saw this: 24.196.252.60
That looks to be an external DNS server.
Simple rule - No external DNS servers should be anywhere in the network configuration of any servers that are not domain controllers. Domain controllers should also not have external DNS in their network configuration, only external DNS should be in the DNS server applet.
Therefore the first thing I would do is go through the DNS configuration and remove any external DNS servers that are listed.
Simon.
_____________________________
Simon Butler,
Exchange MVP
Blog: http://blog.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.sembee.co.uk/
Exchange Resources: http://exbpa.com/
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
Printable Version
