smartnut007
Contributor
Contributor

exception thrown when starting virtual machine

Jump to solution

I had to switch between 6.0.1 and 6.0.0 because i am having troubles with VIX API.

The virtual machine i had created using 6.0.0 seemed to be working fine all along in either version.

but now , the virtual machine is throwing an exception when i try to start it using the workstation ( the one i am using is VMware-workstation-6.0.1-55017.exe )

any help please ?

I have attached the automatically created support information zip file thru the workstation.

                                              • The vmx file is ********************** config.version = "8"

virtualHW.version = "6"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

memsize = "996"

MemAllowAutoScaleDown = "FALSE"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Windows Server 2003 Enterprise x64 Edition-cl1.vmdk"

ide1:0.present = "TRUE"

ide1:0.fileName = "auto detect"

ide1:0.deviceType = "cdrom-raw"

floppy0.fileName = "A:"

ethernet0.present = "TRUE"

ethernet0.virtualDev = "e1000"

usb.present = "TRUE"

displayName = "Clone of Windows Server 2003 Enterprise x64 Edition"

guestOS = "winnetenterprise-64"

nvram = "Clone of Windows Server 2003 Enterprise x64 Edition.nvram"

scsi0:0.redo = ""

ethernet0.addressType = "generated"

uuid.location = "56 4d 19 d1 3f ee d4 93-43 5f 4e ce dd ad 31 3c"

uuid.bios = ""

ide1:0.autodetect = "TRUE"

ethernet0.generatedAddress = "00:0c:29:ad:31:3c"

ethernet0.generatedAddressOffset = "0"

tools.remindInstall = "FALSE"

workingDir = ""

ide1:0.startConnected = "TRUE"

sharedFolder.maxNum = "2"

sharedFolder0.present = "TRUE"

sharedFolder0.enabled = "TRUE"

sharedFolder0.readAccess = "TRUE"

sharedFolder0.writeAccess = "TRUE"

sharedFolder0.hostPath = "
tsclient\D\"

sharedFolder0.guestName = "local-CD(Arun)"

sharedFolder0.expiration = "never"

tools.syncTime = "FALSE"

extendedConfigFile = "Clone of Windows Server 2003 Enterprise x64 Edition.vmxf"

msg.autoAnswer = TRUE

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "manual"

isolation.tools.hgfs.disable = "FALSE"

sharedFolder.option = "alwaysEnabled"

sharedFolder1.present = "TRUE"

sharedFolder1.enabled = "TRUE"

sharedFolder1.readAccess = "TRUE"

sharedFolder1.writeAccess = "TRUE"

sharedFolder1.hostPath = "C:\LWMT_4_3"

sharedFolder1.guestName = "LWMT_4_3"

sharedFolder1.expiration = "never"

checkpoint.vmState = ""

pciBridge0.present = "TRUE"

ehci.present = "TRUE"

svga.autodetect = "TRUE"

inVMTeam = "FALSE"

*******************************************************************

0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal

Disconnect the floppy device.

Something on your system has set a flag in Windows to tell it to generate error dialogs when programmatically trying to access the floppy drive.

Try following these instructions:

http://support.microsoft.com/default.aspx?scid=kb;en-us;281345

View solution in original post

0 Kudos
5 Replies
admin
Immortal
Immortal

Disconnect the floppy device.

Something on your system has set a flag in Windows to tell it to generate error dialogs when programmatically trying to access the floppy drive.

Try following these instructions:

http://support.microsoft.com/default.aspx?scid=kb;en-us;281345

View solution in original post

0 Kudos
smartnut007
Contributor
Contributor

super , editing the registry was easier and it worked.

thanks

0 Kudos
Juul
Contributor
Contributor

Hi,

Had the same problem with Workstation 5.5.5

Same remedy here: changing the value

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\ErrorMode Value in the registry to 2 iso 0.

Thanks a lot for pointing this one out!

Best rgds,

--Juul

Best rgds, --Juul
0 Kudos
dpro
Contributor
Contributor

This worked for me as well. VMWare Workstation 6.5.

XP Pro 64-bit host and Vista 64-bit guest. I would receive the message when starting the guest and the guest OS would not see the DVD drive. I changed the registry and now everything is working.

Thanks.

0 Kudos
clikycraky
Contributor
Contributor

just ran into this issue and the registry fix solved the issue. i had been working with vmware workstation 6.5.2 every day for the past few weeks and out of the blue this exception started to show up. running a repair on the vmware workstation installation didn't help but the registry change did the trick. hopefully this doesn't cause any "side effects" as MS mentions in the PRB article.

0 Kudos