Hello,
we have got a problem within our View environment using VMWare Administrator 4.6 and ESXi 4.0, Win7 linked clones.
Users log on via fat clients.
We get the following log files in the debug files of the connection servers:
2012-09-11 08:01:25,118 DEBUG <VirtualCenterDriver-e2e5cf3c-fc91-44d9-ad1e-d228681ef8a7> [VirtualCenterDriver] VM Name:Machine001, VM IP:machine001.anydomain.com ,GuestInfo Agent [Error Code:1, Error Text:JMS stopped, Active Broker:- -]
The user gets only the donut of the Windows7-Welcome-Screen at startup. The donut keeps spinning and spinning and the above error gets logged meanwhile. We are able to get the user logged in again by resetting the machine. It seems to be the agent on the client that cannot connect to an active broker.
If the agent can connect to
2012-09-10 09:19:43,558 TRACE <VirtualCenterDriver-e2e5cf3c-fc91-44d9-ad1e-d228681ef8a7> [VirtualCenterDriver] VM Name:Machine001, VM IP:machine001.anydomain.com ,GuestInfo Agent [Error Code:0, Error Text:OK, Active Broker:broker02.anydomain.com broker02.anydomain.com/111.222.333.444]
We have this problem with 2 to 4 users every day.
I fournd out that from the messagebus (c:\Program Files\VMware View\Server\messagebus\log) we get additional errors:
2012-09-12 08:44:33,042 TRACE <propagate-e2e5cf3c-fc91-44d9-ad1e-d228681ef8a7> [PoolInformation] Machine001 (ipHostNumber=Machine001.anydomain.com, ipHostNumberOverride not set) added to zombieVMs
I knew the term "zombieVM" describing a machine that is idle and is only consuming resources from the resource pool. But our machines are in use every day we provide only one spare machine per pool to avoid zombieVMs.
