<

Exchange 2010 Backup fails with Consistency check failed and transaction logs did not purged. Event IDs (565, 9782, 10005).

Published on
17,985 Points
11,485 Views
5 Endorsements
Last Modified:
Approved
Problem: Exchange backup fails with event IDs (565, 9782, 10005).


Event ID: 565

The consistency check for the component 'a68a6481-5b9f-493e-825b-8234fa2bb025'\'Microsoft Exchange Server\Microsoft Information Store\MAIL' has failed. The application 'Exchange' will not be available in the backup created at '15T01:16:00.735484400Z'. Review the event details for information about consistency check issues.

Event ID: 9782

Exchange VSS Writer (instance c0f2f748-3652-4e6c-84cf-3ca738aae0e8:5) has completed the backup of database 'Mailbox Database 1234567890' with errors. The backup did not complete successfully, and no log files were truncated for this database.

Exchange VSS Writer (instance c0f2f748-3652-4e6c-84cf-3ca738aae0e8:5) has completed the backup of database 'Public Folder Database 1234567890' with errors. The backup did not complete successfully, and no log files were truncated for this database.

Event ID: 10005

DCOM got error "193" attempting to start the service wsbexchange with arguments "" in order to run the server:
{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}

This article shows how I applied some troubleshooting to get to the final solution.


Cause:

Unable to start "Microsoft Exchange Server Extension for Windows Server Backup service” (wsbexchange).

Resolution:

Fixed "Microsoft Exchange Server Extension for Windows Server Backup service” (wsbexchange) issue.

Troubleshooting steps:

Observed above events after the backup fails.
Executed VSSadmin list writers and verified all the VSSwriters are in stable state.
For testing purpose created a new database "Database" & "Test" mailbox in it.
Performed backup of it but got the same above error.
Took system stat data backup & it was successful.
Performed consistency check of the databases - passed.
Observed Exchange 2010 was installed with SP1.
Upgraded Exchange 2010 SP3 with update rollup5.
Tried to start the service ‘Microsoft Exchange Server Extension for Windows Server Backup service” (wsbexchange) and got error 193:0xc1.
Verified the regisrty for (wsbexchange) & {D8A2E312-3B17-4293-B71E-CD72A7C04BF3} with the working machine and seems to be fine.
Verified the permissions of object "CExchangeHelper Class" in DCOM config.
Took a backup of the registry.
Deleted and recreated ‘Microsoft Exchange Server Extension for Windows Server Backup service” (wsbexchange) service using SC delete/create command.
sc delete wsbexchange.
sc create wsbexchange binPath= "C:\program files\microsoft\exchange server\v14\bin\wsbexchange.exe" DisplayName= "Microsoft Exchange Server Extension for Windows Server Backup service" type= own start= demand
Tried to started "Microsoft Exchange Server Extension for Windows Server Backup" & it failed with error 193:0xc1.
Went to HKEY_LOCAL_MACHINE\SYSTEM\currentControlSet\Services\wsbexchange and in imagepath found the value was C:\program files\microsoft\exchange server\v14\bin\wsbexchange.exe
In the HKEY_LOCAL_MACHINE\SYSTEM\currentControlSet\Services\wsbexchange imagepath Value data box, added quotation marks around the complete path as "C:\Program Files\Microsoft\Exchange Server\bin\wsbexchange.exe" of the executable file wsbexchange.

e.g,  the path of the wsbexchange service is C:\Program Files\Microsoft\Exchange Server\bin\wsbexchange.exe, change the entry in the Value data box for the wsbexchange service to the following "C:\Program Files\Microsoft\Exchange Server\bin\wsbexchange.exe"

Started "Microsoft Exchange Server Extension for Windows Server Backup" service and it started successfully. It should be in manual state.
Performed a Exchange backup using windows backup and it was successful & purged the log files.

After having done that, exchange backup was successful & transaction logs purged.
5
Comment
Author:R--R
0 Comments

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Join & Write a Comment

how to add IIS SMTP to handle application/Scanner relays into office 365.
This video discusses moving either the default database or any database to a new volume.

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month