The system cannot access one or more event logs because of insufficient rights
Configuration refresh message. The system cannot access one or more event logs because of insufficient rights, file corruption, or other reasons. For more information, see the Operation channel in the ServerManager-ManagementProvider error log on the target server.
Problem occurred on Server 2012 servers that have been upgraded to Server 2012R2 servers. Servers are also clustered.
Following the event logs leads to a few registry keys. You can eliminate the messages by:
1. Export the following registry keys (for safety)
Access to drivers on Windows Update was blocked by policy EventID:122 errors appearing on Windows
Server 2012 Hyper-V host.
“Device Setup Manager” service. There is a scheduled task that runs each night
in “Microsoft | Windows | Device Setup” called “Metadata Refresh”. When that task runs it causes the “Device
Setup Manager” service to start, and that’s what is causing the messages. If you look in the Event Viewer under
“Application and Services Logs | Microsoft | Windows | DeviceSetupManager |
Admin” and filter on Event ID 122 then you can see the entries.
The “policy” that is causing the block is actually the Device Installation
Use the search in the
Control Panel window and look for “device installation” When that window
opens, you will see the settings that define the “policy” If you change the
setting to “Always install the best driver software from Windows Update.” then
the Event ID 122 errors will go away. If you *also* select
the “Automatically get the device app…
Hyper-V is not in a state to accept replication on the replica server for virtual machineMessage appears at the end of the replication Wizard. A replica for this virtual machine had previously existed on the Replica server.
CauseThe previous successful or unsuccessful replicated virtual machine may be still exist at the replica server.
SolutionRemove the old virtual machine at the replica server and enable replication again.
Yes this pushes a fresh replication to the replica server.
Additional notesUnder the details of the error message on the source server a Virtual machine ID is listed, and using this ID to find the replication files from the previous replication on the Replica server (under \Virtual Hard Disks\Hyper-V Replica\Virtual hard disks\<ID>\ and under \Virtual Hard Disks\Hyper-V Replica\Virtual Machines\<ID>. These files may be locked while a previous replica exists on the Replica server