Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Serious problems and exchange becomes unresponsive

Status
Not open for further replies.

reynolwi

IS-IT--Management
Sep 7, 2006
452
US
Ok im not entirely sure where to look. I have had this problem twice now and its got me wondering what has happened.

The exchange server becomes totally un-responsive and after its been hardbooted you can sit there and look thru the logs and see numerous errors in the application logs.

Event Type: Error
Event Source: MSExchangeMTA
Event Category: Directory Access
Event ID: 155
Date: 10/22/2007
Time: 5:58:34 PM
User: N/A
Computer: EXCH1
Description:
Error 0X80004005 occurred while reading information for directory name (DN) CN=SMTP (EXCH1-{DDE7F979-0998-4400-B52B-88F2BD236547}),CN=CONNECTIONS,CN=DOMAIN,CN=MICROSOFT EXCHANGE,CN=SERVICES,CN=CONFIGURATION,DC=DOMAIN,DC=NET from the directory. [MTA OPERATOR 23 38] (12)

----
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1001
Date: 10/22/2007
Time: 9:10:31 PM
User: N/A
Computer: EXCH1
Description:
Fault bucket 537233242.

Data:
0000: 42 75 63 6b 65 74 3a 20 Bucket:
0008: 35 33 37 32 33 33 32 34 53723324
0010: 32 0d 0a 2..

----
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1031
Date: 10/22/2007
Time: 10:38:54 AM
User: N/A
Computer: EXCH1
Description:
One of the System Attendant's task is blocked.
Function: COffLineABScanTask::Work

----
Event Type: Warning
Event Source: MSExchangeMU
Event Category: General
Event ID: 1040
Date: 10/22/2007
Time: 10:07:29 AM
User: N/A
Computer: EXCH1
Description:
Metabase Update failed replication 5 times with error 80004005 (Unspecified error). Please change the diagnostic logging level of MSExchangeMU to 'minimum' or greater to find the source of the problem.

----
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 10/22/2007
Time: 8:17:29 PM
User: N/A
Computer: EXCH1
Description:
Process MAD.EXE (PID=2104). All Domain Controller Servers in use are not responding:
cont1.domain.net
cont2.domain.net

----
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2103
Date: 10/22/2007
Time: 1:13:29 PM
User: N/A
Computer: EXCH1
Description:
Process MAD.EXE (PID=2104). All Global Catalog Servers in use are not responding:
cont1.domain.net
cont2.domain.net

----
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date: 10/22/2007
Time: 1:30:54 PM
User: N/A
Computer: EXCH1
Description:
Process EMSMTA.EXE (PID=2916). All the DS Servers in domain are not responding.

----
Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Field Engineering
Event ID: 2219
Date: 10/22/2007
Time: 8:58:35 PM
User: N/A
Computer: EXCH1
Description:
The MTA is running recovery on the internal message database because the MTA was not shut down cleanly. This operation may take some time. Status updates will be written to the Windows 2000 Event Log. [DB Server MAIN BASE 1 0] (14)

----
Event Type: Error
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3079
Date: 10/22/2007
Time: 9:37:28 AM
User: N/A
Computer: EXCH1
Description:
Unexpected replication thread error 0x80004005 on database "First Storage Group\Public Folder Store (EXCH1)".

FReplAgent

----
Event Type: Error
Event Source: MSExchangeIS Mailbox Store
Event Category: General
Event ID: 7200
Date: 10/22/2007
Time: 9:18:00 AM
User: N/A
Computer: EXCH1
Description:
Background thread FDoMaintenance halted on database "First Storage Group\Mailbox Store (EXCH1)" due to error code 0x80004005.

----
Event Type: Warning
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8031
Date: 10/22/2007
Time: 9:10:38 AM
User: N/A
Computer: EXCH1
Description:
Unable to open LDAP session on directory 'CONT1' using port number 389. Directory returned the LDAP error:[0x1] Operations Error.

----
Event Type: Error
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 9097
Date: 10/22/2007
Time: 9:14:43 AM
User: N/A
Computer: EXCH1
Description:
The MAD Monitoring thread was unable to connect to WMI, error '0x800705aa'.

----
Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Date: 10/22/2007
Time: 8:58:32 PM
User: N/A
Computer: EXCH1
Description:
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000

----
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9153
Date: 10/22/2007
Time: 9:20:58 AM
User: N/A
Computer: EXCH1
Description:
Microsoft Exchange System Attendant reported an error '0x80004005' when setting DS notification.


Each event id repeats serveral times and the 8031 had the most. There were about 47000 events and 8031 probably had 40000.

What is going on? I mean its got me stumped and im not sure where to look. Ive checked settings and checked the directory servers and they are good. Someone please point me in the right direction or a suggestion.

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
What is your LAN topology?
One Exchange server?
One GC? Is that the Exchange server?
How many users?
 
The enterprise is setup with 2 sites. The main site has the 3 servers which are the Primary AD Controller with all FSO Roles, Exchange Server w/ fax capabilities, and File Server w/ Remote Access VPN. The remote site which is connected to the main site via a Hardware VPN on symantec routers and it just has a Domain Controller. Both sites' domain controllers are GCs.

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
Any event log errors in the system log that aren't about Exchange that may help?
 
reynolwi,

Did you ever find the root cause for this problem and if so, how did you solve it?

I am having the same problems and for the life of me, I cannot put my finger on it. For the past three nights, my server has gone down ... All I've done is to add new SMTP email accounts for my users to use a different email format. I kept the original accounts.

Hope to hear from you!
 
i have not entirely found the root of my problem. it only does it to me everyonce in a while and i havent seen any errors for it yet so i dont know whats going on. I did have some FRS problems between my 2 domain controllers and i got that fixed and i just added a 3rd domain controller thru a VPN tunnel and i still havent seen any errors. Im unsure if it was FRS problems causing it or what. Im going to keep a very close eye on it and see what happens. The thing i find weird is that the exchange server sits in the corporate office and is hooked into the same switch as the main domain controller. i dont see why it would become unresponsive and say that it cant contact the domain controller but who knows.

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
Oh well, I'm glad to hear things are better for you. I am having the same problem with it not being able to connect to one or another of my LDAP directories ...

I am a total novice in this and it sure is fun (not) to struggle with this. I am sure that in the end, I will walk away know a lot more than it all started :) Trying to look at it from a positive perspective.

Thanks,




 
I have read through the event log entries, must of which are the same error/warning.

Sorry, I don't even know what dcs and gcs are? :(

 
----
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 10/22/2007
Time: 8:17:29 PM
User: N/A
Computer: EXCH1
Description:
Process MAD.EXE (PID=2104). All Domain Controller Servers in use are not responding:
cont1.domain.net
cont2.domain.net

----
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2103
Date: 10/22/2007
Time: 1:13:29 PM
User: N/A
Computer: EXCH1
Description:
Process MAD.EXE (PID=2104). All Global Catalog Servers in use are not responding:
cont1.domain.net
cont2.domain.net

----
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date: 10/22/2007
Time: 1:30:54 PM
User: N/A
Computer: EXCH1
Description:
Process EMSMTA.EXE (PID=2916). All the DS Servers in domain are not responding.


It's fairly clear it's a connectivity issue. It could be network connectivity or permissions. What was the outcome of your troubleshooting?
 
Funny, reading the quoted error I realized what DCS and GCS mean

DCS - Domain Controller Server
GCS - Global Catalog Server

I have 2 DNS servers (which I figure are same as DCS), primary and secondary. As per the GCS, no idea! Lets see what google returns.

Regards,
 
dcs are your active directory domain controllers which you should have atleast 1 of and you should have atleast 1 global catalog server.

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
Can they be one in the same? I do have 1 active directory server ... Not sure if same as Exchange Server ...


Regards,
 
exchange should not be installed on an active directory server unless its the only server. Its extremely, extremely unwise to install exchange on an active directory server because of the issues it could cause. There should always be atleast one global catalog server and yes a domain controller can also be a global catalog server and you should always have atleast 1 gc.

what is your setup like...

what OS are you running in your network? windows 2003 r2, 2000, and what is exchange installed on?

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
MX 2003, on WIN-2003 R2 running on a DELL PowerEdge 58xx Server.

I came in as a developer and two months later I find myself doing the ADMIN stuff. I welcome it solely because I love learning and it is something different but it is driving me crazy.

How/where do I find answers for your questions? It seems to me that these are the very basic stuff an ADMIN should know. I am the first one to admit that I am not, by any means, an administrator. I sure will give it my best and see to it that things are handled and taken care of properly.

God knows I am not off to a good start :(

Regards,

 
The sites * services applet. Expand the site * expand the domain controller ...

As far as what exchange sees, look at event 2080.


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top