Critical Error on Windows 2003 Server

[danboh]

Hello all,

I need some assistance from experts. Here's what happened:

On a Windows 2003 Server host, and using Remote Desktop Connection to that server, I installed another Windows 2003 Server image on VirtualBox 3.0.4. Everything went fine and by the time the Windows Login screen appeared on the recently installed Virtual Machine I realized that I had lost connection to the server due to some network issue. When I went to the server I noticed that it had hanged, so I rebooted it. Then, when trying to open the application (VirtualBox) again I started receiving a Critical error (in spanish)

I have tried several things like uninstalling it and installing it again, installing the latests version, rebooting again. I just don't want to format the server and reinstall the OS all over again.

Any ideas??? Any suggestions???

Thanks in advance!

[Perryg]

Maybe you should post the log file for the guest. The indication is that you are out of memory so also post the host memory and what you are setting it to in the guest.
Also the HDD specs and the free space.

[danboh]

Hi Perry,

Thanks a lot for taking the time to help me out with this. Here's the server's specifications:

Total memory installed: 4Gb RAM
Total memory assigned to guest: 512 Mb.
Total HDD available space: 280Gb.
Total HDD assigned to guest: 20Gb.

Im not able to post the Log file since I have already uninstall the application several times so I don't think there's any Log file for the guest.

[Perryg]

There should be a log file. Usually when you uninstall VBox the logs, and the machines are left intact. Look for a folder called virtualbox in a file manager search and then see if there is a folder that says machine. Inside that you should see the machine folder of the guest and in that you should see a folder that says logs. It really would help to see what is in the folder.

Also look at the system logs of the server and see if it indicates anything that would be useful.

[danboh]

Here's the Log file I found http://www.elepos.com.ve/VBox.log

There's nothing logged in the Windows Event Viewer, so I'm not sure what kind of system log you refer to.

Again, thanks.

[Perryg]

The logs show version 3.0.0 so I assume that is the version that you upgraded from. I suspect that the problem now is because of the hang and the fact that you had to power down and has corrupted the install. Try this and see if it helps.

1. Right click on the install program and then left click on run as admin. Select repair. Reboot when complete. (please don't tell me that you are the Admin, just do as suggested)
or
2a If that fails you need to reinstall version 3.0.0 and select repair (or install if repair is not an option). (DO NOT reboot)
2b Run the version 3.0.0 install again and tell it to uninstall (DO NOT reboot)
2c Run the new Version 3.0.6 install and see if it works (This time reboot)

[danboh]

According to your suggestions, this is what I did:
1. Reinstall version 3.0.0 (no option to Repair in version 3.0.6 installer)
2. No repair option when running 3.0.0 installer, so I removed it using the installer.
3. Installed version 3.0.6 and rebooted:
The results were the same, I get the same error when double clicking the VirtualBox Icon.

The I tried running the version 3.0.6 installer again, but this time I selected repair. After a while it asked me to reboot for the changes to take effect and immeditely I received an error saying "MSI Failed"

[Perryg]

The important part is to get version 3.0.0 installed.
then without rebooting you reinstall and tell it to uninstall.
Still not rebooting you then try to install the newer version.

There more than likely is a remanent still left in there that needs to be removed.
You can also use the MS removal tool and see if that helps. http://support.microsoft.com/kb/290301

[danboh]

I understand, but I did exactly what you suggested. I installed version 3.0.0 and still nothing. I will try using Microsoft's application and let you know.

[danboh]

Hello again,

I completely uninstalled any version of VirtualBox, I even checked for any instance of this application installed using Microsoft Removal tool. Then I re-installed version 3.0.0 of VirtualBox and the same error appears! I'm getting a little bit frustrated about this application not running on my server, I'm afraid I will need to use VMWare

[Perryg]

Of course that is your decision, but you still have the Devs you can talk to. Submit a ticket in Bugtracker (link is below my post) and be sure to give this this link along with a description of what you did and have done. You need to setup an account there because it is on a different system though, sorry.

[danboh]

Thanks. I've already opened the ticket if you'd like to check it, the number is 5075.

Best regards,