Recompose the vmware view 4.6 error "error:-customization operation timed out."

Similar Questions

• Get error 118 (net::ERR_CONNECTION_TIMED_OUT): the operation timed out when opening applications on Facebook

  I need help for my this error error 118 (net::ERR_CONNECTION_TIMED_OUT): the operation timed out

  It's my app from facebook

  Hi Muhammadarif,

  1. the problem occurs only in facebook?
  2. what web browser do you use?

  This is a known error in Google chrome. If you are using Google chrome then I suggest you post in the forums of Google chrome.
  http://productforums.Google.com/d/Forum/chrome

  If the problem only occurs in facebook, then I suggest you to contact facebook support.
  http://www.Facebook.com/help/

  Hope this information is helpful and let us know if you need more assistance. We will be happy to help.

• How can I see more events in the VMware View 4 Administrator?

  Hello

  in the events section of the VMware View 4 Administrator, I see that all the events of the day.

  Where can I search for events two or three days ago?

  Kind regards

  André

  On the events tab it is that a message contains the field.  If you hit the drop down it will allow you to specify how many days to go back.

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

• Game get unresponsive, a communication error has occurred: Operation Timed out

  A communication error has occurred: "Operation timed out".

  The Web server may be down, too busy or other problems preventing him from answering. You can try again at a later date.

  For assistance, contact your network support team. That's what I get when I try to access a game I play. Worked fine when I stopped last night, but all day was like that, everything is fine.

  Hello

  ·          Game in which you try to read?

  ·          You play this game online?

  I would say also, please contact game support to check their end technical issues.

• vSphere high availability 'Élection' fails at 99% 'operation timed out' to 1 of the 2 hosts

  Hello

  We had a system with 1 host ESXi 5.1 with local disks.

  Now, we install redundancy by adding a 5.5 U2 ESXi host and a device of vCenter 5.5.

  After having installed and any addition to vcenter, we went the ESXi 5.1 to 5.5 U2 ESXi. The SAN works correctly (vMotion works on the own NETWORK card).

  Now, if I try to activate the high availability, both servers will install the HA Agent and start "Election".

  All the warehouses of data (4) on the SAN are chosen for the HA heartbeat, response of isolation is "keep it turned on" by default.

  A server will always be this process done, and the other will keep "elect" until it reaches 100% and errors on the operation "election timed out.

  I've seen this problem on both servers, so I think that the 'master' elected does not have the problem, only the "slave".

  I have checked these items and executed, but not worked:

  VMware KB: Reconfiguration HA (FDM) on a cluster fails with the error: operation timed out

  -The services were running

  VMware KB: Configuration HA in VMware vCenter Server 5.x does not work, error: Operation Timed out

  -All the MTU has been set at 1500

  VMware KB: VMware High Availability Configuration fails with the error: unable to complete the configuration of the ag of HA...

  -the default gateway is not the same on the two hosts, but I fixed that. There is no itinerary changes. HA the setting is "leave power." After correction and deactivation/reactivation HA, the problem is always the same.

  VMware KB: Check and reinstall the correct version of the VMware vCenter Server agents

  -J' ran "Reinstall ESX host management agents and HA on ESXi" agent of HA, and I checked that it was uninstalled and reinstalled during the reactivation of HA.

  CP /opt/vmware/uninstallers/VMware-fdm-uninstall.sh/tmp
  chmod + x /tmp/VMware-fdm-uninstall.sh
  /tmp/vmware-FDM-uninstall.sh

  I did this for two guests. This fix makes the problem of the election and I was still able to run a HA test successfully, but when after this test, I turned off the 2nd Server (in order to test the PA in the other direction), HA has no failover to 1 and everything remained low. After pressing 'reconfigure HA', the problem of the election appeared again on 1 hosts.

  Here are a few extractions of newspapers:

  -L' availability vSphere HA of that host State became election info 29/11/2014 22:03 192.27.224.138

  -vSphere HA agent is healthy info 29/11/2014 22:02:56 192.27.224.138

  -L' availability vSphere HA of that host State became Master info 29/11/2014 22:02:56 192.27.224.138

  -L' availability vSphere HA of that host State became election info 29/11/2014 22:01:26 192.27.224.138

  -vSphere HA agent is healthy info 29/11/2014 22:01:22 192.27.224.138

  -L' availability vSphere HA of that host State became Master info 29/11/2014 22:01:22 192.27.224.138

  -L' availability vSphere HA of that host State became election info 29/11/2014 22:03:02 192.27.224.139

  -Message "host vSphere HA State" on 192.27.224.139 changes from green to red info 29/11/2014 22:02:58 192.27.224.139

  officer of HA - vSphere for this host has an error: vSphere HA agent may not be properly installed or configured WARNING 29/11/2014 22:02:58 192.27.224.139

  -L' availability vSphere HA of that host State became info error of initialization of 29/11/2014 22:02:58 192.27.224.139

  -L' availability vSphere HA of that host State became election info 29/11/2014 22:00:52 192.27.224.139

  -DSMD3400DG2VD2 data store is selected for the storage heartbeat controlled by the HA agent vSphere on this info host 29/11/2014 22:00:49 192.27.224.139

  -DSMD3400DG2VD1 data store is selected for the storage heartbeat controlled by the HA agent vSphere on this info host 29/11/2014 22:00:49 192.27.224.139

  -Firewall configuration has changed. 'Enable' to rule the fdm value successful.  29/11/2014 info 22:00:45 192.27.224.139

  -L' availability vSphere HA of that host State became not initialized info 29/11/2014 22:00:40 reconfigures vSphere HA 192.27.224.139 root host

  -vSphere HA agent on this host is disabled info 29/11/2014 22:00:40 reconfigures vSphere HA 192.27.224.139 root

  -Reconfigure HA vSphere host 192.27.224.139 operation has timed out.     root of HOSTSERVER01 29/11/2014 22:00:31 29/11/2014 22:00:31 29/11/2014 22:02:51

  -Configuration of vSphere HA 192.27.224.139 operation has timed out.     System HOSTSERVER01 29/11/2014 21:56:42 29/11/2014 21:56:42 29/11/2014 21:58:55

  Can someone give me please with help here?

  Or the extra things that I can check or provide?

  I'm currenty running options.

  Best regards

  Joris

  P.S. I had problems with cold Migration during the implementation of the SAN. After setting up all (vMotion, ESX upgrade), these problems have disappeared.

  When you search for this error, I came to this article: KB VMware: VMware vCenter Server displays the error message: unable to connect to the host

  And this cause could make sense, since the server vCenter changed and IP addressing has been changed during the implementation.

  However, in the file vpxa.cfg, the < hostip > and < serverip > is correct (verified by using https://< hostip > / home).

  Tried this again today, no problem at all.
  

  P.P.S. I have set up several of these systems from scratch in the past without problem (if it is an 'upgrade').

  OK, so the problem is solved.

  I contacted Dell Pro Support (OEM offering the license) and they checked the logs (fdm.log) and found that the default IP gateway could not be reached.

  The default gateway is the ip address by default host isolation, used by HA.

  Because it is an isolated production system, the front door provided proved only for future purposes.

  Now, I've changed the default gateway address of management on the switch plugged into both hosts, namely the ping requests.

  This solved any problem.

• The event viewer displays continuously errors with ID 7000 and 7009

  I use Acronis Disk Monitor, which shows the disk health 82% due to a bad block on disk. Observer events poster continually errors on ID 7000 and 7009, but I can't find a solution to these errors or what they mean exactly.

  11/14/2010 08:31 am, Catkin333 wrote:

  I use Acronis Disk Monitor, which shows 82% because of the bad health disk
  block on the disk. Event Viewer displays continuously errors on ID 7000 and
  7009, but I can't find a solution to these errors or that they
  mean exactly.

  If Acronis reports bad blocks on the disk, then you should replace the disk as soon as possible.  Blocks of bad sectors/bad is not repairable, and once they begin to appear that they tend to behave like a snowball rolling downhill, you will get several of them with increasing speed.  You may lose your data if you keep using this drive.

  Regarding the events 7009 & 7000, you will need to copy & paste the events here for give us to you more information.  Double-click on the event to see its properties, and then click the icon of the Clipboard (which looks like 2 pages of paper) to copy the event, you can then paste it in your next post.  These Service Controller errors may be caused by a multitude of different things.

  John

• Installation of the VMware Tools 2.02 - error 2229

  2.02 installation went well.

  Started WIN XP SP3, tried to update the VMware Tools.

  Installation stopped with the error "internal error 2229 - Service Install - SELECT"Name""... etc. "."

  Several reboots and reboots - still the same error...

  Any ideas anyone?

  Thank you!

  Try to uninstall VMware Tools via firstly, control panel and after uninstall and reboot then install VMware Tools in the Virtual Machine menu.

• personalization operation timed out VMware View 4.5

  I'm quite new to Vmware view and this is my first time setting up, please bare with me.

  I get the above error when trying to automatically create a related pool.

  I also spent review the previous post that says abot ensuring that:

  • DHCP is enable on the master image
  • VMware view agent is installed
  • VMware tools is installed
  • The firewall is disabled

  The new virtual machines are created and when I connect to Vsphere is to see that they connect to the field, receive IP from the DHCP server. But I don't see their name in my DNS.

  I hope to have provided enough information and you will appreciate any help.

  To the first just nslookup query, and check whether or not the host of clones name is resolved. Also select al virtual machines to see the Administrator page and perform a reset and see<--  if="" both="" these="" actions="" resolve="" your="" issue="" then="" it="" was="" due="" to="" a="" minor="" network="" outage="" happened="" during="" the="" provisioning="">

  Otherwise,.

  1. If the DNS server is a server active directory integrated one or not? If this is not the case, check the permission to register for this DNS server.

  2. the question of whether the DNS entry received from the DHCP server to clone is directed to the right DNS server? and same DNS / domain name cannot be resolved vcenter server?

  3. have you used Sysprep customization? If Yes, be aware that the domain setting is not levied custom specification but DNS settings will be taken from custom spec. In this case the definition given in the spec custom DNS should resolve the field added in vcenter configuration Admin display page

• Horizon of VMware View Client cryptic error

  Anyone know what this error of the latest version of VMware Horizon View Client trying to say?

  

  My initial guess was she trying to say that the user has not right to the office pool. However, I know for sure that the user has the right. It seems to happen so far only for that user. I googled the error but nothing came.

  Any comments or advice, help reduce our troubleshooting.

  TIA!

  Something has changed in the configuration if the shortcut is no longer valid.

  What happens if you delete the connection parameters and the re - enter?

  Linjo

• Installation of the VMWare Tools (XP/Mac) error

  Hello

  I had problems with the von VMWare Tools installation. Whenever I try to install it, I get the response attached to this email. I use the most recent Mac OS X and Windows (SP3) as well. Windows is the virtual machine.

  Any ideas?

  Thank you

  In the "Major known issues" section (near the bottom of the document) frequently asked Questions about VMware Fusion , take a look at «Fusion 2.0.2»

  In short you need to download the latest Version: 2.0.2 | 2009/02/11 | Build: 147997

• Error: "connection attempt timed out, please check the connectivity of the internet" when trying to connect to Cisco AnyConnect 2.5 on Windows 7 x 64 computer with modem usb wireless HSIA.

  Original title: issue with Cisco AnyConnect 2.5 on win 7 x 64 when connecting to the internet using wireless HSIA usb modem.

  I have win 7 x 64 enterprize edition on my laptop.

  I have problems with Cisco anyconnect VPN client. When I'm on my corporate network it works fine.

  But when I connect to internet using HSIA modem usb wireless home form, client AnyConnect VPN will not connect. The error I get is "connection attempt has expired, please check internet connectivity.

  Please help me to solve this problem as soon as possible.

  Hi Manish,

  The question you posted would be better suited in the TechNet Forums. I would recommend posting your query in the TechNet forums for assistance.

  I also recommend that you contact the VPN support to help:

  https://supportforums.Cisco.com/community/NetPro/security/VPN

• Display users, every day a customer 19:00 error: secure connection timed out (the session has expired, please login again.)

  Hello

  Every day at 19:00 that our employees are disconnected from their virtual desktops, I know that it is because the connection has expired.

  My question is about this delay, the default session out of time (in minutes) is 600. Users log on the connection of the view at 09:00 and they will lunch at 13:30 and return to 15:00.

  600 minutes is the value of minutes between 09:00 and 19:00.

  But time out of session in the VDM global configuration settings is the session limit of when a user opens a session on the server to connect to when the session ends due to INACTIVITY?

  Users are still working at 19:00, so there is no inactivity.

  Why they were disconnected?

  Jorpavon wrote:

  But time out of session in the VDM global configuration settings is the session limit of when a user opens a session on the server to connect to when the session ends due to INACTIVITY?

  No, it isn't. It is the length of the maximum session regardless of the activity, and is necessary to avoid thin clients that never disconnect flooding the broker with the sessions. There is no setting "off". You will simply have to increase it the maximum time that a user will be connected.

• How the VMware View client to its audio? PCoIP or UDP?

  Audio sent by stream UDP separated or is it hardcoded PCoIP?

  Just curious. In fact, I didn't get audio on the client for the iPad.

  It is at the same time.  PCoIP works on UDP and audio is in the stream of PCoIP.

  Larry B.

• VMware View 5.1.1 Security Server LDAP errors

  Im having a serious amount of errors on my VMware View (5.1.1) security server

  Log debugging shows a large amount of LDAP errors, see below.

  2012-09 - 06T 10: 46:49.075 + 02:00 ERROR (0610-0940) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 11: 01:50.102 + 02:00 ERROR (0610-0CB8) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 11: 16:50.109 + 02:00 ERROR (0610-0FE8) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 11: 31:51.120 + 02:00 ERROR (0610-0DD8) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 11: 46:51.132 + 02:00 ERROR (0610-0244) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 12: 01:52.159 + 02:00 ERROR (0610-0F3C) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 12: 16:52.155 + 02:00 ERROR (0610-0E5C) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 12: 31:53.182 + 02:00 ERROR (0610-0F68) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 12: 46:53.194 + 02:00 ERROR (0610-092 C) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 13: 01:54.217 + 02:00 ERROR (0610-08E4) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 13: 16:54.227 + 02:00 ERROR (0610-0504) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE

  Anyone got any suggestions?

  Hello

  The plugin ws_admin trying to make field checks every 15 minutes, but given that your security server is not on the field these checks fail. It is completely harmless, but they should not run in first place, I raised this in their own country.

  Mike

  Edit:

  There is a simple solution for this in 5.1.x:

  Under the current registry key HKLM\Software\VMware, Inc. \VMware VDM\plugins\wsnm\admin, create a new key named Params, and under that a new DWORD value named InitiateDomainChecks with 0 data. Once set, you will need to restart the VMware View Security Server service for the change to take effect.

• VMWare View Agent on the Terminal Server

  We are trying to install the Agent on a Server Terminal server view, and the view Agent service crashes. I looked in the VDM newspapers and see the following information.

  Anyone know why the view Agent cannot load jar files?

  17:42:13, INFO 337 < Service main Thread > [wsnm_desktop] DesktopManager Queue Server installed
  17:42:13, 337 INFO < MessageFrameWorkDispatch > [wsnm_desktop] Session CONNECTED after reboot wsnm: id = 0, KCDOM01\lbeardall, the client user = SPI-LBEARDALL
  17:42:13, INFO 337 < logloaded > [MessageFrameWork] "ws_filesystem - component of VMware View filesystem plugin" Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:42:13, INFO 337 < logloaded > [MessageFrameWork] Plugin 'wsnm_jmsbridge - VMware View framework JMS Bridge Controller' loaded, version = 4.6.0 build-366101, buildtype = output
  17:42:13, 353 INFO < logloaded > [MessageFrameWork] "ws_perfmon - VMware View Performance Monitor and counter shop" Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:42:13, 353 INFO < logloaded > [MessageFrameWork] Plugin "ws_thinappmgmt - support for VMware View infrastructure Application Management" loaded, version = 4.6.0 build-366101, buildtype = output
  17:42:13, 353 INFO < Service main Thread > [wsnm] start the VMware View System Service
  17:42:13, 509 INFO < 7008 > [MessageFrameWork] 'wsnm_jms - VMware View framework JMS bridge' program began, version = 4.6.0 build-366101, pid = 7096, buildtype = release, usethread = 1, closeafterwrite = 0
  17:42:13, 541 INFO < main Thread > [] classpath option:-Djava.class.path=C:\Program VMware View\Agent\lib\; C:\Program View\Agent\lib\\agentjms.jar VMware; C:\Program View\Agent\lib\\concurrent-1.3.4.jar VMware; C:\Program View\Agent\lib\\events-client.jar VMware; C:\Program View\Agent\lib\\events-common.jar VMware; C:\Program View\Agent\lib\\gnu-crypto-2.0.1-1.jar VMware; C:\Program View\Agent\lib\\jdom-1.0.jar VMware; C:\Program View\Agent\lib\\jms-7.6.3.jar VMware; C:\Program View\Agent\lib\\log4j-1.2.14.jar VMware; C:\Program View\Agent\lib\\messagesecurity.jar VMware; C:\Program View\Agent\lib\\orchestratorj.jar VMware; C:\Program View\Agent\lib\\securitymanager.jar VMware; C:\Program View\Agent\lib\\sessionclientapi.jar VMware; C:\Program View\Agent\lib\\swiftmq-7.6.3.jar VMware; C:\Program View\Agent\lib\\winauth.jar VMware; C:\Program View\Agent\lib\\ws_appender.jar VMware; C:\Program View\Agent\lib\\ws_properties.jar VMware; C:\Program View\Agent\lib\\xercesImpl-2.9.1.jar VMware;
  17:42:13, 541 INFO < logloaded > [MessageFrameWork] 'ws_javaview - VMware View Framework Java Diagnostics' Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:42:13, 541 WARN] < main Thread > error occurred during initialization of VM
  17:42:13, 650 INFO < JavaBridge > [wsnm_jmsbridge] wsnm_jms is dead, restart in one minute
  17:43:13, 724 < 5732 > INFO [MessageFrameWork] program 'wsnm_jms - VMware View framework JMS bridge' started, version = 4.6.0 build-366101, pid = 5952, buildtype = release, usethread = 1, closeafterwrite = 0
  17:43:13, 755 INFO < main Thread > [] classpath option:-Djava.class.path=C:\Program VMware View\Agent\lib\; C:\Program View\Agent\lib\\agentjms.jar VMware; C:\Program View\Agent\lib\\concurrent-1.3.4.jar VMware; C:\Program View\Agent\lib\\events-client.jar VMware; C:\Program View\Agent\lib\\events-common.jar VMware; C:\Program View\Agent\lib\\gnu-crypto-2.0.1-1.jar VMware; C:\Program View\Agent\lib\\jdom-1.0.jar VMware; C:\Program View\Agent\lib\\jms-7.6.3.jar VMware; C:\Program View\Agent\lib\\log4j-1.2.14.jar VMware; C:\Program View\Agent\lib\\messagesecurity.jar VMware; C:\Program View\Agent\lib\\orchestratorj.jar VMware; C:\Program View\Agent\lib\\securitymanager.jar VMware; C:\Program View\Agent\lib\\sessionclientapi.jar VMware; C:\Program View\Agent\lib\\swiftmq-7.6.3.jar VMware; C:\Program View\Agent\lib\\winauth.jar VMware; C:\Program View\Agent\lib\\ws_appender.jar VMware; C:\Program View\Agent\lib\\ws_properties.jar VMware; C:\Program View\Agent\lib\\xercesImpl-2.9.1.jar VMware;
  17:43:13, 771 INFO < logloaded > [MessageFrameWork] 'ws_javaview - VMware View Framework Java Diagnostics' Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:43:13, 771 WARN] < main Thread > error occurred during initialization of VM
  17:43:13, 880 INFO < JavaBridge > [wsnm_jmsbridge] wsnm_jms is dead, restart in one minute
  17:44:14, 064 < 3228 > INFO [MessageFrameWork] program 'wsnm_jms - VMware View framework JMS bridge' started, version = 4.6.0 build-366101, pid = 3160, buildtype = release, usethread = 1, closeafterwrite = 0
  17:44:14, 095 INFO < main Thread > [] classpath option:-Djava.class.path=C:\Program VMware View\Agent\lib\; C:\Program View\Agent\lib\\agentjms.jar VMware; C:\Program View\Agent\lib\\concurrent-1.3.4.jar VMware; C:\Program View\Agent\lib\\events-client.jar VMware; C:\Program View\Agent\lib\\events-common.jar VMware; C:\Program View\Agent\lib\\gnu-crypto-2.0.1-1.jar VMware; C:\Program View\Agent\lib\\jdom-1.0.jar VMware; C:\Program View\Agent\lib\\jms-7.6.3.jar VMware; C:\Program View\Agent\lib\\log4j-1.2.14.jar VMware; C:\Program View\Agent\lib\\messagesecurity.jar VMware; C:\Program View\Agent\lib\\orchestratorj.jar VMware; C:\Program View\Agent\lib\\securitymanager.jar VMware; C:\Program View\Agent\lib\\sessionclientapi.jar VMware; C:\Program View\Agent\lib\\swiftmq-7.6.3.jar VMware; C:\Program View\Agent\lib\\winauth.jar VMware; C:\Program View\Agent\lib\\ws_appender.jar VMware; C:\Program View\Agent\lib\\ws_properties.jar VMware; C:\Program View\Agent\lib\\xercesImpl-2.9.1.jar VMware;
  17:44:14, 095 INFO < logloaded > [MessageFrameWork] 'ws_javaview - VMware View Framework Java Diagnostics' Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:44:14, 095 WARN] < main Thread > error occurred during initialization of VM
  17:44:14, 204 INFO < JavaBridge > [wsnm_jmsbridge] wsnm_jms is dead, restart in one minute
  17:45:14, 388 INFO < 1292 > [MessageFrameWork] 'wsnm_jms - VMware View framework JMS bridge' program began, version = 4.6.0 build-366101, pid = 1288, buildtype = release, usethread = 1, closeafterwrite = 0
  17:45:14, 419 INFO < main Thread > [] classpath option:-Djava.class.path=C:\Program VMware View\Agent\lib\; C:\Program View\Agent\lib\\agentjms.jar VMware; C:\Program View\Agent\lib\\concurrent-1.3.4.jar VMware; C:\Program View\Agent\lib\\events-client.jar VMware; C:\Program View\Agent\lib\\events-common.jar VMware; C:\Program View\Agent\lib\\gnu-crypto-2.0.1-1.jar VMware; C:\Program View\Agent\lib\\jdom-1.0.jar VMware; C:\Program View\Agent\lib\\jms-7.6.3.jar VMware; C:\Program View\Agent\lib\\log4j-1.2.14.jar VMware; C:\Program View\Agent\lib\\messagesecurity.jar VMware; C:\Program View\Agent\lib\\orchestratorj.jar VMware; C:\Program View\Agent\lib\\securitymanager.jar VMware; C:\Program View\Agent\lib\\sessionclientapi.jar VMware; C:\Program View\Agent\lib\\swiftmq-7.6.3.jar VMware; C:\Program View\Agent\lib\\winauth.jar VMware; C:\Program View\Agent\lib\\ws_appender.jar VMware; C:\Program View\Agent\lib\\ws_properties.jar VMware; C:\Program View\Agent\lib\\xercesImpl-2.9.1.jar VMware;
  17:45:14, 419 INFO < logloaded > [MessageFrameWork] 'ws_javaview - VMware View Framework Java Diagnostics' Plugin loaded, version = 4.6.0 build-366101, buildtype = output
  17:45:14, 419 WARN] < main Thread > error occurred during initialization of VM
  17:45:14, 528 INFO < JavaBridge > [wsnm_jmsbridge] wsnm_jms is dead, restart in one minute

  Looks like the Sun JVM, the portion of the agent running JMS integration crashes at startup. It's just a guess, but I've seen a similar case with another client where they were running XP virtual machines with large amounts of RAM and some third-party software that was loading DLLs in the middle of the address space of the process. The JVM tries to get a contiguous area of memory, it may be falling on this sequel to a similar problem. On large memory systems, the default behavior of the JVM seizes more than necessary (although it is normally not a problem), try to set the following in the registry to avoid this:

  [Manager\JVM of \VMware VDM\Node of HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc..]

  JVMOptions = - XX: + ForceTimeHighResolution-Xmx64m

  Note that I added only option - Xmx64m to the existing setting.