Tuesday, August 15, 2017

Warning "Snapshot provider error 0xe00008526. Backup Exec could not locate a VSS software or hardware snapshot provider for this job."


Backup Exec unable to locate snapshot providers installed on the computer.

Error Message

V-79-57344-34086 - AOFO: Initalization failure on: "C:". AOFO used: Microsoft VSS. Snapshot provider error 0xe0008526: Backup Exec could not locate a VSS software or hardware snapshot provider for this job. Select a valid VSS snapshot provider for the target computer.

Application Log :
Log Name: Application
Source: VSS
Event ID: 7001
VssAdmin: Unable to create a shadow copy: The volume shadow copy provider is not registered in the system.
Command-line: 'C:\Windows\system32\vssadmin.exe Create Shadow /AutoRetry=15
C: Drive properties window shows error about VSS Provider:
1. Go to Windows Explorer
2. Right click on C: drive
3. Click " Shadow Copies" tab.
4. Check for this error:
Initialization Failed:
Error: 0x80042304 : The volume shadow copy provider is not registered in the system.


The snapshot provider selected for the backup job is not installed on the server being backed up.


1.  Check that snapshot providers are installed on the system being backed up.
  • Open a command prompt.
  • Type "vssadmin list providers"
  • If nothing is returned, then there is most likely an issue with VSS that will most likely need assistance from Microsoft to resolve
    • You can also verify that VSS is properly registered by checking the following registry key:
      •  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}
  • If writers not listed or show they are in an error state, reboot the server and run the command again

2.  Change the backup job to use a specific snapshot provider.
  •  Open the backup job properties.
  •  Navigate to Advance Open File.
  •  Confirm the "Use advanced open file option" is checked.
  •  Select the appropriate snapshot provider - "Microsoft Volume Shadow Copy Service" with "System" selected in the pull down menu is typically best:

Hyper-V Virtual Machine Error 0x80070569

If you find you are getting a similar error 0x80070569 on Hyper-V 2012, you might be experiencing something similar to this.
Try restarting the Hyper-V Virtual Machine Management Service.

I wasn't sure if I could restart this service while I had Virtual Machines running, but since it was on my home lab environment, I thought I'd give it a shot. The service restarted with no issues on any of my virtual machines. What's more, when I tried to create a virtual machine, it worked, no error. I'm not sure why this happens or why restarting the service fixes it as it seems by the error to be a permissions issue but as a work around it seems to do the trick.

Since installing Backup Exec FP3 Hyper-V backup jobs leave a checkpoint against the virtual machine


Before installing Backup Exec 15 Feature Pack 3 (FP3) , a Hyper-V backup job created a checkpoint (usually visible in the Hyper-V manager). This checkpoint results in the creation of  an AVHDX file against each VHDX file inside the storage containing the virtual machine (VM). However at the end of the backup job the checkpoint and associated AVHDX files are merged and removed/deleted.

Since installing FP3, it can be seen that Hyper-V backups now create a checkpoint (and associated AVHDX files), however even when the backup job finishes, a checkpoint now remains linked to the VM although the checkpoint will be updated during subsequent backup processes.

NOTE: Backup Exec 15 Feature Pack 4 (FP4) and later updates or later Backup Exec versions may also see such symptoms, although the default setting for FP4 and later depends on which Feature Pack (FP) was installed prior to installing FP4 and if it was installed over an FP that already includes the choice, what the current setting for Hyper-V processing was prior to updating.


In the newer versions of Hyper-V, Microsoft have introduced a potentially faster method of performing incremental backups and Backup Exec 15 FP3 implements this new method as a server default (for Hyper-V 2012 and later installations) . This means all Hyper-V jobs (not just newly created jobs) on a given Backup Exec server will use the new settings immediately after FP3 is installed.

The basic concept of the new method is:

    •    A child checkpoint (snapshot) is created to collect the changes.
    •    On incremental backup, a new child checkpoint is created for current changes and then the parent checkpoint is backed up.
    •    When the backup is complete, the child and parent checkpoint is merged leaving only the new combined checkpoint.
    •    This combined checkpoint remains on the system and is used as the new parent for the next backup.
    •    A full backup will backup the current complete state of the VM and not just the parent checkpoint

Extra information:

Within Backup Exec this new method is known as the Faster processing method for Incremental Hyper-V backups with the original method being called the Standard processing method

Backup Exec has supported this new method since Backup Exec 2014 was released however Backup Exec 15 FP3 enabled it as the default method where prior to this, to enable it required the use of Powershell Commands (scripts) which are no longer needed against the FP3 (or later) updates.

FP4 (and later) set the default Hyper-V processing Standard when installing over FP2 and earlier update levels, but honors the current setting when installing over FP3 (or later) update levels. 

The backup job log will clearly show which method was used to perform the backup operation.

With the faster method, a checkpoint is created and remains in place against the VM even if the backup strategy is to only run full backups.

It is possible to revert to the Standard method (see information in the Solution section below), however, it should be noted that if reverting to the Standard method where at least one backup job with the Faster method has already run, then Powershell Commands will be needed to remove the Backup Checkpoints. Typically Hyper-V 2012 R2 installations will not remove the Backup Checkpoints when changing method, but Hyper-V 2012 installations usually will remove the Backup Snapshots. This is because Microsoft changed the behaviour (and the terminology) between these two Operating System versions.

The AVHDX file is often referred to as a differencing disk

The very first time a Faster method backup is performed against a VM, it will result in the Hyper-V-VMMS log on the host containing events 15070 and 10150,  reporting  errors of being unable to remove  a checkpoint. These errors can be ignored unless they happen during every backup operation.

A restore from a backup set created using one method will still work if the server settings have been changed to the other method.

If more than 1 backup checkpoint is present (when a backup job is not running) or more than 2 backup checkpoints present (when a backup job is running) then an issue has occurred that has blocked the removal of a checkpoint. As Backup Exec is calling Microsoft processes it is likely the cause is within the Operating System and not Backup Exec (unless you can see service stability issues against Backup Exec at the time of the backup.)


Backup Admins managing Hyper-V environments should choose between electing to continue using the default Faster method (in which case no further action is necessary) or reverting back to the Standard method. To revert to the Standard method perform the following steps:
  • In the Backup Exec console click the Backup Exec button (yellow button top left) and select Configuration and Settings —> Backup Exec Settings.
  • In the left sidebar of the Settings screen, click on Virtual Machines
  • Change the radio button in the Hyper-V, Incremental Backup Settings to “Use the standard processing method” and click OK
  • For Hyper-V Windows 2012 R2 installation then go to the Hyper-V host and open Powershell
To merge and remove all snapshots use the command
Get-VMSnapshot -VMName 'VM' -ComputerName 'HOST' | Remove-VMSnapshot
although if there are manual checkpoints against the VM that need retaining the to remove just the Backup Checkpoints use the command
Get-VMSnapshot -VMName 'VM' -ComputerName 'HOST' -SnapshotType Recovery | Remove-VMSnapshot

Where VM represents the actual name of your virtual machines as seen in the Hyper-V Manager on the host and HOST represents the name of the Hyper-V host

Note: these commands are case sensitive and can also be used to remove backup checkpoints that due to operating system errors have not been removed correctly. However, customers with these types of issue  should also review the Hyper-V-VMMS logs to understand what may have caused the condition.

Saturday, August 12, 2017

DFSR Event 5012 (DFS Replication)


DFS Replication failed to communicate with a replication group member because the member didn’t have the same configuration information. DFS Replication will retry this operation, which might resolve after configuration changes replicate through Active Directory Domain Services (AD DS).


DFS Replication could not establish a connection with the member. This error can occur for the following reasons:
  • An administrator recently made a configuration change or created a new replication group. If two replication group members obtain their configuration data from different domain controllers, they may have mismatched configuration data due to AD DS replication latencies.
  • An administrator altered AD DS permissions.


Wait for configuration changes to replicate with AD DS

DFS Replication will retry this operation, which usually resolves automatically after configuration changes replicate through AD DS.
To poll immediately for configuration changes, open a command prompt window and then type the following command once for each member of the replication group, where is the domain the server is located in and is the server name:
Dfsrdiag PollAD /Member:\
If this problem persists, verify that AD DS replication is working and that the service is able to reach a domain controller. If the problem persists for 8 hours, the DFS Replication service will disable the connection and log DFS Replication Event 5016.

Test AD DS connectivity

To test DFS Replication’s ability to communicate with AD DS, open a command prompt window and then type the following command: Dfsrdiag pollad /verbose. The command should report Operation Succeeded. If not, there is a problem communicating with AD DS.


To confirm that the issue is resolved, look for DFS Replication Event 5004 in the Event Viewer.crusoe
To manually verify the replication topology, see Repair a Disconnected Topology (http://go.microsoft.com/fwlink/?LinkId=187103 )

Friday, August 4, 2017

Windows Server 2012 How To Create System Restore Point Using Windows Server Backup Feature

In this article, let us see how to enable and use the backup features of Windows Server 2012/2016. Let us go step by step as usual.
1. Go To Server Manager.
2. Click on Next.
3. Select Role-based or Feature based installation and click Next.
4. Select the Server and Click Next.
5. The default roles will be selected. Don’t bother about them and click next.
6. On the Features Wizard, Select the Windows Server Backup Feature and click Install.
7. Once, the installation completes, do a restart of the server and execute the below exe from the Run.
8. The following wizard will appear.
9. On the Right Panel, you will find various options like Backup Schedule, Backup Once, Recover etc., they are self-explanatory as the name explains. Now, let us go with a Backup Once option. For this wizard, I request you to follow the screen shots as there is no explanation required for them.
Now, After the Backup, the System Restore Point will be Created.
Issues faced while creating a Backup.
1. Backup failed to complete. A Volume Shadow Copy Service Operation failed. Please check "VSS" and "SPP" application event logs for more information. Detailed error: The operation ended before completion.
Looking into the EventVWR, the detailed exception was like
The backup operation that started at '‎2013‎-‎10‎-‎08T07:37:24.827000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '0x807800A1'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
To resolve this, I had a look into the below link and got out.
2. System Writer not found.
This is one of the important exception, which I got struck for 2 days and after a long time, I found a useful link about this. There are already a lot of discussions are going on around this.
And moreover, a recent patch for this from Microsoft can be downloaded from here.
Install the hotfix and do a restart. System writer will be listed on your system. To confirm, run the command prompt as administrator and type “vssadmin list writers”.
3. Make sure that, the VSS Service is running.
Probably, that’s all about this. Please do let me know, if you feel that something has been missed.

Sunday, July 16, 2017

Cannot see all users on the domain in Active Directory Import Wizard

Issue: When you use a user to run the Active Directory Import Wizard in Microsoft Dynamics AX, you cannot see all users on the domain. This problem occurs if the user that you use is not domain administrator.
Cause: This problem occurs because some settings on the network domain are required for non-domain administrators to view all users on the domain within the Active Directory Import Wizard in Microsoft Dynamics AX.
To see all users on the domain when you use a non-domain administrator user to run the Active Directory Import Wizard within Microsoft Dynamics AX, follow these steps:
  • Make sure that the user who you use is a part of the “Authenticated Users” security group on the domain. To do this, follow these steps:
  1. In Active Directory Users and Computers, make sure that Advanced Features is selected under the View menu option.
  2. Right-click the user that you cannot see when you run the import wizard. Then, select Properties.
  3. Click the Member Of tab. The user should appear under Domain Users.

  4. Then Click the Security tab, select Authenticated Users Group, and then make sure that the Read Permission for Authenticated Users property is set to Allow.

  • Set up the “Authenticated Users” to have “Read” permissions to all objects. This enables authenticated users to see the complete list of Active Directory users during the import process in Microsoft Dynamics AX. To do this, follow these steps:
  1. In Active Directory Users and Computers, make sure that Advanced Features is selected under the View menu option.
  2. Right-click the user that you cannot see when you run the import wizard. Then, select Properties.
  3. Click the Security tab.
  4. Click Authenticated Users group.
  5. Click the Advanced button.

  6. Select Authenticated Users name, and then click Edit.

  7. Make sure that the Type is set to Allow and that the Applies to: box is set to This object and all descendant objects.
  8. Make sure Read all
    properties check box in Properties section is checked.

After you complete these steps, the Read permission is selected by default when you create a new user.

How to resolve AAD Connect performance counters error (Event 6313)

During a recent upgrade of Azure AD Connect I encountered the following error in the Application event log:
Log Name:      ApplicationSource:        ADSyncDate:          05-12-2016 11:28:21Event ID:      6313Task Category: ServerLevel:         InformationKeywords:      ClassicUser:          N/AComputer:      AADSync.adatum.dk
Description:The server encountered an unexpected error creating performance counters for management agent “adatum.dk”.Performance counters will not be available for this management agent.

After analyzing the issue in details I found that this occur when AAD Connect installation lack permissions to write performance counter information correctly in the local Registry.
To avoid this issue in the first place, always start Azure AD Connect installation or upgrade from an elevated command prompt or an elevated PowerShell prompt.
Fixing the issue after Azure AD Connect is installed, require either that AAD Connect is first un-installed and then properly re-installed (from an elevated command prompt), or that the following changes are done to re-register the ADSync performance counters.
To perform re-registration of the ADSync performance counters, first open an elevated PowerShell prompt and stop the three Azure AD Connect services:
Stop-Service AzureADConnectHealthSyncInsightsStop-Service AzureADConnectHealthSyncMonitorStop-Service ADSync
Next, we need to make a change in the local Registry, but before this ensure that you have a backup of the Registry key.
Open the local Registry and right-click on the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADSync\Performance key
Select Export and save the key to a .REG file
Right-click the following registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADSync\Performance and select Delete
Before proceeding, create a new Performance key in the Registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADSync\
Switch back to the elevated PowerShell prompt and two commands to unload and create the performance counters.
Run the first command to remove performance counters name and explain text for the ADSync performance counters:
unlodctr.exe ADSync
Run the second command to register name and explain text of the ADSync performance counters, based on the information in the mmsperf.ini file:
lodctr.exe “C:\Program Files\Microsoft Azure AD Sync\Bin\mmsperf.ini”
Start the Azure AD Connect service from the elevated PowerShell prompt:
Start-Service AzureADConnectHealthSyncInsightsStart-Service AzureADConnectHealthSyncMonitorStart-Service ADSync
Review the Application log for the event ID 1000 for confirmation that the performance counters are successfully loaded:
Log Name:      ApplicationSource:        Microsoft-Windows-LoadPerfDate:          05-12-2016 11:43:41Event ID:      1000Task Category: NoneLevel:         InformationKeywords:User:          N/AComputer:      AADSync.adatum.dk
Description:Performance counters for the ADSync (Microsoft Azure AD Sync) service were loaded successfully.The Record Data in the data section contains the new index values assigned to this service.

Thursday, July 13, 2017

How to Reset Windows 7 Password

In this tutorial, I will show you how to reset Windows 7 user password
You will need the Windows 7 installation DVD
I am running Windows 7 as a Virtual Machine for demo purpose

Step 1: Boot Into Windows 7 Installation DVD

Boot Into Windows 7 Installation DVD
Click 'Next'

Step 2: Take Note of Windows 7 Drive Letter

Take Note of Windows 7 Drive Letter
In this example is drive E

Step 3: Click 'Command Prompt'

Click 'Command Prompt'
To access COMMAND PROMPT window

Step 4: Replace UTILMAN.exe With CMD.exe

Replace UTILMAN.exe With CMD.exe
-Replace drive letter E with your Windows 7 drive letter
To backup utilman.exe, run command:
copy e:\windows\system32\utilman.exe e:\
-Replace utilman.exe with cmd.exe
copy e:\windows\system32\cmd.exe e:\windows\system32\utilman.exe
-Click 'Restart' to reboot Windows

Step 5: Click 'Easy Access' Icon

Click 'Easy Access' Icon
It will execute cmd.exe which open up command prompt window

Step 6: Reset User Password

Reset User Password
-To reset user password (ex: administrator), run command:
net user administrator 1234
-Replace 1234 with your own password
-Login Windows with that user and the new password

Step 7: Restore Utilman.exe

Restore Utilman.exe
-You will need boot back into Windows 7 installation DVD
-Choose 'Next', then 'Repair your computer'
-Take note of Windows 7 drive letter where it's being install
-Select 'Command Prompt'
-To replace current utilman.exe with the backup in earlier step, run command:
copy e:\utilman.exe e:\windows\system32\utilman.exe
-Click 'Restart' to reboot Windows

Step 8: Check Ease Access

Check Ease Access
-Click on Ease Access to make sure it's the version we just restore
-Login Windows

Step 9: Delete Backup Utilman.exe

Delete Backup Utilman.exe
In Windows, delete e:\utilman.exe (backup copy of utilman.exe we copy earlier to root drive)