• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2374
  • Last Modified:

Physical-to-virtual conversion fails

I am attempting to perform a physical to virtual conversion.  Source machine is a Windows Server 2003 R2 Standard x64 and the destination is Windows Server 2008 R2.  I am using Virtual Machine Manager to perform the conversion.  
The error on the source:
Event Type:      Error
Event Source:      VSS
Event Category:      None
Event ID:      12289
Date:            3/30/2010
Time:            11:41:07 PM
User:            N/A
Computer:      computername
Description:
Volume Shadow Copy Service error: Unexpected error LookupAccountName( NULL, domain\user, NULL, p, NULL, p, p).  hr = 0x800706fd.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2d 20 43 6f 64 65 3a 20   - Code:
0008: 53 45 43 53 45 43 52 43   SECSECRC
0010: 30 30 30 30 32 30 38 36   00002086
0018: 2d 20 43 61 6c 6c 3a 20   - Call:
0020: 53 45 43 53 45 43 52 43   SECSECRC
0028: 30 30 30 30 32 30 36 39   00002069
0030: 2d 20 50 49 44 3a 20 20   - PID:  
0038: 30 30 30 30 30 38 38 38   00000888
0040: 2d 20 54 49 44 3a 20 20   - TID:  
0048: 30 30 30 30 30 32 31 32   00000212
0050: 2d 20 43 4d 44 3a 20 20   - CMD:  
0058: 43 3a 5c 57 49 4e 44 4f   C:\WINDO
0060: 57 53 5c 53 79 73 74 65   WS\Syste
0068: 6d 33 32 5c 73 76 63 68   m32\svch
0070: 6f 73 74 2e 65 78 65 20   ost.exe
0078: 2d 6b 20 6e 65 74 73 76   -k netsv
0080: 63 73 20 20 20 20 20 20   cs      
0088: 2d 20 55 73 65 72 3a 20   - User:
0090: 4e 54 20 41 55 54 48 4f   NT AUTHO
0098: 52 49 54 59 5c 53 59 53   RITY\SYS
00a0: 54 45 4d 20 20 20 20 20   TEM    
00a8: 2d 20 53 69 64 3a 20 20   - Sid:  
00b0: 53 2d 31 2d 35 2d 31 38   S-1-5-18
00b8: 2d 20 45 72 72 6f 72 3a   - Error:
00c0: 4c 6f 6f 6b 75 70 41 63   LookupAc
00c8: 63 6f 75 6e 74 4e 61 6d   countNam


The error that VMM is giving is:
Error (3110)
VMM is unable to create a snapshot set on excelshare. An unexpected error occurred during the Volume Shadow Copy service operation.
 (Unknown error (0x80042308))

Recommended Action
Try the operation again.
0
exceli
Asked:
exceli
  • 11
  • 6
  • 3
1 Solution
 
merowingerCommented:
which hyper visor do you run?
Virtual Server does not support x64 guests!
0
 
exceliAuthor Commented:
Hyper-V
0
 
merowingerCommented:
ok that should work.

If nothing will help, then use the sysinternals tool disk2vhd, this helped me :)
http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
msmamjiCommented:
Have a look also at this
http://contoso.se/blog/?p=238 

P2V: Converting Physical Computers to Virtual Machines in VMM
http://technet.microsoft.com/en-us/library/cc764232.aspx

Regards,
Shahid
0
 
exceliAuthor Commented:
merowinger, i used the disk2vhd and received a blue screen when i installed the integration disk.
0
 
exceliAuthor Commented:
the blue screen was 0x0000007b
0
 
exceliAuthor Commented:
msmamji, the first link references a different event id and the second link is just an overview.  I have converted many physical to virtual servers.  Before i even start the process i check to make sure all prerequisites are present.
0
 
msmamjiCommented:
I gave you the first link as it referenced DPM failing because of VSS, I thought maybe it can lead you in the right direction. Clearly it didn't.
I have done P2V quite a few times, and have ran into several issue and got them resolved. I have never gotten this error.
Have you tried P2Ving any other server?

Regards,
Shahid
0
 
exceliAuthor Commented:
msmamji, i have p2v'ed many other servers.
0
 
msmamjiCommented:
Do you have the same problem with other P2V operation... or is this happening with p2ving one specific server.
0
 
exceliAuthor Commented:
This is happening with one specific server.
0
 
msmamjiCommented:
Is this the only WS08 R2 server you P2V'ed? I am guessing that this is your first instance P2V'ing a WS08 R2 server?
Are you getting Error 1789 on either the source machine or SCVMM server?
It might help you look into this
http://support.microsoft.com/?kbid=976494

Regards,
Shahid
0
 
exceliAuthor Commented:
Source machine is a Windows Server 2003 R2 Standard x64 and the destination is Windows Server 2008 R2.  I am P2Ving a WS03 R2.  The server running hyper-v is a WS08 R2 server.
0
 
msmamjiCommented:
can you check and see if Volume Shadow Copy Service is running in your Guest VM?
can you run this at command prompt on the guest machine
vssadmin list writers

see If you get any errors?
0
 
exceliAuthor Commented:
VSS is running and i have ran vssadmin list writers and there are no errors.
0
 
exceliAuthor Commented:
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: {4d1605de-9c44-4fad-9cf1-4d1b8fe5c075}
   State: [1] Stable
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {306c8636-b7df-4c25-b380-20a58e5f3d6d}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {c0553546-9833-4a5e-88fe-2058ccbb8afc}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {df0e27bd-112f-42c5-911b-dca249138ab5}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {939905fb-2328-422a-b398-ad94577518c9}
   State: [1] Stable
   Last error: No error

Writer name: 'SPSearch VSS Writer'
   Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
   Writer Instance Id: {1677ff47-888e-4d2b-8217-97b7170b478f}
   State: [1] Stable
   Last error: No error

Writer name: 'OSearch VSS Writer'
   Writer Id: {8d5f38cd-fb7a-49ca-ae1b-21d1f017d8f9}
   Writer Instance Id: {eeb14ff4-96b2-493a-bf01-87e6183d38be}
   State: [1] Stable
   Last error: No error

0
 
msmamjiCommented:
That seems perfect.
Is there anything different about this source machine with other machines that you p2v'ed?
0
 
exceliAuthor Commented:
It's running sharepoint. Other then that its exactly the same.
0
 
exceliAuthor Commented:
I uninstalled the microsoft system center virtual machine manager p2v agent (x64) and ran through the process over again.  This has cleared up the issue above.
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 11
  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now