New Version 4.1.18 now rendered all 3 of my VM inaccessible

[vdotmatrix]

http://db.tt/Rjn0unQj

WHY DID I UPGRADE this program while on a working vacation?

The link above is what I am looking at for the next week.

Can someone please tell me there is a simple fix to this condition. That I have to merely point to where the old files are stored and hara kiri won't be necessary.

Thanks in advance.....

I have seen similar post on recent upgrades after my thing happened...I should have looked here but with as PERFECT as this program ran xp-pro and windows-7 in my wildest nightmare would I have ever thought this could happen and at the worst most worst possible time.

SOLUTION: after 48 hours of generous time from people responding to this post we have fixed this problem with NO idea why this happened . But the solution when the machines have a runtime error on opening -102 (file not found), is to remove the machine. then create a new machine but instead use the previous *vdi file located in users>VMs>whatever folder this resides. It will restore the machine but the shared folders may be broken. My windows-7 machine fails to launch but that was the least of my issues. The xp-pro machines fired right up. So , please look at all the screen shots and especially the last 10 or so posts on this thing to get the gist of the problem and decide if the solution is right for you. Thanks to Perry for his patience in helping us!!!

[mpack]

Please pick one VM, describe the symptoms properly, and upload the VM log for a failed session, as a zipped attachment. The log file is "VBox.log" and is found in the "Logs" subfolder of the VM folder.

Incidentally: I do not click unknown links, especially obfuscated ones! So I have no idea what your link was intended to show.

[vdotmatrix]

It is a screen shot of my VIRTUAL MACHINE gui in drop box....with the error code.

http://dl.dropbox.com/u/5501747/VM_upgrade_diaster.tiff

in the meantime I will find this log file.

[vdotmatrix]

I found many vbox files in FINDER and the last one was a zip file please let me know if this is what you would like to see or if I have to try to zip one of the other log files.....


All 3 VB show inaccessible now after the upgrade; the link above is the screen shot with the main screen.

I just woke up hoping for a better day...and this was really just a bad bad dream......


thanks in advance.

v.

[mpack]

I suspect you have not provided the correct log - the one you provided is dated April 3rd, 2012.

My previous message told you where to find the correct log. Incidentally, the log does not come pre-zipped. Zipping is something I asked you to do yourself, prior to uploading file.

[vbox_user1001]

Please consult "Ugh. 4.1.18 GuestAdditions locked me out..."

You're suffering from something very close to what I just was (and fixed). More details on that topic.

[vdotmatrix]

I suspect you have not provided the correct log - the one you provided is dated April 3rd, 2012.

My previous message told you where to find the correct log. Incidentally, the log does not come pre-zipped. Zipping is something I asked you to do yourself, prior to uploading file.

this vbox.log is a relatively tiny file from this morning-"the morning after".

thanks man!

v.

[mpack]

The new log shows the VM being shut down normally, after a user request. No crash. No failure to boot.

[mpack]

Please consult "Ugh. 4.1.18 GuestAdditions locked me out..."
You're suffering from something very close to what I just was (and fixed). More details on that topic.

Since the OP has not installed the v4.1.18 GAs, that seems unlikely.

[vdotmatrix]

Will someone please look at this screen shot and tell me what has happened to my virtual box. It has the error code and whatever is going on.

To reiterate, as I was getting ready to work on a project, I opened VB and a notification window opened telling me about an update; I installed it and everything got broken.

http://dl.dropbox.com/u/5501747/VM_upgrade_diaster.tiff

I do not understand anything you guys are talking about in these cryptic and technical responses. I just need someone to look at this screen shot.....wait I am going to just cut and paste this jazz if you guys are so afraid to click this link ...hold on....it is what I should have done to begin with...

Runtime error opening '/Users/vincedaddy/VirtualBox VMs/windows 7/windows 7.vbox' for reading: -102 (File not found.).
/Users/vbox/tinderbox/4.1-mac-rel/src/VBox/Main/src-server/MachineImpl.cpp[708] (nsresult Machine::registeredInit()).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
VirtualBox
Interface:
IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}


Here is what the top says:
Runtime error opening '/Users/vincedaddy/VirtualBox VMs/XP-PRO box/XP-PRO box.vbox' for reading: -102 (File not found.).
/Users/vbox/tinderbox/4.1-mac-rel/src/VBox/Main/src-server/MachineImpl.cpp[708] (nsresult Machine::registeredInit()).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
VirtualBox
Interface:
IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}

and here is the 3rd VB:

Runtime error opening '/Users/vincedaddy/VirtualBox VMs/GAME BOX/GAME BOX.vbox' for reading: -102 (File not found.).
/Users/vbox/tinderbox/4.1-mac-rel/src/VBox/Main/src-server/MachineImpl.cpp[708] (nsresult Machine::registeredInit()).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
VirtualBox
Interface:
IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}

thanks in advance for helping.



[url]http://dl.dropbox.com/u/5501747/VM_upgr ... r.tiff/url]

[Perryg]

Does the file /Users/vincedaddy/VirtualBox VMs/windows 7/windows 7.vbox exist?
If not does a file /Users/vincedaddy/VirtualBox VMs/windows 7/windows 7.vbox-prev exist?
If the latter does exist then make a backup of it and rename it to remove the -prev and see if the guest boots. If so do this to each machine that is giving you issues.

[vdotmatrix]

Yes..all the files are there!!!!! for each VBOX!!!!

So , by just removing the previous....it 'll automatically see the right file and my life will be on track again? LOL!!!!

I am verifying everything here...before I do any changes in real time...


THANK YOU FOR TAKNG THE TIME TO LOOK!!!!

V.

[Perryg]

Just be sure to backup the -prev file before you rename it.

[vdotmatrix]

Just be sure to backup the -prev file before you rename it.

The file(s) in each VB without the (-prev) exist already as you can see above with the XP-PRO VB.

If I do what you suggest then I will have 2 files with the same name right?

[Perryg]

Back it up somewhere else.