Quantcast
Channel: Exchange Server Blog
Viewing all articles
Browse latest Browse all 133

Exchange Server Various Errors and Their Recovery

$
0
0

In these days Exchange Server is using by almost all organization due to its facility to communicate business. But still acquiring these features, it shows sometimes different types of errors. Due to these errors Exchange database gets corrupted and all facilities may become inaccessible to the users.

Here we are going to discuss some rareExchange Server errors with their solutions:-

Error1:-“An internal processing error has occurred. When Trying to restart the Exchange System Manager or the Microsoft Exchange Information Store service, or both. ID no: c1041724 Exchange System Manager”

Cause:-
The root cause of this problem is that the System mailbox object exists in the System Objects container, which is created for this mailbox store. And when you try to mount it, Exchange Server creates another object for the same, which is causing the problem.
Resolution:-
The solution of the above error is in these following steps:-
1. First start the Active Directory and Computers snap-in.
2.Then click the ‘Advanced Features’ option in the View menu.
3. After that find the Microsoft Exchange System Objects container, and then look for the System mailbox object whose mailbox store that you were trying to mount.
4.
At last delete the System mailbox and now again try to mount the mailbox store.

Error2:-”Error -1022='JET_errDiskIO' = Disk I/O error”
Cause:-
The requested database page cannot be accessed due to an I/O error. This error message could be appear because of disk or controller failure or because the path to check file is incorrect.
Resolution:-
1. In such circumstances you should run chkdsk /f /r command to check valid permissions on Exchsrvr folder.
2. Then ensure the correct path to check file and troubleshoot file-level anti-virus software scanning.
3.After this, you need to either restore the database from backup or repair the database using Exchange Recovery default command such as:- eseutil/p, isinteg -fix, and ExMerge.

These are very crucial errors which can damage the whole Exchange database and all essential data and files can be lost. When you have applied above solutions but you are finding that Exchange database is still out of your reach then its better to go for some proficient commercial Exchange server recovery application available in the market such as Stellar Phoenix Exchange Server Recovery. These type of utilities provides very effective EDB recovery and comes in very affordable price.

Viewing all articles
Browse latest Browse all 133

Trending Articles