MSExchange Server 4999 is a common error that appears in different versions of Exchange Server due to various reasons. This error can actually lead to email communication issues if not fixed on time. Today we will talk about error 4999 in MSExchange Server.
MSExchange Server error 4999 was originally noticed in Exchange Server 2013 and Exchange Server 2916 versions.
Exchange Server 4999 Error
Exchange Server 2016 in your environment 4999 error may occur. This error can interrupt your Exchange Server email flow (such as internal emails or incoming emails). The only way to fix the problem is to restart your Exchange Server. 🙁
A System.FormatException error or Event ID 2016 may occur in Exchange Server 4999. The details of this error are as follows;
Log Name: Application
Source: MSExchange Common
Event ID: 4999
Task Category: General
Level: Error
Tags: classic
Users: N/A
ErrorReportingEnabled: False
ErrorReportingEnabled: True
Watson report about to be sent for process id: 14648, with parameters: E12IIS, c-RTL-AMD64, 15.01.1531.007, w3wp#MSExchangeOWAAppPool, MECOwa2.Server, MECOSCOwaMapiNotificationManager.SubscribeToSuiteNotification, System.NotSupportedException, 80d2-dumptidset, 15.01.1531.007. XNUMX .
ErrorReportingEnabled: True
Causes of Error 4999
In fact, when solving an error, we need to learn the reasons behind this error, because if you can find the reason, you can solve the problem more easily.
In fact, according to the report, Microsoft Exchange Service Host routinely fails. Along with this, MSExchangeMailboxAssistants crashes occur. Also, this error can occur when the value of OABGeneratorWorkCycleCheckPoint property is set to a value greater than 49. Another reason is that the showInAddressBook attribute is not set.
- Exchange Server not being updated regularly
- Installing third-party applications
- Other software updates
- Antivirus compatibility issues
- Exchange Server configuration issues
- Expired SSL Certificates
Solution to Exchange Server 4999 Error
- First, you need to identify if a specific event is occurring when the error occurs. You can check if there are any backups or maintenance taking place, such as a snapshot, a virtual machine backup, or a database backup. Also, check if there are any other applications running at the time, such as an antivirus scan. If a new antivirus application is installed, you may need to check if the application is compatible with your Exchange Server and its specific version.
- You need to confirm that all Exchange Server services are running. If a service is not starting, you may need to check them.
- It is also important to check the disk space. Disk space will affect many things, especially the delivery of emails. Apart from this, lack of disk space can cause corruption and data loss of mailbox databases and transaction logs, which are crucial for the operation of Exchange Server. It is important to have enough space on your operating system drive and mailbox database drives.
- You can investigate the number of transaction log files on the mailbox database drive whose location you set during the Exchange installation.
The screenshot shows the default path where it was created. Now, if you see a lot of logs, it means there is a problem with the backup. It is important to check the backups as the backup clears the log files after the transactions are committed to the database. This cannot be done manually. It must be done with a backup process.
What is Exchange Server Log Structure and How Does It Work? – ÇözümPark (cozumpark.com)
If this doesn't work, you may lack disk space and experience performance issues that could lead to data corruption in the mailbox database.
If these logs are too old, it means that your backup solution does not recognize the application and is not compatible with your Exchange Server version. You can verify the last full backup of the database by running the following command.
Get-MailboxDatabase -Status | select Name,LastFullBackup
This gives the last date the database was fully backed up.
Since the issue is related to the delivery of mailboxes, you also need to check if there is any custom connector that has been created and is causing these issues. You need to check the receive and send connector from PowerShell or Exchange Admin Center.
You can also create a new database and move all mailboxes to it. However, if there is corrupt data, you may face a wall in front of you.
