Unable to create a VSS snapshot of the source volume(s). Error code: 259 (0x00000103).

[metarushej]

Hi,

We are virtualising a Win 2011 SP1 server using VMware vCenter Converter Standalone - running locally on the server.

We encounter @ 3% complete.

The error code is  FAILED: Unable to create a VSS snapshot of the source volume(s). Error code:

259 (0x00000103).

Can anyone advise on what might be causing the error\how to resolve?

Thank you

John

[daphnissov]

The last version of Converter to support Windows 2000 was version 4.0, and even then it required SP4 be installed. Regardless, I think you're going to need SP4 anyhow.

[metarushej]

Sorry, the source server is a Windows SBS Server 2011 SP1.

Regards

[Rosen Tomov]

Seems that snapshot creations take too long time ( > 5min)

Try again, after worker service restart, or to limit number of active snapshots via vssadmin command, or to exclude some disk(s) from conversion.

HTH

[RajeevVCP4]

Refer this KB

VMware Knowledge Base

VMware Knowledge Base

[metarushej]

Hi,

Apologies for the delay in replying here.

I have done some further analysis here and can see that the event log contains the following error.

Exchange VSS Writer (instance b**********************************) failed with error code -2147221233 when preparing for Snapshot.

Any insight that can be provided into the above would be appreciated.

Thank you

[daphnissov]

This is a Windows/Exchange issue and not one that is VMware related.

[metarushej]

Hi,

Sorry, I saw an Exchange-related error VSS error in the evet log and assumed that this was related to the problem. I see that the Converter job continued past that point so I guess that the the xchange-related error VSS error is not the root cause.

Does anyone know what  Error code: 259 (0x00000103) is \what its cause is?

Thank you.

[Rosen Tomov]

More clear explanation that "snapshot creations take too long time ( > 5min)" is not possible.

[metarushej]

Hi,

Based on your feedback (snapshot take too long), I shut down a number of database services on the server to free up resources.

I found that the migration then ran successfully.

Thank you!

[Alex_Romeo]

Hi,

It's a bit old and the version isn't the same thing, but I think it might be useful.

[SOLVED] VMWare converter failed - Spiceworks

[SOLVED] VSS causes image push to fail - VMware Forum - Spiceworks - Page 2

Alessandro Romeo

[liam-ng]

I found a way to increase the VSS timeout value or by sheer luck.
I'm using VMware vCenter Converter 6.6.0, converting a 1-TB VM (v2v) from ESXi 6.7 to ESXi 8.0u2. 

I tried restarting VMware services, stopping background services (even though it's at 1% utilization), editing converter-agent.xml (read/writeTimeoutMs), restarting VM, no luck with all of those.

Here's the fix that worked for me:

Using the registry editor, "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform"

- If need be, create a new registry value of type DWORD with name "CreateTimeout"

- Change value to 12000000(2*10*60*1000 = 20 mins) in decimal

I couldn't find supporting document behind this regkey, and there's a typo, the value should be 1,200,000 for 20 mins.

Source: How to Fix VSS Timeout Error VSS_E_FLUSH_WRITES_TIMEOUT | BC Blog (backupchain.com)