Converter 5.0 fails at first step while converting

[SANPS]

Hallo, i'm trying to convert physical W2K8 ENT 64bit to virtual server, but I had An error occurred during the coversion: "Unknown exceptions". I'm using VMware vCenter Converter Standalone server 5.0.0 installed on the same server as VMware vCenter Server 5.0.0. I have two clustered hosts, one is ESXi 5.0.0, another ESX 4.1.0, but I think that the problem exist not in the hosts. Maybe somebody have any idea how to solve this my problem?

[POCEH]

Please upload log bundle of failed task for check,

[SANPS]

This is log bundle. Thanks for looking at my issue.

[POCEH]

Seems that your problem is bitmapdriver: Unexpected Exception: converter.fault.BitmapDriverStartFault ...

Check the driver with command "sc query bmdrvr" in command prompt with administrator rights.

Also try to start driver with "sc start bmdrvr"

The bitmapdriver is capable to helkp with synchronization task in P2V, try conversion without syncronization, if it doable for you. Otherwise you must find why the driver can not start - look at EventLogger.

[SANPS]

I have checked that bmdrvr state is stopped, I started bmdrvr and now state is running, but converter finished it's task without syncronization  with the same error. I cheked EventLogg and found that after running converter task it's show this error:

Event Type:    Error
Event Source:    crypt32
Event Category:    None
Event ID:    8
Date:        3/8/2012
Time:        8:05:56 PM
User:        N/A
Computer:    VCENTER
Description:
Failed auto update retrieval of third-party root list sequence number from: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt> with error: The specified server cannot perform the requested operation.

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

Any ideas?

[POCEH]

I don't know if this relate to your problem or not... Could you select in UI the failed task and rertieve and upload log bundle again? Is bitmapdriver still running after fail?

[SANPS]

bmdrvr state is RUNNING and here are new log bundle, thanks for looking.

[UmeshAhuja · Accepted solution]

Hi,

Request you to check 4 points

1) Cross check wether NetBIOS over TCP/IP is enable in your physical server.

2) Windows Installer , Windows module Installer and WMI Performance adapter and Virtual disk services are running.

3) Windows firewall service is stop

4) All the below mention ports are open in firewall.

Source	Destination	TCP  Ports	UDP  Ports	Notes
Converter  server	Source  computer	445, 139, 9089  or 9090	137,  138	If  the source computer  uses NetBIOS, port 445 is not required. If NetBIOS  is not being used, ports 137,  138, and 139 are not required. If in  doubt, make sure that none of the ports are  blocked. Port 9089 is  used for Converter Standalone versions, and 9090 is used for the Converter  plugin. Note:  Unless you  have installed Converter server to the source computer, the  account used for  authentication to the source computer must have a  password, the source computer  must have network file sharing enabled,  and it cannot be using Simple File  Sharing.
Converter  server	VirtualCenter	443		Only required if the  conversion target is VirtualCenter.
Converter  client	Converter  server	443		Only required if a custom  installation was performed and the Converter server and client portions are on  different computers.
Source  computer	ESX	443,  902		If the conversion target  is VirtualCenter then only port 902 is required.

[POCEH]

Please upload agent's log. I see in worker log but not in ZIP ("C:\WINDOWS\TEMP\vmware-temp\vmware-SYSTEM\agentTask-task-14-rufaazap.zip")

Also check the ports and connectivity between machine and ESX.

[SANPS]

Thanks a lot. My problem was that source target cannot connect to ESX via port 902. After enabling this port everything worked good. Thanks once more.

[gpouser]

I was trying to sync windows 2003 x64 to ESX 5.5 - napp-it in one storage, this failed. VMware Modified Clusters Tracking Driver test with "sc query bmdrvr" produced driver disabled or not in service.

I noticed on another server with windows 2003 x64 that worked on sync there was a reg key relating to bmdrvr to pointing to the  following location SysWOW64\drivers\bmdvr.sys, I exported the key and import to the server that was not working with sync, after that reboot to load registry and it still failed, but showed up on query, I removed two items from the key.

I removed "security" - "Enum" from the bmdrvr reg key and then tried to start, it worked. Why vConverter did not install this key on installing vConverter Stand alone on the Windows 2003 x64 does not make sense when it worked on the other system.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bmdrvr]

"Type"=dword:00000001

"Start"=dword:00000000

"ErrorControl"=dword:00000001

"ImagePath"=hex(2):53,00,79,00,73,00,57,00,4f,00,57,00,36,00,34,00,5c,00,64,00,\

  72,00,69,00,76,00,65,00,72,00,73,00,5c,00,62,00,6d,00,64,00,72,00,76,00,72,\

  00,2e,00,73,00,79,00,73,00,00,00

"DisplayName"="Modified Clusters Tracking Driver"

"WOW64"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bmdrvr\Enum]

"0"="Root\\LEGACY_BMDRVR\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001

First Export

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bmdrvr]
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,57,00,4f,00,57,00,36,00,34,00,5c,00,64,00,\
  72,00,69,00,76,00,65,00,72,00,73,00,5c,00,62,00,6d,00,64,00,72,00,76,00,72,\
  00,2e,00,73,00,79,00,73,00,00,00
"DisplayName"="Modified Clusters Tracking Driver"
"WOW64"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bmdrvr\Security]
"Security"=hex:01,00,14,80,b8,00,00,00,c4,00,00,00,14,00,00,00,30,00,00,00,02,\
  00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
  00,00,02,00,88,00,06,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,\
  05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\
  20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,04,00,00,00,00,\
  00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,06,00,00,00,00,00,14,00,00,01,\
  00,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,00,18,00,fd,01,02,00,01,02,00,\
  00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,00,00,00,00,00,05,12,00,00,00,\
  01,01,00,00,00,00,00,05,12,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bmdrvr\Enum]
"0"="Root\\LEGACY_BMDRVR\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

[POCEH]

It's not property of installer - these subkeys are created from Windows.

You can re-create bmdrvr with sc command, this will fix them I hope.

[gpouser]

You are right on this, but as I exported the reg key from another server they fail to allow bmdrvr to start, if you see the image at the bottom of this post you can see they are recreated or at lease the sub key "enum", if you have more insight on how to recreate these sub keys with the sc command for bmdrvr can you please advice.

Thanks.

[POCEH]

You can execute the following commands in administrative command prompt:

sc delete bmdrvr

sc create bmdrvr binPath= SysWOW64\drivers\bmdrvr.sys type= kernel DisplayName= "Modified Clusters Tracking Driver"

This must be enough for Windows to recreate all required subkeys.

HTH

[gpouser]

After the event, but I think this was all that was needed to get the bmdrvr working, thanks for this feedback. Will test it out on a spare VM clone