VMware Cloud Community
vijayrabha
Contributor
Contributor

unable to create a vss snapshot of the source volume error code 2147754753 (0x80042301) in vmware converter

I'm trying to do P2V for our active directory domain controller. The source machine is a windows 2008 R2. I'm getting a VSS error on the DC.

I'm seeing this error in converter. "Unable to create a VSS snapshot of the source volume. Error code 2147754753 (0x80042301).


The source machine is in DSRM mode as we cannot perform an online migration of active directory domain controller.

On the server I can see log for VSS Event ID 84 i.e. This machine is a Domain Controller in Directory Services Restore Mode (DSRM), Backup cannot be performed in this case, please reboot out of DSRM.

Please help me regarding this as I am stuck and not able to get any resolution for this issue.

Br,

Vijay Rabha

Tags (3)
10 Replies
dhanarajramesh

this might be caused because of windows backup issue. check volume shadow copy dependencies are running if not start those services. vss.JPG

Reply
0 Kudos
vijayrabha
Contributor
Contributor

My VSS is in automatic mode and is started. I ran it again but still no luck. But one thing i notices that I can see only one dependency for my VSS.

12.JPG

Reply
0 Kudos
wmarusiak
Enthusiast
Enthusiast

Why don't you create new virtual machine and install additional domain controller? It is much simpler than P2V of existing domain controller. You just need to transfer fsmo roles afterwards.

Best Regards, Wojciech https://wojcieh.net
Reply
0 Kudos
qroberts709
Contributor
Contributor

vijayrabha​ were you able to perform your P2V while using Windows Server 2008 R2 with VMware Converter on a Domain Controller after? How did you fix the error you were experiencing with VSS?

FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 2147754753 (0x80042301)

Reply
0 Kudos
JoshuaSiwek
Contributor
Contributor

Chiming in on this thread, was anyone able to find a solution to this issue? I'm seeing the same thing and this seems to be the only thread with the error.

qroberts709​ ??

Reply
0 Kudos
qroberts709
Contributor
Contributor

JoshuaSiwek

I was able to convert the physical domain controller running Windows Server 2008 R2 to a virtual machine afterwards. The reason this error was being generated was because VMware Converter uses the Volume Snapshot Service (VSS) to perform a backup as part of the P2V process. You cannot perform a backup using VSS in Safe Mode on a Domain Controller. You are using Safe Mode because it is recommended to do so when P2V'ing a Domain Controller in Directory Services Restore Mode.

My resolution was to perform the P2V of the Domain Controller while booting normally, not in DSRM or Safe Mode. The reason it is recommended to use DSRM when performing a P2V is because you do not want your Domain Controller communicating on the network with other domain attached computers or servers as the database would get corrupted. My P2V VM destination is a network destination so I needed the network enabled anyways. The domain controller server has more than 1 physical network port on the NIC. I plugged in a network cable into the second NIC port, on a network separate from the normal LAN, with only my destination machine for the P2V on that network. I disabled the network adapter that is for the main LAN and left the other adapter enabled which was only for transferring the VM after VMware Converter finished the P2V process.

By booting normally (not safe mode or DSRM), disabling the network adapter that is attached to the main LAN, and then run the P2V via VMware Converter, you should be good to go. This eliminates the risk of the Domain Controller communicating with anything else on the domain while the P2V is in progress.

POCEH
VMware Employee
VMware Employee

Adding error descriptions:

VSS_E_BAD_STATE 0x80042301L A function call was made when the object was in an incorrect state for that function.

from similar thread about DC in DSRM mode:

VSS_E_PROVIDER_VETO 0x80042306L The shadow copy provider had an error. Check the System and Application event logs for more information.

I'm curious - why not try to stop the DC service and then convert?

HTH

Reply
0 Kudos
JoshuaSiwek
Contributor
Contributor

Thanks so much for the reply! You are absolutely right I was trying this in DSRM mode (as recommended) I will give this a shot and let you know how it goes, thanks again!

Reply
0 Kudos
JoshuaSiwek
Contributor
Contributor

Everything I had read about P2Ving a DC recommended trying it in DSRM mode so as to prevent AD issues, so that is why we were attempting there.

Though I don't have clearance to do so until Saturday, that is exactly what I'll be trying next, thanks!

qroberts709
Contributor
Contributor

JoshuaSiwek

No sweat. I spent a couple weeks attempting this multiple times and this solution worked the best, honestly I ran into 0 issues with the process I outlined above.

Reply
0 Kudos