[SOLVED] Runtime error opening. -102 (File not found)

[Izabelcka]

My host is Win7 Pro 64bit.

My virtual account is WinXP 32bit. All of a sudden, my virtual windows does not boot. Here is the message I get:

Runtime error opening 'C:\Users\X\VirtualBox VMs\WinXP\WinXP.xml' for reading: -102 (File not found.).
D:\tinderbox\win-4.1\src\VBox\Main\src-server\MachineImpl.cpp[708] (Machine::registeredInit).
Result Code:
E_FAIL (0x80004005)
Component:
VirtualBox
Interface:
IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}

I need help asap. Thanks in advance.

[mpack]

Lots of likely/possible explanations for this. Can't tell without some basic info:

Does the file mentioned (C:\Users\X\VirtualBox VMs\WinXP\WinXP.xml) actually exist?
If not, then does the folder mentioned (C:\Users\X\VirtualBox VMs\WinXP) exist at least?
If yes to the latter, what is in that folder?


Your file naming seems peculiar btw. Your VM is located in "VirtualBox VMs", implying a VM created by v4 or later. However the settings file has the ".xml" extension instead of ".vbox", implying v3 or earlier VM. Have you been doing some manual tinkering perhaps?

[Izabelcka]

No manual tinkering. Once there was the error, I did an update of VirtualBox. But I still got no luck.

[Perryg]

Does the file mentioned (C:\Users\X\VirtualBox VMs\WinXP\WinXP.xml) actually exist?
If not, then does the folder mentioned (C:\Users\X\VirtualBox VMs\WinXP) exist at least?
If yes to the latter, what is in that folder?

You didn't answer the questions mpack asked.

[Izabelcka]

Does the file mentioned (C:\Users\X\VirtualBox VMs\WinXP\WinXP.xml) actually exist?

- Yes it exists.

If yes to the latter, what is in that folder?

- These are the files in the folder:
WinXP (Type: VirtualBox Machine Definition)
WinXP (Type: Virtual Disk Image)
WinXP.xml
WinXP.xml-prev
WinXP.xml-tmp

[mpack]

Please post a screenshot of an "Explorer" view of that folder. Make sure that Explorer is configured to show the address bar.

I also suggest that you go into Explorer | Tools | Folder options, select the "View" tab, and uncheck the "Hide extensions for known file types" item, since it is both dangerous and confusing.

[Izabelcka]

Here is the requested screen shot.

[mpack]

I see that you have both a .xml and a .vbox file in the same folder. VirtualBox doesn't do that: this has definitely had manual tinkering. I await the full story with interest.

[Izabelcka]

When the problem started, the employee working on that station told me they did not do anything. I have a feeling perhaps they tried something.

I looked up the issue myself, then tried this before posting my issue on the forum:
viewtopic.php?f=6&t=33196

[Izabelcka]

And I updated the program afterwards, to the latest version.

[Perryg]

Have you taken any snapshots for this guest? Please say no.

[Izabelcka]

No I did not take any snapshots for this guest.

[Perryg]

Since you do not have snapshots you can actually create the guest again and attach the *.vdi file when asked if you want to create a new HDD or use an existing one.

Here is how I do it:

• Write down all of the guest settings, including the MAC address, backup the original *.vdi file before you do anything else.
  Then select to remove the guest (and NOT delete) the the guests file.
  Shut down VBox and wait 20 seconds and start the main manager again.
  Now create the guest as if it were new. Use the same name as before would be advisable and set the guest settings to what you wrote down.
  When asked to create a new HDD or use an existing one just select the *.vdi file and see if it works.

From what I see though you really should tell Windows to show the file extensions or you could have problems telling what is what.
One last thing, I would backup all of the *.vbox & *.xml files then remove them from the folder, but not the *.vdi, before you start to build again.

[Izabelcka]

Ok. Will try now and keep you posted on the outcome.

Thanks.

[Izabelcka]

The REMOVE is the option with a red x. Isnt that delete?