4.0 Converter Error Code 2147754776 (0x80042318)

[rbenash]

At a loss at this point. Brand new reformatted FAT32 external USB harddrive on an XPpro Laptop. I can succesfully R/W to this drive, create folders, etc so seems fine.

Download and run 4.0 Converter and persistantly receive the following after about 3 minutes:

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

2147754776 (0x80042318).

Simply trying to create a VM for this physical powered on machine to the USB drive which is empty

Trying to create a VM of this machine before returning it. Lots of work ahead if I can simply create this VM and run it on the new host.

Any help would be appreciated. Read the manuals and notes. Couldn't find this error code mentioned. Email to VMware - they sent me here.

Thanks

[rbenash]

Sorry - logs attached here.

[victorg]

You may want to check the Events Viewer -oftentimes it has an error message from VSS provider.

[rbenash]

Events Viewer? Might not be clear on just what you are talking about. The error message I provide is coming from the Standalone Converter status during the task.

[rbenash]

Please note that I also have SR1163514835 case opened on this issue.

[rbenash]

Just an update with added detail. I do have VSS errors in the logs for each of about 20 or so attempts to run the converter. Error message example below. I am also attaching my event logs. I am running a backup service on this machine - Connected Data Protector. I had tried disabling this service during a few of the attempts but that did not seem to help. If anyone has any suggestions or has seen this problem before I would be grateful for any input or suggestions on how to resolve.

Event Type: Error

Event Source: VSS

Event Category: None

Event ID: 12302

Date: 3/21/2009

Time: 9:39:05 AM

User: N/A

Computer: RBENASH-WXP

Description:

Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 42 55 45 43 58 4d 4c 43 BUECXMLC

0008: 33 36 33 37 00 00 00 00 3637....

0010: 42 55 45 43 58 4d 4c 43 BUECXMLC

0018: 33 36 30 37 00 00 00 00 3607....

Event Type: Error

Event Source: VSS

Event Category: None

Event ID: 5013

Date: 3/21/2009

Time: 9:39:05 AM

User: N/A

Computer: RBENASH-WXP

Description:

Volume Shadow Copy Service error: Shadow Copy writer ContentIndexingService called routine RegQueryValueExW which failed with status 0x80070002 (converted to 0x800423f4).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 57 53 48 43 4f 4d 4e 43 WSHCOMNC

0008: 32 32 39 32 00 00 00 00 2292....

0010: 57 53 48 43 49 43 00 00 WSHCIC..

0018: 32 38 37 00 00 00 00 00 287.....

[victorg · Accepted solution]

I don't think your problem is with Converter. I googled your VSS error message and found MS KB article: http://support.microsoft.com/kb/907574. Sounds like the problem you have in your setup.

[rbenash]

Hi Victor - yes that's correct. After working with Converter support yesterday I was off researching the VSS events and came to the same conclusion as far as which MD would apply. Once I applied Microsoft update fix M907574. Found an entry left in the registry location referred to in that update. Once removed VSS errors disappeared.

[gefraenk]

I resolved the problem by

1) running vssadmin list writers, gave the following error: 0x8000ffff

2) regsvr32 ole32.dll

3) re-run vssadmin list writers which gave:

C:\Documents and Settings\jojje>vssadmin list writers

vssadmin 1.0 - Volume Shadow Copy Service administrative comma

(C) Copyright 2001 Microsoft Corp.

Writer name: 'SqlServerWriter'

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

Writer Instance Id: {cfbc32b5-f1ac-4813-97ca-30eb4b2ff9b0}

State: Stable

Writer name: 'Microsoft Writer (Bootable State)'

Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}

Writer Instance Id: {10cebadd-b437-4625-ad27-f76349a42815}

State: Stable

Writer name: 'Microsoft Writer (Service State)'

Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}

Writer Instance Id: {6e45dec1-b45e-4604-bd1a-e93a16b1563d}

State: Stable

Writer name: 'MSDEWriter'

Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}

Writer Instance Id: {ef32e9f8-1332-430b-999d-a63d94fca803}

State: Writer name: 'IIS Metabase Writer'

Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

Writer Instance Id: {cc73828c-cd53-443a-b2cc-b128a7e31545}

State: Stable

Writer name: 'WMI Writer'

Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

Writer Instance Id: {f4baf031-7d2e-4912-919b-9b3d612912ae}

State: Stable

Been able to run VMconverter 4.01

[AnalogKid99]

Microsoft KB907574 helps.

The 'rouge' app in my case was Visio

The registry settings were deleted for Visio and all was fine after

[davis_cruz]

Registering ole32.dll worked perfectly for me.

Thank You!

[Haiikal]

MAX FILE SIZE for FAT32 is only 4GB. If your physical machine is larger than 4GB, it will not work.