VMware Communities
talesoff
Contributor
Contributor

installing vmware 6.0 error, somebody help me please.

I always got the message when

install in service starting status

contents of message is like this

\----


error1920. Service VMware Agent Service failed to start.

Verify that you have sufficient privilege to start system services.

\----


I use windows XP professional and

do the reboot and install and

turn off all network device..

but that is no use.

how can I install vmware??

vmware 5.5 work well but, only 6.0 make this error..

0 Kudos
7 Replies
magic-man
Hot Shot
Hot Shot

Do you have administrator access during the install?

0 Kudos
talesoff
Contributor
Contributor

No I didn't do any works during install

0 Kudos
RDPetruska
Leadership
Leadership

??? That didn't answer the question. Are you running the VMware setup while logged in as the Administrator user account?

0 Kudos
KevinG
Immortal
Immortal

Make sure you are installing using the "Local Administrator" account and not a Domain account. This includes not using the Domain Administrator account.

0 Kudos
Thommie
Enthusiast
Enthusiast

Hi, I'm having a similar problem:

Installation of VMWare Tools into a Win XP Home Guest fails with "error 1920" so that vmware service doesn't start.

Environment: vmware workstation 6.0.2 build-59824, host: opensuse linux, guest: win xp home

I already tried the hints mentioned in http://communities.vmware.com/message/214719 (install into e:\ drive instead of c:\... or edit the path manually in the registry). The user HAS admin privileges.

I re-tried this three times now, including reboot of the guest, without success. The files are written onto the virtual disk but the installer fails, as soon a he wants to start the service.

0 Kudos
Thommie
Enthusiast
Enthusiast

Hi,

here are some additional lines from the log, but I don't believe that this clears things up ... ?

-


Mar 02 08:10:49.295: vcpu-0| GuestRpc: Channel 0, registration number 1, guest application toolbox.

Mar 02 08:10:49.295: vcpu-0| DISKUTIL: ide0:1 : toolsVersion = 0

Mar 02 08:10:49.295: vcpu-0| DISKUTIL: ide0:0 : toolsVersion = 0

Mar 02 08:10:49.295: vcpu-0| DISKUTIL: Offline toolsVersion = 0

Mar 02 08:10:49.295: vcpu-0| TOOLS setting the tools version to '1'

Mar 02 08:10:49.295: vcpu-0| DISKLIB-DDB : "toolsVersion" = "1" (was "0")

Mar 02 08:10:49.296: vcpu-0| DISKLIB-DDB : "toolsVersion" = "1" (was "0")

Mar 02 08:10:49.297: vcpu-0| TOOLS autoupgrade protocol version 2

Mar 02 08:10:49.298: vcpu-0| TOOLS ToolsCapabilityGuestTempDirectory received 1 C:\WINDOWS\TEMP

Mar 02 08:10:49.298: vcpu-0| TOOLS setting the tools version to '7240'

Mar 02 08:10:49.298: vcpu-0| DISKLIB-DDB : "toolsVersion" = "7240" (was "1")

Mar 02 08:10:49.298: vcpu-0| DISKLIB-DDB : "toolsVersion" = "7240" (was "1")

Mar 02 08:10:49.298: vcpu-0| VMXVmdbGuest_GetGuestUptime failed. ret = Type mismatch

Mar 02 08:10:49.298: vcpu-0| DISKUTIL: ide0:1 : toolsVersion = 7240

Mar 02 08:10:49.298: vcpu-0| DISKUTIL: ide0:0 : toolsVersion = 7240

Mar 02 08:10:49.298: vcpu-0| TOOLS installed version 7240, available version 7240

Mar 02 08:10:49.298: vcpu-0| TOOLS don't need to be upgraded.

Mar 02 08:11:15.766: vcpu-0| GuestRpc: Channel 1, conflict: guest application toolbox tried to register, but it is still registered on channel 0

-


0 Kudos
4u2b3
Contributor
Contributor

I have same problem in 6.0.3. I tried:

1. roll back to 6.0.2

2. install/repair/modify from control panel and from iso image.

3. recompiled my kernel with and without TSC, different TSC options in global vmware config.

All to no avail - it is still impossible to remove (or reinstall) those VMware tools.

When I try to start services manually (by going in console to Vmware program files folder) it says smth like "PANIC: this program should be run in Virtual Machine".

You know, it is the same game as with permissions - as soon as you enforce them, everything breaks. Now who introduced those checks into services binary? It runs inside Virtual Machine. But it still thinks that it does not? I spent two days on trying to correct this situation, and this is really horrible, I need to to work - I guess I will need to rollback even further back tomorrow - or maybe just give up on virtualization for good

0 Kudos