Read Time: 5 minutes
Frustrated with the “Exchange Service Error 1068: The dependency service or group failed to start” issue while starting the Exchange services? As a result, you are not able to access mailboxes or mount databases after a server start or configuration change.
The challenge with this error is that the actual problem usually lies outside the Exchange service itself, like Windows or network-related services, etc. But don’t worry. With this write-up, we will clear all doubts regarding the error and provide the possible fixes to address them smoothly.
It occurs when a service depends on another service that can be turned off, corrupted, misconfigured, or not running properly.
Exchange Service Error 1068: Common Symptoms
Administrators may notice the following symptoms for the Exchange Service error 1068:
- Outlook connection failures.
- Exchange services fail to start.
- Mailboxes become inaccessible.
- Databases may enter an Exchange dirty shutdown state after abrupt server failure
- Increase in email delivery interruptions.
- Exchange Admin center not responding.
Major Causes of Exchange Service Error 1068
With the help of the following causes, you will get insights into which solutions are ideal to fix the error.
- Incorrect DNS settings or network interruptions may hamper services.
- Disabled dependency services like Windows Event Log, IIS Service, etc.
- Improper service account permissions may prevent Exchange services.
- Active Directory connectivity issues, as Exchange heavily depends on it.
- Dealing with the damaged or corrupted Exchange database, i,e EDB files.
- Damaged Exchange binaries or configuration files can also cause the error.
- Restart the server, as temporary glitches may resolve after rebooting.
- Check database growth regularly and reduce Exchange EDB file size to maintain optimal server performance
- You can also check the Change Management Request to locate any new changes.
- Verify disk space because low disk space may prevent services from starting.
- Check Event Viewer like Windows logs, Application logs, & Exchange related errors.
- Run “sfc/scannow”, as corrupted Windows system files can trigger error 1068. Then, restart the server.
- Reset Service Logon credentials with Services> Exchange Services > Properties > Log On. Then, re-enter the correct credentials.
- Temporarily turn off the anti-virus, apply needed anti-virus exclusions, re-enable anti-virus, & then restart Exchange Services.
Best Workable Fixes for “Exchange Server Error 1068”
Here, we have provided the top solutions to fix Exchange Server error 1068 with their complete step-by-step approach.
Fix 1. Check Dependency Services
In this, we will need to go to the services console & then verify the dependencies. Let’s understand with the following steps:
Step 1. Press Windows + R key & type services.msc. Hit OK.
Step 2. Locate the Exchange Services like Microsoft Exchange Information Store/ Transport/ Mailbox Assistants.
Step 3. Right-click on it, select Properties & open the Dependencies tab. Make sure that all the listed services are either Running or Set to Automatic.
Fix 2. Restart the Required Windows Services
This section will help you with the commands through which you can restart the needed services. You need to run the Command Prompt as an Administrator with the following commands:
- Remote Procedure Call [RPC]: net start RpcSs
- Windows Event Log: net start EventLog
- IIS Admin Service: net start IISAdmin
- Tcp Port Sharing Service: net start NetTcpPortSharing
Fix 3. Check the Active Directory Connectivity
Exchange requires constant communication with the Active Directory to manage user mailboxes, routing, & permissions. So, verifying them can also be helpful in fixing the error.
First, check Domain connectivity with the following prompt:
- nltest /dsgetdc:yourdomain.com
Then, verify the DNS configuration & ensure that the:
- Preferred DNS points to the Domain Controller.
- No incorrect external DNS should be configured.
Fix 4. Check Exchange Database Health
It is obvious that if you are dealing with damaged databases, the chances of errors increase, including the Exchange Service error 1068. So, we will first identify the health status, then perform the needed steps accordingly.
- Run Exchange Management Shell as an administrator with the following command:
If the output is Clean Shutdown, it implies a healthy database. But if the output is Dirty Shutdown, it implies the server stopped abruptly. In such situations, administrators may also need to recover EDB public folders along with user mailboxes to restore complete Exchange functionality.
- If needed, you perform soft recovery with this command:
However, if the database remains inaccessible after recovery attempts, using an advanced EDB to PST converter can simplify mailbox extraction and recovery. Such tools help administrators recover mailboxes from corrupt EDB files and export them directly into PST format without mounting the database
Fix 5. Repair the Exchange Server Installation
It is helpful when your Exchange files are corrupted or damaged. Using the standard & Microsoft-supported method helps you to rebuild a corrupted or failed Exchange Server. Here are the steps:
- Use the same Exchange version ISO.
- Run repair command: Setup.exe /Mode: RecoverServer
Final Words on Fixing “Exchange Server Error 1068”
The Exchange Server error 1068 may appear critical, but with the right & systematic approach, it can be resolved quickly. I hope the blog provided them in a structured manner.
Moreover, to handle the severe corruption in the EDB files of any size, irrespective of Exchange Server versions, check out our advanced Exchange Server software. It even allows you to restore them into PST, Exchange, or Office 365 without data loss.
FAQs
Ans. It is possible that an incomplete or failed Windows update may modify service configurations or dependencies that can trigger error 1068.
Ans. Not necessarily. The error is primarily service dependency-related. But corruption in databases can contribute to the error.
Ans. Indirectly Yes as insufficient memory may prevent services from starting correctly during server boot.
