Sysadmin Bloggers

DEconfiguring Failover of DHCP failed with error 20116

Hi Guys

Today I am going to tell you if your getting a error when you force removing a DHCP failover from a Partner server or a Primary server and getting the below error.

open the Powershell and run the below command but to run the below command you have to find the Replication name of the failover server for that you can check from the below screenshot.

In the above screenshot the Blue line is the Relationship name in the failover.

So once you got the name run the below command in PowerShell and then you can delete the scope as it will be removed from the failover.

Remove-DhcpServerv4FailoverScope -ComputerName "dhcpserver.contoso.com" -Name "SFO-SIN-Failover" -ScopeId 10.10.10.0,10.20.20.0

In the above command change the computername and the Relationship name and also the scope

once you run this command the scope will be removed from the failover and then delete the scope and

re-create the failover from the primary server.

Comments

Popular posts from this blog

PowerShell DSC log amount issue on operating system drive Overview Problem Impact Microsoft Ticket (Workaround) solution References Overview When using PowerShell DSC on a configured system in some (seldom) cases it can lead to log amount issues in a specific folder. The following folder grows (over time) so several GB size holding hundreds and thousands of JSON log files as visible in the following screenshot: Also sometimes it looks like this: Problem The problem is (but must not be) related to DSC configuration issues as far as it could be analyzed. The log folder „Configuration Status“ is filled with sometimes up to 7 Megabyte sized JSON files. This log folder (based on our analysis) is used for sending reports to report server but is not cleaned up automatically. Impact Some PowerShell DSC managed systems need extensive disk space due to log directory grown to 40 Gigabyte plus. This causes an alert in disk space / availability monitoring and could in some cases lead to non w...

Vm backup failling with snapshot error (156)An error occurred while saving the snapshot: Failed to quiesce the virtual machine.

Hi Everyone, I am here back with another issue. If anyone is getting error taking backup snapshot of a virtual machine and getting the below error. Vm backup failling with snapshot error (156)An error occurred while saving the snapshot: Failed to quiesce the virtual machine. Apr 28, 2021 2:22:55 AM - Critical bpbrm (pid=15849) from client XXXXX: FTL - vSphere_freeze: Snapshot task for virtual machine XXX-YYY (/vmmor/vm-341) failed, 0 retries remaining, error type: 263, error message: An error occurred while saving the snapshot: Failed to quiesce the virtual machine.. Apr 28, 2021 2:23:08 AM - Critical bpbrm (pid=15849) from client XXXX: FTL - vfm_freeze: method: VMware_v2, type: FIM, function:...

How To Resolve VSS Writer Errors Without Rebooting (VShadow)

Background This article describes how to resolve VSS Writer errors without rebooting Windows. Here are the scenarios in which you'd want to use these instructions: Scenario 1: Failed VSS Writers. There are instances when backups are failing due to an agent's VSS writers being in a failed state, but it is impossible or not desirable to restart the server until at least after business hours. Scenario 2: VSS Writers Not Started There may also be a writer that is not running and needs to be. Running the command - " vssadmin list writers" will only show a list of writers that are currently started Scenario 3: Using VShadow for Windows Server 2003 or XP VSS is available in the Volume Shadow Copy Service 7.2 SDK, which you can download from the Windows Download Center . Troubleshooting Troubleshooting Scenario 1: Failed VSS writers Find the failed VSS writers and their associated services, and restart them: 1) Run Command Prompt as Administrator (...