Se Lai
asked on
All the exchange services are in stopping or starting state on DAG...
There are different type of event errors 4027, 1008, 106 ..... the server is in DAG but showing no operational....
Have you checked to make sure the disks aren't full? I've see disks fill up and the services are in that kind of state.
ASKER
Sean,
The disks have enough space more than 10TB.... please check the attached image.
We have two exchange servers the one is operational and good but the second one has this issue...
Exchange2016.PNG
The disks have enough space more than 10TB.... please check the attached image.
We have two exchange servers the one is operational and good but the second one has this issue...
Exchange2016.PNG
check the database for consistency through powershell
C:\program files\Microsoft\Exchange Server\14\BIn> eseutil /mh "<Database path>"
You will find the result saying : Clean Shutdown or Dirty Shutdown
under state.
Then do one thing right click properties of Mailbox database and remove two things
1) Do not mount store at startup 2) Remove Circular logging
Then Restart All Exchange services infact Restart the microsoft Exchange AD Topology service and check whether all services are started or not,
If the database is in Dirty shutdown mode then check for the number of logs required
under Log required : (Status) in the result for eseutil /mh and check for the logs required
Also check for the logs are corrupted or not with the command line
eseutil / ml "E:\Exchange\E00001.log" (example)
and check the status of log passed or corrupted and report your findings
C:\program files\Microsoft\Exchange Server\14\BIn> eseutil /mh "<Database path>"
You will find the result saying : Clean Shutdown or Dirty Shutdown
under state.
Then do one thing right click properties of Mailbox database and remove two things
1) Do not mount store at startup 2) Remove Circular logging
Then Restart All Exchange services infact Restart the microsoft Exchange AD Topology service and check whether all services are started or not,
If the database is in Dirty shutdown mode then check for the number of logs required
under Log required : (Status) in the result for eseutil /mh and check for the logs required
Also check for the logs are corrupted or not with the command line
eseutil / ml "E:\Exchange\E00001.log" (example)
and check the status of log passed or corrupted and report your findings
ASKER
I can't see the database in Console(ECP), its showing only ex1 the current operation one... i can't see databases on this server...
Did you run the powershell commands? The database path is the physical path on the local server.
ASKER
Yes it is showing dirty shutdown...
ASKER
I have attached result for first command or dirty shutdown...... but I was not able to pull the info on the second command for corrupted logs..
logsrequire.PNG
logsrequire.PNG
From error, I can see IS service not starting, what all errors you see in application and system logs? Share the exact event id with source and description. Any change made recently, like IP or Patch?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I added Exchange servers in Manage Auditing and Security Log under the user Rights Assignment and fixed the issue.