Could not open the virtual machine

Similar Questions

• Getting error: could not open the Virtual Machine: failed to query the Source for more information

  When I have a virtual machine to export to the FVO on an ESXi 4.0 and then try again to import the FVO on VMware Player or Workstation 7.1, I get the following message:

  «Could not open the Virtual Machine: failed to query the Source for more information.» I can successfully re-import this file OVF in an ESXi server without any problems. Anyone know why this is happening and what can be done to remedy this?

  Thank you

  Christopher

  Hello.

  Try to use ovftool to convert a VMX of the FVO.

  Good luck!

• Could not open the Virtual Machine: get Windows XP line 1: syntax error

  The VMware Fusion team:

  I impatiently force them to leave my MacBook Pro as my virtual machine was frozen... as a result, whenever I try and open my VM, I get this error: http://img.Skitch.com/20100316-bdpjryuqdskw8831i8j56iyqs1.jpg .

  I restart and no improvement.

  Tips, thoughts, suggestions? Thanks a lot for your help.

  I do not have the fainest idea why you're engaging again the truncated .vmx file of origin that you posted first however back a review what I said.  The line at the bottom is the .vmx file that I have attached to my last answer should be used to replace your computer in the Virtual Machine "s as package but the Virtual Machine must be stopped, not suspended and merger closed when you replace the truncated by a good I have attached.»  I can't do it, is more obvious or simple then I already have!

• Could not open the virtual machine after Windows blue screen

  I updated my machine Windows 8, he projected blue, now I can't open my VM that I had open at the time of the blue screen.

  This is the message that I received from VMware Workstation 10 attached.

  Search for files of *.lck in virtual machine directory - delete them all.
  Also delete the directories named *.lck

  Then try again - if it still does not need more details

• Java with Minecraft error "error: could not create the Virtual Machine Java.»

  When I try to open Minecraft SP, it won't let me open and there is a message saying:

  "Error: could not create the Virtual Machine Java.".
  Error: A fatal error has occurred. Program will exit. »
  How can I solve this problem?

  Hello

  What is the operating system installed on your computer?
   
  You can ask your question on the Minecraft forums for assistance. Check out the following link.
  http://www.minecraftforum.NET/viewforum.php?f=1002

• Stage of JavaFX Builder 1.0 error: could not create the Virtual Machine Java.

  Hello
  I have installed JavaFX scene Builder under Windows 7 x 32. The installation process is OK, but when I try to launch the app it crashes and displays an error that says:
  "Error: could not create the Virtual Machine Java.".
  Error: A fatal error has occurred. Program will exit. »
  
  I installed JVM 7u5, JDK 7u5, JavaFX SDK 2.1.1 JavaFX 2.1.1 (Java EE JDK + Glassfish) I would be grateful if someone could tell me if there is something missing. I reinstalled almost all software java several times, but without success.
  
  Kind regards!
  
  Published by: 942925 on June 26, 2012 10:23

  Hello

  This message appears usually when the JVM cannot allocate sufficient memory. It may be the consequence of the stage Builder set - Xmx1024m command line: this is currently followed by default TLD-4515 and will be fixed in the next few weeks.
  For the time being you can give a try on a system with more memory. Moreover, what is your current hardware configuration?
  Concerning

• VMDKMounter gets error "could not open the virtual disk.

  I have two Win7 x 64 virtual machines running fine with VMware Fusion 4.1.2.  I installed VMDKMounter from VMware 3.1.3 and OSXFuse 2.3.9.  I can ride one of the files hard with VMDKMounter very well, but others told "Cannot open the virtual disk" when I try to mount it.

  8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: could not parse the instant string ' / Users/finchr/Documents/VirtualMachines.localized/hoth.univ.dir.wwu.edu.vmwarevm/hoth.univ.dir.wwu.edu.vmx '. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: will not be able to take an informed decision, based on partial information. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: mount the drive read-only instead. 8 June 14:43:27 hoth [0 x 0-0xe50e5].com.vmware.vmdkmounter [2394]: failed to open the disc: disc encoding error (261993021117)

  The virtual machine that VMDKMounter fails to mount was created by VMware vCenter Converter 5.0 of a physical machine.  The virtual machine that works was created in VMware Fusion 4.

  Of course, the hard I really want to ride with VMDKMounter is he who fails.  No idea how to make so that he can get?

  Well, I see nothing in the disc DescriptorFile which prevents the hard mounted.

  So right now, you can mount other hard files, but not this one, then I have two suggestions...

  It would be to use vmware-vdiskmanager to create a new hard that will not go up and the other would create a new empty hard, then add it to a virtual machine, as well as one that will not go up and then start with appropriate optical disk or an ISO Image containing the appropriate tools/utilities in order to image the drive to the new empty.  I usually use Symantec Norton Ghost for operations like this.  Then maybe a new mounts with VMDKMounter.

• Could not enumerate the virtual machines that are used as models

  Hey guys,.

  I have a simple script that collects information from a virtual computer. Unfortunately, I'm getting a lot of mistakes, he doesn't pull out information if the virtual machine is used as a model.

  $date = get-Date-format-M - d - yyyy

  Import-Csv C:\test\servers_mate.csv - UseCulture | %{

  Get-VM-name $_. Name |

  Select Name,

  @{N = 'Center'; E = {Get-Datacenter - VM $_______ |} {{Select - ExpandProperty name}}.

  @{N = "Cluster"; E = {Get-Cluster - VM $_______ |} {{Select - ExpandProperty name}}.

  Host, NumCpu, MemoryGB,

  ProvisionedSpaceGB, Powerstate,

  @{N = "Path"; E = {}

  $current = get-view $_. ExtensionData.Parent

  $path = $_. Name

  {}

  $parent = $current

  if($parent.) Name - only "vm") {$path = $parent. {Name + "\" + $path}

  $current is get-view $current. Parent

  } While ($current. Parent - no $null)

  [channel]: join ('-',($path.)) Split('\') [0.. ($path). Split('\'). (Count-2)]))

  }},

  FolderId,

  @{N = "Manufacturer"; E = {(Get-VMHost-Name $_.)} Host). Manufacturer reference}},

  @{N = ' model'; E = {(Get-VMHost-Name $_.)} Host). Model}},

  @{N = "ProcessorType"; E = {(Get-VMHost-Name $_.)} Host). ProcessorType}}

  } | Export-Csv "C:\test\servers-vcenter-servers-vmpath-$date.csv" - NoTypeInformation - UseCulture

  the output current is like that.

  Name

  Data Center

  Cluster

  Host

  NumCpu

  MemoryGB

  ProvisionedSpaceGB

  PowerState

  Folder path

  FolderId

  Manufacturer

  Model

  ProcessorType

  I just also want to collect the same information, even if the virtual machine is used as a model. Introduction 1 additional column is perhaps something like below. So we can clearly identify if it is a virtual machine or be used as a model? Thank you.

  Name

  Data Center

  Cluster

  Host

  NumCpu

  MemoryGB

  ProvisionedSpaceGB

  PowerState

  Folder path

  FolderId

  Manufacturer

  Model

  Type of processor

  Virtual MACHINE or template

  Erros I receive.

  Get - VM: get-VM VM with name 03/08/2015-12:40:44

  "xxxx" was not using the specified

  filter (s).

  Online: 2 char: 5

  + Get-VM-name $_. Name |

  +     ~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: ObjectNotFound: (:)) [Get - VM], VimException)

  + FullyQualifiedErrorId: Core_OutputHelper_WriteNotFoundError, VMware.VimA

  utomation.ViCore.Cmdlets.Commands.GetVM

  Try something like this

  Import-Csv C:\test\servers_mate.csv - UseCulture | %{

  Notice-EEG - ViewType VirtualMachine-filter @{'Name' = $_.} Name} | %{

  $esx = get-view-Id $_. Runtime.Host

  $_ | Select Name,

  @{N = 'Template'; E={$_. Config.Template}},

  @{N = 'Center'; E = {Get-Datacenter - VM $_.} Name | {{Select - ExpandProperty name}}.

  @{N = "Cluster"; E = {Get-Cluster - VM $_.} Name | {{Select - ExpandProperty name}}.

  @{N = 'Host'; E = {$esx. Name}},

  @{N = "NumCpu"; E={$_. Config.Hardware.NumCpu}},

  @{N = "MemoryGB"; E = {[int]($_.)} Config.Hardware.MemoryMB/1KB)}}.

  @{N = "ProvisionedSpaceGB"; E = {($_.Summary.Storage.Committed+$_.Summary.Storage.Uncommitted)/1 GB)}},

  @{N = "Powerstate"; E={$_. Runtime.PowerState}},

  @{N = "Path"; E = {}

  $current = get-view-Id $_. Parent

  $path = $_. Name

  {}

  $parent = $current

  if($parent.) Name - only "vm") {$path = $parent. {Name + "\" + $path}

  $current is get-view $current. Parent

  } While ($current. Parent - no $null)

  [channel]: join ('-',($path.)) Split('\') [0.. ($path). Split('\'). (Count-2)]))

  }},

  @{N = "FolderId"; E={$_. Parent.ToString ()}}.

  @{N = "Manufacturer"; E = {$esx. Hardware.SystemInfo.Vendor}},

  @{N = ' model'; E = {$esx. Hardware.SystemInfo.Model}},

  @{N = "ProcessorType"; E = {$esx. Hardware.CpuPkg [0]. Description}}

  }

  }

  The error you see seems to indicate that there is an entry in the CSV file for a nonexistent VM.

• Could not start the virtual machine after you use vmkfstools to resize - HELP!

  I thought I knew what I was doing, but apparently not...

  I tried to increase the size of a VM over 36 GB drive and now I can not start the server. Here's the change front of directory list:

  -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

  -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

  -rw - 1 root root 4096 9 February 14:55 PJAEast-DL01-000002 - delta.vmdk

  -rw - 1 root root 277 9 February 14:55 PJAEast-DL01 - 000002.vmdk

  -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

  -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

  -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

  -rw - 1 root root 8684 25 August at 21:03 PJAEast - DL01.nvram

  -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

  -rw - r - r - 1 root root 1042 28 August to 01:52 PJAEast - DL01.vmsd

  -rwxr-xr-x 1 root root 2779 Feb 9 15:10 PJAEast - DL01.vmx

  -rw - r - r - 1 root root 267 Feb 9 15:10 PJAEast - DL01.vmxf

  -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

  -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

  -rw - 1 root root 73728 9 February 14:55 PJAEast-DL01_1-000002 - delta.vmdk

  -rw - 1 root root 283 9 February 14:55 PJAEast-DL01_1 - 000002.vmdk

  -rw - 1 root root 36322836480 28 August at 01:41 PJAEast-DL01_1 - flat hard

  -rw - 1 root root 597 25 August at 15:18 PJAEast - DL01_1.vmdk

  -rw - r - r - 1 root root 78710 25 August at 16:06 vmware - 1.log

  -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

  -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

  -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

  -rw - r - r - 1 root root 69453 9 February 14:54 vmware.log

  Then, I run the command:

  vmkfstools x 256g PJAEast - DL01_1.vmdk

  And now the virtual machine does not start, return an error: "the virtual disk parent has been changed since the child was created."

  The directory listing is now ("BOLD" indicates the change of information post-vmkfstools):

  -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

  -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

  -rw - 1 root root 4096 Feb 9 16:12 PJAEast-DL01-000003 - delta.vmdk

  -rw - 1 root root 277 Feb 9 16:12 PJAEast-DL01 - 000003.vmdk

  -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

  -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

  -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

  -rw - 1 root root 8684 Feb 9 16:12 PJAEast - DL01.nvram

  -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

  -rw - r - r - 1 root root 1015 28 August 01:52 PJAEast - DL01.vmsd

  -rwx - 1 root root 2779 Feb 9 16:12 PJAEast - DL01.vmx

  -rw - 1 root root 267 Feb 9 16:12 PJAEast - DL01.vmxf

  -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

  -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

  -rw - 1 root root 73728 Feb 9 16:12 PJAEast-DL01_1-000003 - delta.vmdk

  -rw - 1 root root 283 Feb 9 16:12 PJAEast-DL01_1 - 000003.vmdk

  -rw - 1 root root 274877906944 28 August 01:41 PJAEast-DL01_1 - flat hard

  -rw - 1 root root 599 9 Feb 16:11 PJAEast - DL01_1.vmdk

  -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

  -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

  -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

  -rw - r - r - 1 root root 69453 9 February 14:54 5.log - vmware

  -rw - r - r - 1 root root 39510 Feb 9 16:12 6.log - vmware

  -rw - r - r - 1 root root 39411 Feb 9 16:12 vmware - 7.log

  -rw - r - r - 1 root root 39410 Feb 9 16:14 vmware.log

  I can't do anything else until I get comments. Can anyone recommend a way to solve this problem?

  I thought I knew what I was doing, but apparently not...

  I agree

  Two a problem with the new drive.

  1. You get the error message comes from the basic disk with a different size than the disks of the snapshot.
  2. With a size of 256 GB, you will not be able to create snapshots of the disk (on ESXi prior to 5.0 with a block size of 1 MB)

  What you can try to do is to edit the file PJAEast - DL01_1.vmdk :

  • 536870912 VMFS 'PJAEast-DL01_1 - flat hard' RW--> RW 70943040 VMFS 'PJAEast-DL01_1 - flat hard. "
  • DDB. Geometry.Cylinders = "33418'-> ddb.geometry.cylinders = '4416.

  After that, I would recommend to clone the virtual disk to a new one, replace the virtual disk in the virtual machine settings and resize it to a maximum of 254GB (see "calculates the time system required by the snapshot files" at http://kb.vmware.com/kb/1012384)

  • vmkfstools-i PJAEast-DL01_1 - 000003.vmdk PJAEast - DL01_1a.vmdk

  André

• Could not start the virtual machine: "the specified file is not a virtual disk.

  Hi, I have a problem from a guest vm-workstation.

  Details below - I've done some reading here for some other "the file specified."

  is

  not a virtual disk' messages and I suspect that I am out of luck

  but I have

  wanted to ask just in case there was something miss me

  Here I tried to gather records / logs that other threads

  mentioned - I

  Welcome to all the tips on the revival of the guest, or a

  pointer to a how-to on recovering the files of a given snapshot.

  Thank you

  John

  Summary:

  VMware workstation: 7.0.1 build 227600

  host of os: Vista sp2, 64-bit

  (16 GB of ram)

  guest operating system: sles10 sp2 64-bit (4 GB ram)

  the virtual machine folder:

  drive eSATA (samsung 320, blacx attachment)

  symptom: guest vm

  does not start: says "the specified file is not a virtual disk.

  history: this particular comments works fine; I've done about 30 shots

  during the last 2 months.  The guest is not a copy - even if she did start life as a full-clone

  another linux-client with or without an operating system installed.  In any case, I've used it to very good

  effect for 2 months now.

  So last night I wanted to power off of the host, while I lived my usual steps:

  (1) stop my os of burst (# shutdown - h now)

  (2) even worksation vmware (file - & gt; exit)

  (3) stop start vista (not "suspend" but the real stop turn off the power).

  (4) visa bluescreened.  Now she is doing this every so often, so I thought that it would be

  a big deal.

  (5) this morning I tried to turn on the virtual machine and I got the 'not a virtual disk' error.

  My best guess at this point is the bluescreen stopped some write cache to be

  flushed to disk.  The funny thing is, after the previous bluescreens 3 or 4, the

  Comments to restart without a hitch.

  shrug In any case, just to be weave, I disabled write Vista for outside cache

  device (set to security policy / deletion in Device Manager).  Seems smarter to

  an external device.

  Spare part

  Attached is a file cant_start.zip (191KO) containing:

  dircontents.txt - directory of the client's file listing
  sles10_sp2. NVRAM
  sles10_sp2.vmsd
  sles10_sp2.vmx
  sles10_sp2.vmxf
  VMware.log - other requests asked for *.log files, so I thought
  VMware - 0.log - I should send him these as well.
  VMware - 1.log
  VMware - 2.log
  \ui-logs - 2 IU-logs from C:\Users\jgreve\AppData\Local\Temp\vmware-jgreve
  \vmdk_files - subdirectory of *.vmdk files, light, & can be useful
  -end-

  I checked the VMDK and newspapers - and the VMDK all look great.

  Last departure also seems to succeed?

  As it seems that instant 36 is not used so far - I was just going to throw it away and try again.

  To do this, you would change the line vmx file

  scsi0:0. FileName = 'suse11.2_x64 - cl1 - 000036.vmdk.

  TO

  scsi0:0. FileName = 'suse11.2_x64 - cl1 - 000035.vmdk.

  and then try to restart the virtual machine. If that works then remove all the

  suse11.2_x64 - cl1 - 000036-* files

  ___________________________________

  VMX-settings- Workstation FAQ -[MOA-liveCD | http://sanbarrow.com/moa241.html]- VM-infirmary

• Impossible to turn on the virtual machine with the following error: could not open the disk ' / path/to/vmdk-0001.vmdk ' or one of the Flash disk it depends on. Reason: Broken pipe.

  After the movement of virtual machines in VmWare Server 2 for ESX 4i, I get this error when you try to start the virtual machine:

  Impossible to turn on the virtual machine with the following error: could not open the disc

  "/ path/to/vmdk-0001.vmdk" or one of the Flash disk it depends on.

  Reason: Broken pipe.

  Anyone's idea what is the problem here?

  How did you move virtual machines?

  Did you use the converter (https://www.vmware.com/tryvmware/?p=converter)

  Otherwise try converter

• In opening the virtual machine: "could not find a peer valid to connect to" or "error of Transport (VMDB) - 32" / "-14" ""»

  Hello

  Since yesterday after a reboot of my host (DELL E6410, W7 SP1 64-bit, 8 GB RAM, 2x750GB SATA3 running WorkStation 9.0.2 Update Windows Update), I can't open my existing VM.

  I often get "can not find a valid peer to connect to" and sometime before: "Transport (VMDB) - 32 error: Pipe: reading is not'or'error of Transport (VMDB)"-14: fitting broke"»

  I worked for 2 years on this machine without a hitch, WS7 reclassification in WS9 without any problem.

  FYI: we have changed the domain 3 months ago, but it has never be a problem.

  I have google and search several Forum. So far, I tried to:

  -restart the service vmware-auth as an administrator

  -launch vmware.exe administrator

  stop/start the vmx86 service

  -uninstall / reboot / install Workstation.  3 times. First using uninstall from the Control Panel, then doing a / clean before installation and finally track down any file/reg entry.

  -HE asked if any group policy changes were made recently (like not allowing to run vmware.exe?)

  -Rename vmware.exe (logs I look similar to what is in this post: http://communities.vmware.com/thread/331099?start=0 & tstart = 0 ... but no luck)
  

  -excluded vmware.exe in my AV (Microsoft ForeFront). Unfortunately, in that I'm not allowed disabled...

  -Open the virtual machine using the drive == > does not work either.

  This isn't a file corrupted in a virtual machine (even backup - 7zipped - don't work on my laptop... but the launch on the other).

  Even a newly created WM (boneless), unbootable! :-(

  *, BUT to BE NOTE *: if a virtual machine is created as a shared virtual machine, I can start the application locally remotely! And this same VM, if started (via the.vmx) does not work using Workstation GUI!

  I have attached 2 newspapers. Work a (vmware.log remotely) and the inactive (vmware-vmx - 4072.log thru WS GUI).

  Of after what I saw (and what little I understand), it's as if the CPU is not detected?

  The two newspapers have this line:

  FeatureCompat: EVC masks:

  but the non-working goes - we with

  Module CPUID initialization failed.

  While working it display information on CPU (hostCPUID name / family / type... etc...)

  Any idea is welcome.

  I'll answer me to my problem!

  A lot of research to this knowledge.

  In summary: don't mess with the processor affinity... or keep it in mind!

  Response to distinguish:

  I installed 6 months ago a small utility named prio (search for "PRI prnwatch"), because it can save the priority of a given process. What I did notice, is that it also save the processor affinity ! What happened: I probably changed the affinity once for a VM running to give greater priority to a 7zip archive process to complete more quickly (setting HT no core to 7zip and one - or 2? - HT core to VM). Everything works until the next reboot, where the CPU detection during * start EVERY * VM has been somewhat "damaged" leading to the wrong log message: failed initialization Module CPUID.

  This is the reason of *my* question. Perhaps it might help someone else?

  TIPS:

  For advanced people who do not want to check the processor affinity of each process in the Task Manager, you can try this Windows Powershell command (remember to launch PowerShell as an administrator):

  Get-Process | Format-Table-PriorityClass name, ProcessorAffinity property

  ProcessorAffinity column gives the number of representation of the authorized core, 1-bit by heart.

  15 = 1111 is all possible core (for a logical processor 4). Mine is 1 CPU with 2 core HT <=>4.

  LSB is the core lowest. So if you allow only core0 and core3 (1001) on a process, the number of ProcessorAffinity will be 9...

  Post edited by: cbiero (LSB and MSB...)

• Power error: could not open the file exists

  This weekend a partition containing my virtual machines VMWare has been accidentally deleted by the Acronis backup software
  I have rebuilt the partition and re-assigned the same drive letter.
  Then I restored the 'Virtual Machines' from my backup folder.
  Now when I run VMPlayer and start my virtual machine I get the following error:

  Power error: could not open the file 'H:\Virtual Machines\Windows\XP Professional\Windoes XP Professional.vmdk': the system cannot find the specified file.

  The directory search I find the file with the name and the correct directory path.
  Some attributes (readonly, hidden, etc.) are on.
  I am logged in as administrator.

  Is there some other files/directories should I have also restored?
  Suggestions?

  "" According to the newspaper files of the virtual machine has a 40 GB virtual disk consisting of 21 files Windows XP Professional - s001.vmdk '-Windows XP Professional - s021.vmdk. However, the screenshot shows only 5 of these files hard! Please check if you can recover the missing files.

  André

• 2% failed: ERROR: could not open the file %s

  I'm trying to convet system winnt in esx, always fail in the setp2. I tired to convet locally and remotely and get the same error message. Help, please

  10:32 step 1: connecting to Agent VMware Converter on 172.19.129.10

  10:32 step 2: creation of target virtual machine and the conversion of the data

  10:32:05 configuring settings for the virtual machine target...

  10:32:07 creating virtual machine target...

  10:33:04 ERROR: could not open the file %s

  The newspaper has been attached

  I already test the TCP 902 on the source by telnet to the target ESX machine and it seems that TCP 902 is open. The result of telnet has also been downloaded.

  Help, please!

  Problems with vConverter.

  StarWind Software R & D

• VMware Converter failed % 2: ERROR: could not open the file %s

  I'm trying to convet system winnt in esx, always fail in the setp2. I tired to convet locally and remotely and get the same error message. Help, please

  10:32 step 1: connecting to Agent VMware Converter on 172.19.129.10

  10:32 step 2: creation of target virtual machine and the conversion of the data

  10:32:05 configuring settings for the virtual machine target...

  10:32:07 creating virtual machine target...

  10:33:04 ERROR: could not open the file %s

  The newspaper has been attached

  This is the result of that port TCP 443 is blocked?

  Nope

  More likely, the system of the source (172.19.129.10) cannot reach the host ESX by DNS or TCP Port 902 is stuck between them.

  HA - nfc: / /------Corcus [storage2] / [email protected]:902

  Kind regards

  EvilOne

  VMware vExpert 2009

  NOTE: If your question or problem has been resolved, please mark this thread as answered and awarded points accordingly.