I have the same trouble on WinServer 2003. Previous Beta was removed clean, with restart. After restart I started new beta (1.0.0-24927) setup but it failed with the same error.
the same here when I install to e:
when installing to c: (an alias made with subst to e:) I get
error 1320 Path is too long
Same problem here. Removed expired beta build 22874, rebooted, received this installation error:
Internal Error 2381. G:\
Environment is Windows 2000 Pro, SP4. The drive mentioned in the error is a volume on a SATA RAID. Previous VMWare Server had been running virtual machines saved on this volume.
I don't know if it is related, but VMWare doesn't like the D: partition on my server at all and seems to be concerned with the user permissions. the user for installation and the vm login itself have full permissions on the D: partition (which I verified by creating a folder, a file, and then deleting both), but VMWare is convinced that is not the case. I tried installing as local Administrator, but the exact same problems occurred.
I somewhat solved the problem by installing ONLY the main server component and having it install to a different partition.
the D: drive is on a SATA RAID, but I had the same problem installing to a different partition on a different SATA drive that is not RAID. I ended up installing the program to C: and moving all of my virtual machines to E: (it still doesn't like D:).
Everything worked fine with prior builds.
The new release (VMware-server-installer-1.0.0-27828.exe) still has the same problem with non C: drives here.
Is an old version without this problem still available somewhere ?
Message was edited by:
I somewhat solved the problem by installing ONLY the
main server component and having it install to a
Good call. It works for me, too, with only the VMWare Server selected, and no other components.
This thread may be a bit old now, but I just received this error installing VMware-server-installer-1.0.1-29996.exe on my WinXP Pro SP2 machine...
I found some threads and a MS article that talked about checking the SYSTEM account had enough permissions on the temp directories, but it was fine (inherited full) BUT I did run the install using my[/u] user account, which is a member of the local administrators group.
Hope this helps