Event Log issues with MRCBT


Author
Message
RayG
RayG
Advanced Member
Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)
Group: Forum Members
Posts: 265, Visits: 1.2K
Looks like an old problem has returned:

The description for Event ID 263 from source mrcbt cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Ntfs\HarddiskVolume11

One of these for each device of course.
Installing the full version and doing a repair + reboot gives the same errors on restart.



Regards
RayG
Windows10 Pro X64 V1809 B17763.134 MR v7.2.3858

JamieW
JamieW
Macrium Representative
Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)
Group: Moderators
Posts: 115, Visits: 1.4K
Hi RayG,
Please can you confirm that the file MRCBTES.DLL exists in the \Windows\system32 folder?
If so, please can you also confirm the version as displayed the Details page of the file Properties dialog box?

Kind Regards,
Macrium Support​​​

RayG
RayG
Advanced Member
Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)
Group: Forum Members
Posts: 265, Visits: 1.2K
Hi JamieW,
Yes it does exist - details as per image below



Regards
RayG
Windows10 Pro X64 V1809 B17763.134 MR v7.2.3858

JamieW
JamieW
Macrium Representative
Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)
Group: Moderators
Posts: 115, Visits: 1.4K
Hi Ray,

Thank you for this.​​

Please can you also confirm that the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\EventLog\System\mrcbt"​​ Registry key exists and contains the values as per the following screenshot?


Kind Regards,
Macrium Support​​

Edited 8 May 2018 7:16 AM by JamieW
RayG
RayG
Advanced Member
Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)
Group: Forum Members
Posts: 265, Visits: 1.2K
JamieW - 8 May 2018 7:15 AM
Hi Ray,

Thank you for this.

Please can you also confirm that the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\EventLog\System\mrcbt" Registry key exists and contains the values as per the following screenshot?


Kind Regards,
Macrium Support

Hi Jamie,
This is my registry entry:

Which shows the problem I think mrcbt.sys?



Regards
RayG
Windows10 Pro X64 V1809 B17763.134 MR v7.2.3858

JamieW
JamieW
Macrium Representative
Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)Macrium Representative (171 reputation)
Group: Moderators
Posts: 115, Visits: 1.4K
Hi Ray,

Yes, the EventMessageFile should be "%SystemRoot%\​​System32\mrcbtes.dll".

You will need to reboot (or restart the EventViewer service)​​​ for any change to take effect.

​​I'm not sure why that has been set incorrectly, but I will look into it and get it​​ sorted for the next update.
​​
Kind Regards,
Macrium Support​​​
RayG
RayG
Advanced Member
Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)
Group: Forum Members
Posts: 265, Visits: 1.2K
Jamie,
FYI
I changed the entry in the registry but it appeared to make no difference on a reboot. I also uninstalled and re-installed MR and after the re-install the registry key was back to the image I posted earlier


Regards
RayG
Windows10 Pro X64 V1809 B17763.134 MR v7.2.3858

1geoff99
1geoff99
New Member
New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)New Member (1 reputation)
Group: Forum Members
Posts: 1, Visits: 25
I changed the EventMessageFile to "%SystemRoot%\System32\mrcbtes.dll" in the registry as described above and rebooted.

The warning message then changed from "The description for Event ID 263 from source mrcbt cannot be found... (etc)"
to
"Created a new tracking file file on device "\Ntfs\HarddiskVolume1"."

So that is the solution to the issue and needs to be fixed in the next update.





RayG
RayG
Advanced Member
Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)Advanced Member (527 reputation)
Group: Forum Members
Posts: 265, Visits: 1.2K
1geoff99 - 26 May 2018 8:45 AM
I changed the EventMessageFile to "%SystemRoot%\System32\mrcbtes.dll" in the registry as described above and rebooted.

The warning message then changed from "The description for Event ID 263 from source mrcbt cannot be found... (etc)"
to
"Created a new tracking file file on device "\Ntfs\HarddiskVolume1"."

So that is the solution to the issue and needs to be fixed in the next update.





Yes I agree changing the registry entry is the solution but the entry should not include the surrounding quotes (") On my system if you include the quotes and then look in event viewer at the mrcbt entries MMC will crash.


Regards
RayG
Windows10 Pro X64 V1809 B17763.134 MR v7.2.3858

Lilien
Lilien
New Member
New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)
Group: Forum Members
Posts: 4, Visits: 12
Hello,
I changed the registry entry weeks ago, but I still get the ​Event ID 263 errors (Win 10/64, 1803).
Shouldn't this be fixed in the latest version?

Regards
 Juergen​​​

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search