vCenter

 View Only
  • 1.  Converter fails on Server 2008 R2 P2P

    Posted Mar 27, 2013 03:14 PM

    I am trying to P2V several servers running Server 2008 R2. They all fail at about 1 minute with the error:

    Failed: Unable to create a VSS snapshot of the source volume.
    Error code: 2147754767 (0x8004230F)

    I have tried using VMware-converter-all-5.0.1-875114 and also VMware-converter-en-5.1.0-1023810. I have verified the Microsoft Software Shadow Copy Provider and Volume Shadow Copy services are enabled and running.

    The evens logs show the following:

    Cannot find anymore diff area candidates for volume \\?\Volume{de61058e-ec3e-11df-8b61-806e6f6e6963}\ [0]
       0x8000ffff, Catastrophic failure 
       Operation: Automatically choosing a diff-area volume Processing EndPrepareSnapshots Context: Volume Name: \\?\Volume{de61058e-ec3e-11df-8b61-806e6f6e6963}\ Execution Context: System Provider
       2D20436F64653A20535052414C4C4F4330303030313137342D2043616C6C3A20535052414C4C4F4330303030303739302D205049443A202030303030343432382D205449443A202030303030313533322D20434D443A2020433A5C57696E646F77735C53797374656D33325C737663686F73742E657865202D6B2073777072762D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820


    {b5946137-7b9f-4925-af80-51abd60b20d5}
       EndPrepareSnapshots({548287c0-1abd-47b7-8d28-4be21b0ed700})
       0x80042302, A Volume Shadow Copy Service component encountered an unexpected error. Check the Application event log for more information. 
       Operation: Executing Asynchronous Operation Context: Current State: DoSnapshotSet
       2D20436F64653A20434F52534E50534330303030313632342D2043616C6C3A20434F52534E50534330303030313630352D205049443A202030303030313434342D205449443A202030303030343236342D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820

    Cannot find anymore diff area candidates for volume \\?\Volume{de61058e-ec3e-11df-8b61-806e6f6e6963}\ [0]
       0x8000ffff, Catastrophic failure 
       Operation: Automatically choosing a diff-area volume Processing EndPrepareSnapshots Context: Volume Name: \\?\Volume{de61058e-ec3e-11df-8b61-806e6f6e6963}\ Volume Name: \\?\Volume{de61058f-ec3e-11df-8b61-806e6f6e6963}\ Execution Context: System Provider
       2D20436F64653A20535052414C4C4F4330303030313137342D2043616C6C3A20535052414C4C4F4330303030303739302D205049443A202030303030343432382D205449443A202030303030313533322D20434D443A2020433A5C57696E646F77735C53797374656D33325C737663686F73742E657865202D6B2073777072762D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820


    {b5946137-7b9f-4925-af80-51abd60b20d5}
       EndPrepareSnapshots({529e729a-77c0-4b87-8f30-a35e4ad66b43})
       0x80042302, A Volume Shadow Copy Service component encountered an unexpected error. Check the Application event log for more information. 
       Operation: Executing Asynchronous Operation Context: Current State: DoSnapshotSet
       2D20436F64653A20434F52534E50534330303030313632342D2043616C6C3A20434F52534E50534330303030313630352D205049443A202030303030313434342D205449443A202030303030323332342D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820

    The diagnostic logs are attached from one of the servers.
    Any suggestions on how to fix this??



  • 2.  RE: Converter fails on Server 2008 R2 P2P

    Posted Mar 27, 2013 05:45 PM

    This is a VSS error, it is not related to Converter. Try looking for it, e.g. http://kb.macrium.com/KnowledgebaseArticle50031.aspx



  • 3.  RE: Converter fails on Server 2008 R2 P2P

    Posted Mar 27, 2013 08:52 PM

    I looked at that kb and have gone through resetting and rebuilding both VSS and WMI and still have the same issue. The WMI was not working on either system and System Information could not get any info about the drives or anything else. After resttting and re-registering the components that is working WMI is working. VSS says the it is fine from the command line, but I get the same error in Converter. I am going to try a couple of other things but if it is not working today the dev guys will just have to reinstall in a new VM.



  • 4.  RE: Converter fails on Server 2008 R2 P2P

    Posted Mar 28, 2013 08:56 AM

    Hmm.

    Did you disable UAC on the source machine? And, if Converter is installed on the same machine, did you run the client as administrator?



  • 5.  RE: Converter fails on Server 2008 R2 P2P

    Posted Mar 28, 2013 01:35 PM

    Yes UAC is disabled and I am logged in as the local administrator. I also tried specifically running converter as administrator. I have also shut down a lot of the processes running on this server (SQL,web and custom software) but get the same error.



  • 6.  RE: Converter fails on Server 2008 R2 P2P

    Posted Jun 20, 2013 01:01 AM

    OK, i found a fix for this. What worked for me was to install the Windows Server backup feature in server manager and perform a quick backup. I backed up my entire C: drive to a network share but I guess any type of backup will do. After performing the backup I tried the vmware converter using version 5.1 and it created the image with no errors.

    When I ran 'vssadmin list writers' from an adminstrator level command prompt before installing and running the Windows backup there were six writers that had failed being:

    Writer name: 'System Writer'

       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

       Writer Instance Id: {f93bab18-4b9c-4053-94cf-1d7c96b31e25}

       State: [7] Failed

       Last error: Timed out

    Writer name: 'SqlServerWriter'

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

       Writer Instance Id: {9db2d210-0803-4483-a5d1-c73859a705f2}

       State: [7] Failed

       Last error: Timed out

    Writer name: 'TermServLicensing'

       Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}

       Writer Instance Id: {73c291f1-95c3-4e0b-b76e-95c1b375a99e}

       State: [7] Failed

       Last error: Timed out

    Writer name: 'IIS Config Writer'

       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}

       Writer Instance Id: {4b9b60ae-8713-424c-95a6-62da8e888d2f}

       State: [7] Failed

       Last error: Timed out

    Writer name: 'BITS Writer'

       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

       Writer Instance Id: {e69208bd-f9c8-4888-b591-19f46b618271}

       State: [7] Failed

       Last error: Timed out

    Writer name: 'WMI Writer'

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

       Writer Instance Id: {d710bca6-ea70-4c22-b3a0-ca9d20899397}

       State: [7] Failed

       Last error: Timed out

    After runnign the backup only the BITS writer reported as being failed.

    Hope this helps

    DJ