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 Rhinorhino 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
Joined
Sep 7, 2006
Messages
452
Location
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
 
Southbeach... heres a good suggestion that i would hope the others would agree with me on. Go to Barnes and Noble or something and pickup Microsoft books on Windows Server 2003 R2 and Exchange 2003. I have the Windows Server 2003 R2: Administrator Pocket Consultant and the Exchange 2003: Administrators Pocket Consultant and Administrators Companion books. They are extremely helpful and full of information that would help you our. I really suggest you pick up something along those lines for each and read thru them. There are several books from different authors that are all good. Some might just be for Windows Server 2003 but most of i covers 2003 R2.


You can also find how your exchange is setup by doing the following.

Open Exchange System Manager (ESM) on the exchange server, or if you have the exchange tools installed on a client machine you can open it there. Then depending on how exchange is setup your either going to expand the "Servers" folder or the "Administrative groups" folder. If you see administrative gorups your going to expand the "1st admin group" and then expand the "servers" folder. Then right-click on the server and go to properties. Then go to the directory access tab and report back what it shows there.
Your going to see several columns including domain controller, site, domain, type, ldap port. Report back what each row shows in each column. You should atleast have 3 rows under each column.

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
reynolwi,

Thanks for suggesting the books ... I have already purchased a few books, one of them is MS Exchange Server 2003 by Walter J Glenn and Bill English. I find this to be a great reference. I also have Secure messaging Exchange Server 2003 and Accessing Network Security.

The problem is that these books do not tell you anything about recovering from where I find myself.

I have made some progress and have successfully:
1) Installed MS2K3 R2
2) Managed to salvage content of my D drive - Here is where exchange had been installed
3) Have followed steps suggested in this article


I am now installing SP1 uinsg /DesasterRecovery switch.

My next step will be to restore data ... Data is in D drive so I figure I should be able to simply copy it into its normal exchange directory tree.

Can I?

Regards
 
Why are you reinstalling Exchange? Are you starting from scratch or are you going to move everything from the old server to the new server?

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
Same server - The C drive crashed and was not able to boot. Server kept rebooting the moment it reached the Win2003 logo.

I spent hours with DELL Support and we were not able to fix C drive. We ran chkdsk several times and nothing fixed it.

So, I had to install W2K3, format C drive and install the OS on C. D drive was there so I did nothing to it. Original ADMIN had installed Exchange on D so that played in my favor.

Now, the server boots, I installed exchange and need to get my data files from copy location d:\exchsrvr_old to new install location d:\exchsrvr.

The above mentioned article leads me to believe that I should be able to simply copy the databases and mount them.

Here is a twist, I do not see any menu option to open the Exchange Management UI. I went to my ADS server and left clicked my exchange server computer and clicked on manage but so far, it says that the path does not exist. I do not get it ... the server is there!

So right now I have two questions:

1) Can I simply copy d:\exchsrvr_old\mdbdata to d:\exchsrvr\mdbdata?

2) Where is my Exchange System Manager? **


** Why didn't the installation of exchange added the option on my Start/All Programs menu?


Regards,




 
ESM (Exchange system manager) is the server app on which the exchange server is installed on. You have to either be logged in locally or remotely via Terminal Services Admin Mode or use the ESM which can be installed on a local client computer.

To get to esm you would go to all programs on the start menu. then to the microsoft exchange folder and ESM should be listed there.

Now the copying part im not entirely sure about. Ive never had a exchange server completely crash before so i havent had to do disaster recovery.

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
I managed to set the Start Menu options by manually creating the shortcuts. When I try to run the Exchange Managment System.msc file I get an error from MMC saying that it cannot create the snap-in.

I now have to find out why this is ??? !!!!

Regards,
 
It sounds like something didnt take when you installed exchange server. See if the exchange services are running. Open the services applet in the administrative tools panel on that exchange server. There are going to be several exchange related services.

The following services should atleast be started on the exchange server... Microsoft Exchange Information Store, Management, MTA Stacks, Routing Engine, and System Attendant. If one or more is not started try and start it. The Information Store and MTA Stacks services depends on the System Attendant service to be running.

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
Ok it has done it again but this time it wasnt completely unresponsive. I could actually get into OWA this time. In the event logs it says that all DCs were unavailable and i now have 3 total dcs that are gcs as well. I can not get the exchange server to list the other 2 dcs. everytime i try and add them in manually it says it can not locate the server in the directory.

Is my exchange setup falling apart on me?

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
This is a bit of a long shot, but does that Dell server have a TCP/IP Offload Engine (TOE) on the network card? (I'm more of an HP server man myself, s 'm not sure about your Dell, but I'm pretty sure some of the later generation Dells have the TOE).

If so, you might try disabling it, we've seen some occurrences of similar unconnectability with TOE enabled.
 
Hmmm.... i'll check that out. I dont think it does but it might because its only 2 yrs maybe less old.

Any other suggestions? I have people looking at me for answers and im lost. Never had a server do this ever.

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
i am going to be checking again but i did not see that option on the NIC. What else could be causing this? Should i get a new NIC and put it in the computer and see how it responds?

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
Circa 2004 - 2005 Dell was using Broadcom NICs and there were tons of issues with the drivers. Have you updated the NIC drivers lately?

 
Sounds like substituting the NIC wouldn't be a bad idea.
 
Run exbpa.com and see if it says the drivers are over 2 years old.
Run windowsupdate to date for drivers.
 
i have run the exbpa recently and i dont remember it saying the nic drivers were over 2 yrs old. i have it running again and will report back what it says.

Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top