Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, February 25, 2014 7:22 AM
I have Windows 2003 server installed on IBM 226 Server and oracle forms and report server is running on it. While converting P2V using VMWARE Vcenter Converter standalone it is giving error " FAILED: Unable to create a VSS snapshot of the source volume(s). Error code:2147754758 (0x80042306)." I have contacted VMWARE then they told me it is Microsoft problem so you involve micosoft into it. SO, please help in this regards. Thank you in advance.
All replies (4)
Tuesday, March 4, 2014 7:01 AM âś…Answered
Hi,
Firstly, please check the value type of TypeLib under the following key should be Reg_Expand_SZ. If the type is Reg_SZ, it triggers the issue which VSS fails to return all the writers.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem
\26c409cc-ae86-11d1-b616-00805fc79216}\EventClasses
\FAF53CC4-BD73-4E36-83F1-2B23F46E513E}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}]
Please also check if you run Control-M service on the server, if so, stop the Control-M service to see if VSS writer is still not listed.
Regards,
Mandy
Tuesday, February 25, 2014 8:04 AM
Before redirecting your problem to MS, it is useful to search VMware knowledge base. This may give you the fastest answer. Does the following correspond to your case?
Regards
Milos
Wednesday, February 26, 2014 6:37 AM
After applying article 940184 and 2009533, vssadmin list writers it is not showing "VSS writer". The output of vssadmin list writers is as follows
C:\Documents and Settings\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {db299c38-18e8-40a8-bee5-2906c0cdbeaf}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {0f4d9c13-5b8f-413d-8805-0f2dfef960ef}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {0717b861-20a0-42e0-ae83-355c1ec546a7}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {3427ef3b-2b25-49fb-9cc7-033583c9cf10}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {00abad12-0ffc-48a7-8230-f5aa65a1bb79}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {bb8af583-3d7f-4eee-bc7a-181592ef4847}
State: [1] Stable
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {b48f90ab-c05d-4f8f-8593-072580bdbae1}
State: [1] Stable
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {6c6c7b64-61f6-4cb9-a491-c8b32bf545b6}
State: [1] Stable
Last error: No error
Please help.
Sunday, August 24, 2014 6:29 PM
Firstly check size in the creation place and check the performance in VM ware when the creation progressing.
As a simply ( PROCESSOR, RAM ).
and reply me when you have any problems.