paddy80
Contributor
Contributor

ERROR: Failed to take snapshot of a source volume. Possible causes include not having any NTFS volumes on Windows XP or Windows 2003 source systems, and not having enough free disk space

Hello

Having resolved the problem with the Administrator Account, I have allready the next problem: I am still trying to convert my physical computer in a virtual machine. I use the Conversion Wizard from vmware Workstation 6.5.3 ("File", "Import or Export..."). In the first step I select "phydical Computer" as sourcetype. In the next step I choose to convert "this local machine". In the next step I choose to convert only my system disk C:\ (Total Space 698 GB, used Space 88,6 GB). For the new size in the virtual machine I choose the minimal size whitch is 97,49 GB. The checkbox "ignore page file and hibermation file" is activated. In the next step I select "other virtual machine" as destination type. On the next step I give the name "BasisVista" for the new virtual machine. As location I choose "D:\VirtuelleMaschine" (D:\ is another local harddisk. Total Space 931 GB. Used Space 14,3 GB). I choose to create a virtual machine of a "vmware Workstation", Version "6.5.x" type. In the next step I choose to "allow virtual disk files to expand". I do not activate the checkbox "split disk into 2 GB Files". In the next step I do no changes, so I have NIC1 - NIC4, with a bridged network and the checkbox "connect at power on" activated. In the last step I choose to "install the vmware Tools". I do not activate "customize the identity of the virtual machine". I activate the checkbox "Remove all system restore checkpoints (recommanded). So all steps in the wizard are completed and i can start the creation of the new virtual machine. The creation procedure starts for some seconds, and after some seconds, the procedure stops with the following error:

"ERROR: Failed to take snapshot of a source volume. Possible causes include not having any NTFS volumes on Windows XP or Windows 2003 source systems, and not having enough free disk space."

I really do not know what I could do now: I have Vista home premium 64 Bit installed as OS. I have two local harddiscs. They are both on NTFS. As mentionned above, there is enough of free disk space... I have an intel(R) Core (TM)2 Duo CPU E8500 Processor with 3,16GHz. (4GB Ram).

Now I need your help please! Thank you!

Paddy

0 Kudos
5 Replies
jokke
Expert
Expert

Can you verify that 3 services are running; eventsystem, swprv, vss?

What does "vssadmin list writers" return?

Joakim

0 Kudos
paddy80
Contributor
Contributor

Hello

Thank for this fast response!

I am a newbi with vmware Workstation, so I think i will need further information... and I have a german OS so I dont know how the services called in english... I looked for the services you mentionned. I didnt find the services exactly like you wrote them. But I found a service called "vmware Agent Service". This one was not started. I started it. Now I will retry the converting procedure....

What do you mean with "What does "vssadmin list writers" return?"?

Perhaps you know, how the services are called in a german OS? Thank you for further information.

Paddy

0 Kudos
jokke
Expert
Expert

What I meant was the internal windows service name. Open cmd and type (as admin) "sc queryex vss" and "sc start vss". vssadmin.exe should hopefully have the same name over different languages so should not matter. Open cmd once again as admin and type "vssadmin list writers".

0 Kudos
paddy80
Contributor
Contributor

Hi,

OK here are the results: Result of queryex vss:

SERVICE_NAME: vss

TYPE : 10 WIN32_OWN_PROCESS

STATE : 1 STOPPED

WIN32_EXIT_CODE : 1077 (0x435)

SERVICE_EXIT_CODE : 0 (0x0)

CHECKPOINT : 0x0

WAIT_HINT : 0x0

PID : 0

FLAGS :

==================================================

Result of sc start vss :

SERVICE_NAME: vss

TYPE : 10 WIN32_OWN_PROCESS

STATE : 2 START_PENDING

(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)

WIN32_EXIT_CODE : 0 (0x0)

SERVICE_EXIT_CODE : 0 (0x0)

CHECKPOINT : 0x0

WAIT_HINT : 0x7d0

PID : 4672

FLAGS :

==========================================================================

If understand it correctly, the command "queryex vss" is to query the actual state of the service. The command "sc start vss" is to start the service. So after I started the service, I requeried the actual state and it says now:

SERVICE_NAME: vss

TYPE : 10 WIN32_OWN_PROCESS

STATE : 4 RUNNING

(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)

WIN32_EXIT_CODE : 0 (0x0)

SERVICE_EXIT_CODE : 0 (0x0)

CHECKPOINT : 0x0

WAIT_HINT : 0x0

PID : 4672

FLAGS :

====================================================================

So finally the results of "vssadmin list writers":

vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes

(C) Copyright 2001-2005 Microsoft Corp.

Verfassername: "ASR Writer"

Verfasserkennung: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Verfasserinstanzkennung: {d5932a57-a3d7-4241-a41a-0f87e19353c1}

Status: Stabil

Letzter Fehler: Kein Fehler

Verfassername: "System Writer"

Verfasserkennung: {e8132975-6f93-4464-a53e-1050253ae220}

Verfasserinstanzkennung: {75f32776-3277-47ce-8f53-b19b58fb6231}

Status: Stabil

Letzter Fehler: Kein Fehler

Verfassername: "Registry Writer"

Verfasserkennung: {afbab4a2-367d-4d15-a586-71dbb18f8485}

Verfasserinstanzkennung: {e28495bb-d972-4d6f-873c-bd371feff2a9}

Status: Stabil

Letzter Fehler: Kein Fehler

Verfassername: "SqlServerWriter"

Verfasserkennung: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

Verfasserinstanzkennung: {8bf2e2c0-05f3-4d54-a9ff-cc3628de45c4}

Status: Stabil

Letzter Fehler: Kein Fehler

Verfassername: "Shadow Copy Optimization Writer"

Verfasserkennung: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

Verfasserinstanzkennung: {8ceea6d4-1a8e-4132-a416-88112b6fd4e0}

Status: Stabil

Letzter Fehler: Kein Fehler

Verfassername: "COM+ REGDB Writer"

Verfasserkennung: {542da469-d3e1-473c-9f4f-7847f01fc64f}

Verfasserinstanzkennung: {5b65c45c-bbe5-43f3-996e-3a5ec1819afa}

Status: Stabil

Letzter Fehler: Kein Fehler

Verfassername: "WMI Writer"

Verfasserkennung: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

Verfasserinstanzkennung: {e6171ee8-5117-495b-b516-6960ea962a2a}

Status: Stabil

Letzter Fehler: Kein Fehler

Verfassername: "MSSearch Service Writer"

Verfasserkennung: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}

Verfasserinstanzkennung: {aa00c43c-f942-4e7b-a6c7-207b049383e8}

Status: Stabil

Letzter Fehler: Kein Fehler

Verfassername: "BITS Writer"

Verfasserkennung: {4969d978-be47-48b0-b100-f328f07ac1e0}

Verfasserinstanzkennung: {2198445e-e8f7-4ff4-bb01-187c1f24a720}

Status: Stabil

Letzter Fehler: Kein Fehler

===========================================================

So after I started the the Service "Vmware Agent Service" and after starting and quering the vss service, I retried to convert the physical PC in a vm. But it still doesnt work... Same Error after beginning the procedure...

What else could I try?

Paddy

0 Kudos
continuum
Immortal
Immortal

assign a larger disk before anything else - using so little overhead results in a vmdk that you want to expand tomorrow

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos