Good afternoon. It has been too long since I last posted. Today I found a solution to a problem I have seen several times and I wanted to share it.
I had a customer that was experiencing backup issues with a new load of Windows. When trying to backup the server in Windows Serer Backup the backup would always fail with the error “Windows Backup failed to create the shared protection point on the …”. An important point to note is the error would always occur during the VSS snapshot phase of the backup.
Below is the resulting Application event log with the key event highlighted.
At this point it is probably helpful to get a high level overview of how Windows Server Backup and VSS work. When Windows Server Backup starts a backup one of the first steps is to call VSS to take a snapshot. When the backup destination is local disk, the request is for both the backup destination and the backup source. This is so that Windows Server Backup can compare the blocks in both to perform an incremental backup. This means that a failure to snap the source or destination can cause the backup to fail.
I have seen this issue a handful of times and the consensus was the backup drive was causing the problem. While this can be the case, today I learned how to pinpoint which volume is actually causing this error with the event log. The key to determining this is the volume GUID ( Globally Unique Identifier) specified in the description of the event. This is the volume that cannot be snapped by VSS and is causing the backup to fail.
So how do you take the GUID and get the drive letter? This is the easiest part. Simply open an admin cmd window and run the command “mountvol”. At the end of the output all volumes with GUIDs and drive letters will be listed. In our case it was the D:\ drive that contained user data. We ran a test backup excluding the D:\ drive and it completed with no errors.
How do I fix the volume, so it will backup? Obviously we will not want to exclude a volume from the backup. There are two methods to repair this issue. First a chkdsk /f can be run to attempt and repair the volume. If that fails though, then you are likely looking at a bit of work to recreate the volume. Here is the process:
Backup the data with robocopy or another file level backup utility. For robocopy an example command: robocopy <source> <destination> /MIR /XJ /W:5 /R:3 /LOG+:c:\robolog.txt
Run diskpart and “clean” the disk. To do this run diskpart at an admin cmd, select the problem disk, then run the clean command.
Recreate the volume
Restore the data with robocopy or whatever file level backup utility used previously.
I hope you have found this post informative. If you have another way to solve this problem I would love to hear about it in the comments.
Good morning. It has been a while since I posted, so I figured it was time for another article. I ran across an interesting issue this morning that I figured I would share. I had a customer that had recently experienced some file system corruption on the C: drive. Luckily chkdsk was able to correct the issue, but there was an issue that cropped up after running it. My customer was seeing an error in the Windows system log coming up frequently. The error was a 7005 with a source of Server Control Manager. The description was his concern though. “The LoadUserProfile call failed with the following error: The configuration registry database is corrupt.”
I did some research on this error and it is caused by a corrupt user profile. I figured it was probably a service user account as we had several services starting within seconds of each occurrence. Through a process of elimination I discovered that starting any service using the Network Service as the logon service caused the error.
So now I knew which account was causing the error, but how do you recreate the user profile for the Network Service user? I first checked the c:\users folder and the profile is not there. It is also not in the user profiles list in the system properties. I checked the registry as it has a list of all users with profile locations. HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
The Network Service profile is located in C:\Windows\ServiceProfiles\NetworkService. I renamed the profile in the registry (S-1-5-20) to S-1-5-20.old and the NetworkService folder to NetworkService.old.
I then started a service that used the Network Service account, and success. The registry key was recreated, as was the folder, and we received no errors in the event log.
On a side note the above process will also work for the Local Service account. Just rename the appropriate registry key and folder.
I hope you found this article informative. If you have anything to add or would like to suggest an edit, please do so in the comments below.
Good morning. I had a question today on what to do if the hard drives are not detected when performing a bare metal restore. Loading the driver is pretty straightforward, but I could not find a good guide on the whole process, so I figured it was time to put one together. Below I will outline with screenshots the process to do a bare metal restore. The screenshots will be from Windows Server 2016, but the process is the same for all currently supported versions of Windows.
We start by booting to the Windows media. After selecting the language, you have two options; Install now or Repair your computer. Choose Repair your computer.
The next screen may give you more or fewer options. Choose Troubleshoot.
From the Advanced options screen, choose System Image Recovery.
If given the option for a target operating system, choose the one applicable to you.
On the following screen, you will have two options; Use the latest image or select a system image. If you want to restore the latest backup, then you simply need to click next. If however you want to restore an earlier backup, choose the option to select a system image. This guide will continue with the second option.
If you have only one backup drive, then only one line item will show. A line for each backup drive will be displayed on this screen. Choose the backup drive to restore from and click Next.
On this screen all the available backups are displayed to restore from. Select the preferred backup to restore and click Next.
This screen provides three important options. The first is to format and repartition the disks. Select this option to completely wipe the drive being restored to. It is possible to exclude data drives from this by clicking the exclude drives button and checking the drive to exclude. The second option will only restore the system drives. Keep in mind though, if the page file was moved a data drive, that drive is now considered a system drive and has to be part of the restore. The last option is to install drivers. Do this if the drives being restored to are not detected by the restore wizard. Once all desired options are selected, click Next.
This screen is a summary of the restore. Click Finish to start the restore process.
After clicking yes on the prompt, the rest of the process is automated. The server will be restored and automatically boot back into the restored Windows OS.
I hope you found this post informative. If you have anything to add or suggest, please do so in the comments below.
Good morning. It has been some time since I last posted. I had an interesting case though I figured I would share. I had a customer that was attempting to enable BitLocker on his C: drive. When running the wizard it would immediately fail with the message “An internal error was detected.”
I had to do a bit of research as that error is a little vague. I was able to get the error code associated with this error when running manage-bde command. With the error 0x80290107 I was able to find a forum post that indicated the root issue. BitLocker in Windows Server 2012 R2 does not support the SHA256 encryption algorithm. After changing the bios setting to SHA1, BitLocker worked without issue.
So if you have Windows Server 2012 R2 with TPM 2.0 and you get the above error enabling BitLocker on the C:, verify that the TPM is set to use SHA1 encryption.
I hope you found this post informative. If you have anything to add or just want to comment, please do so below.
I ran into an issue that took me quite a bit of time to resolve that I wanted to share with everyone. I had a customer that I worked with that was not able to start any VM (virtual machine) across 3 Hyper-V servers he had deployed in his environment. When attempting to start the virtual machine it would get to starting…4% and then give a pop-up error message “<VM Name> failed to initialize”. My first stop was the Hyper-V VMMS log which contained the same error. I eventually checked the application log and found this event:
This led me to a topic referring to an issue with January 2018 windows updates. You can find that article here. I uninstalled all updates in January and February on the first server, but this made no difference. The solution was to change 2 registry keys:
I ran across an interesting issue I wanted to share. I had a customer that recently had a migration performed. Previously he was running SBS (Small Business Server) 2011 and is now running Windows Server Essentials 2016. After demoting and removing the SBS 2011 server, he started receiving the following error on every boot.
The error is quickly followed by an informational message indicating that DFSR (Domain File System Replication) successfully connected to a domain controller.
Based on my previous experience with similar issues I posited that the problem was due to the DFSR service starting before either the network stack was fully initialized or before the DNS (Domain Name System) service was running.
I explained that based on the behavior this could safely be ignored. This did not go over very well as the error also shows up in the Windows Essentials health report. This brings us to the solution. And this solution will work for just about any service that needs a little more time at boot. We set the startup type for the DFSR service to Automatic (Delayed Start). We restarted the server and this eliminated the 1202 error.
I hope that you found this article informative. If you have anything to add, please feel free to leave a comment below.
Good morning. In case you haven’t guessed it already I typically write these posts in the morning. As I write this now it is 6:30AM. Today I wanted to share a command line utility I just recently discovered. It has been part of Windows for quite some time though. At least since Windows Server 2008. The utility is called diskshadow. This utility allows direct interaction with VSS (Volume Shadow Copy Service). You can find the Microsoft technet article here. In this article I will go over how I used it to troubleshoot a recent issue with VSS.
I was recently troubleshooting a VSS where the snapshot was failing on release. As is typical, my customer was using a 3rd party backup software. I wanted to test outside of the backup software, so we installed the Windows Server Backup feature and tried that. Unfortunately the symptoms were identical. After quite a bit of digging I ran across the diskshadow utility. With that utility I received a different error which led me down the path of discovering the problem. It turned out that the backup software’s filter driver was stepping on VSS and causing the failure. After removing the backup software, VSS worked without issue.
So how is the diskshadow command used? It can be used to create a snapshot, mount an existing snapshot, restore a snapshot and several other things. Below I will cover the commands to take a VSS snapshot, as that is the functionality I find most useful. To take a snapshot of the C: drive and test the majority of the VSS writers there are just 3 commands that need to be run.
diskshadow (This starts the command and puts you at a diskshadow prompt. This is similar to ntdsutil and nslookup.)
add volume c: (This adds the C: drive to the snapshot. You could substitute another drive letter if you want to test a specific writer. The command can also be repeated with other drive letters to include them in the snapshot.)
create (This starts the snapshot process with VSS. It is important to note that the create command by itself will create a non-persistent snapshot. That is the snapshot will be removed on exit from the diskshadow utility. A persistent snapshot can be created with additional parameters.)
This utility is considerably faster when troubleshooting VSS, taking only about 1-2 minutes to take a snapshot or fail. It also removes the requirement for a USB drive to temporarily store a backup. For these reasons I will be using whenever troubleshooting VSS in the future.
I hope you found this article informative. If you have anything to add or just want to leave a comment, please do so below.