How to repair a corrupted Public Folder (on-prem)

1. Check public folder status: Open Exchange Management Shell (EMS).
Run the following command to check the health status of the public folder:
powershell
Get-PublicFolder -Recurse | Get-PublicFolderStatistics
Review the output and verify that there are no errors or warning messages.
2. Use the IsInteg tool to repair: Stop the Microsoft Exchange Information Store service.
Open a command prompt (with administrator privileges) and navigate to the Exchange installation directory (typically C:\Program Files\Microsoft\Exchange Server\V15\Bin).
Run the following command to check and repair the public folder database: cmd
eseutil /g “path_to_public_folder_database.edb”
If an error is detected, run the following command to repair the database: cmd
eseutil /p “path_to_public_folder_database.edb”
Note: The /p option may result in data loss, it is recommended to backup the database first.
3. Rebuild the public folder index: Open Exchange Management Shell (EMS).
Run the following command to rebuild the public folder index:
powershell
Get-PublicFolderDatabase | Update-PublicFolderDatabase
4. Check the public folder permissions:
Open the Exchange Management Shell (EMS).
Run the following command to check public folder permissions:
powershell
Get-PublicFolderClientPermission -Identity “\PublicFolderName”
Ensure that the permissions are set correctly and use the following command to repair the permissions if necessary:
powershell
Add-PublicFolderClientPermission -Identity “\PublicFolderName” -User “User” -AccessRights “Owner”
5. Rebuild the folder using New-PublicFolder: If a specific public folder is damaged and cannot be repaired, you can try to delete and rebuild the folder.
Run the following command to delete the corrupted public folder:
powershell
Remove-PublicFolder -Identity “\PublicFolderName” -Recurse
6. Rebuild the public folder using the following command: powershell
New-PublicFolder -Name “PublicFolderName” -Path “\ParentFolder” -Copy
7. Check the event log: Open Event Viewer and check the Application and Service Log > “Microsoft” > ” Exchange” > ‘HighAvailability’ or ‘MailboxDatabase’.
Take further action based on the error messages in the logs.