Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, July 27, 2018 9:49 AM
How do you troubleshoot the following event viewer entries:
Event ID: 134
The transaction resource manager on volume C: encountered an error during recovery. The resource manager will continue recovery.
What does this mean?
What was being recovered?
In search for a solution I came across: fsutil resource setautoreset true c:\
What is the pro and con of running the above administrative command prompt command?
What does this command do?
What is being reset?
How did it fail that it needs to be recovered?
Are there better troubleshooting steps?
All replies (2)
Monday, July 30, 2018 9:30 AM
Hi,
The command always used when Windows file system transaction log is corrupted. The Windows file system uses the transaction log to recover system transactions when a file error occurs. The Common Log File System (CLFS) transaction logs may be left in an inconsistent state. When the CLFS transaction logs are in an inconsistent state.
Use it to delete the .blf files and the .regtrans-ms files from the %Windir%\System32\SMI\Store\Machine folder.
For this event and error, in many situations, this event indicates a physical problem with the hard disk. It is recommended to ensure that all the data on that drive is backed-up and protected against possible disk failure.
Regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, July 30, 2018 10:47 AM
1) So this is not an operating system corruption but a registry corruption?
2) This then should not be able to be fixed by sfc /scannow?
3) And then should not be able to be fixed by dism /online /cleanup-image /restorehealth?
4) Would creating a new use have any impact?
5) Can this fix itself if there are no active attempts to fix the problem?
6) If a drive has hardware tests that pass what is the next step?
7) If the drive has chkdsk /r problems that indicate repair should the drive file system repair fix this problem?
8) If there are no chkdsk /r problems found then this is all a registry corruption?
9) The common log file system I've never checked. Is this something that should be a part of routine maintenance or only if problems are in the event viewer?
10) If the drive passes tests then the fsutil command above should be run? Are there any potential pitfalls when running this command?