VMware Tools Service not Working on Secondary Virtual Server

Hi All,
I have Primary Server as Physical and Secondary Server is VM , On Secondary server VMware Tools are Installed but not running I tried to Start the service and I got following error.
The VMware Tools service terminated with the following error:
Incorrect function.
Is this normal behavior that on Secondary server doesn't run VM services , Further i Checked there is registry value for VMware Tools.
Regards
Usman Ghani

Hi
Welcome to communities.
I think this is normal behavior
For more please check log if get any additional clue.

Similar Messages

  • ADSSO Service Not Working on Secondary CAS when done Failover

    We are running NAC OS 4.9.2 in OOB L2 Virtual Gateway...
    We have CAS Cluster
    Primary CAS -- 10.245.220.5  & Secondary CAS -- 10.245.220.6 and Service-IP 10.245.220.4
    When in HA Cluster Primary is Active and Secondary is Standby Ok , ADSSO is Working and Service is started
    We have capture details of same .
    10.245.220.5
    2013-04-18 15:46:21.833 +0530  Thread-70 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - GSSServer - done building kdc list for domain kotakgroup.com
    2013-04-18 15:46:21.833 +0530  Thread-70 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - GSSServer - KDC(s) :[kgp-gor-dc01.kotakgroup.com, kgp-gor-dc02.kotakgroup.com, kgp-gor-dc03.kotakgroup.com, kgp-gor-dc04.kotakgroup.com, kgp-gor-dc05.kotakgroup.com, kgp-dr-dc01.kotakgroup.com, kgp-dr-dc03.kotakgroup.com, kgp-dr-dc02.kotakgroup.com]
    2013-04-18 15:46:21.833 +0530  Thread-70 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - GSSServer - writeKrbFile: writing to file ../conf/krb.txt
    2013-04-18 15:46:21.833 +0530  Thread-70 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - GSSServer - writeKrbFile: wrote to file ../conf/krb.txt
    2013-04-18 15:46:21.834 +0530  Thread-70 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - GSSServer - creating login context ...
    2013-04-18 15:46:21.834 +0530  Thread-70 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - GSSServer - created login context ...javax.security.auth.login.LoginContext@bb3f71
    2013-04-18 15:46:39.207 +0530  Thread-70 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - Notifying GSSServer status Started
    2013-04-18 15:47:07.540 +0530  Timer-3 INFO  com.perfigo.wlan.jmx.adsso.GSSRetrier              - GSSR - Windows SSO is running
    When Primary is rebooted and Secondary becomes Active Ok , ADSSO is not working and Service is not started
    10.245.220.6
    2013-04-18 15:50:42.933 +0530  Timer-3 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - Server starting server ...
    2013-04-18 15:50:42.933 +0530  Timer-3 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - Server is now running ...
    2013-04-18 15:50:42.933 +0530  Thread-68 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - GSSServer - SPN : [casadsso/[email protected]]
    2013-04-18 15:50:42.933 +0530  Thread-68 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - GSSServer - building kdc list for domain kotakgroup.com
    2013-04-18 15:50:42.934 +0530  Thread-68 ERROR com.perfigo.wlan.jmx.adsso.GSSServer               - Unable to start server ... kotakgroup.com.
    2013-04-18 15:50:42.937 +0530  Thread-68 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - Notifying GSSServer status Stopped
    2013-04-18 15:50:42.937 +0530  Thread-68 INFO  com.perfigo.wlan.jmx.adsso.GSSServer               - server is exiting .
    Our Observation is krb.txt is not getting generated when Secondary is Active Ok ...
    Can any one suggest how to fix the issue...

    Hi,
    Can you check and see if dns and ntp are accurate and can you verify your AD environment? What version of domain controllers are in service if there are a mix then other steps like modifying a few files maybe needed.
    Also was the secondary CAS replaced or reimaged recently?
    Thanks,
    Sent from Cisco Technical Support iPad App

  • Vmware-tools does not install in 2.6.22 dont panic arch guest os

    Dear All,
    I get the following error while compiling the vmware tools in guest arch linux 2.6.22-ck dont panic (vmware workstation 5.5.3). Though the output shows the vmhgfs module is able to load but I do not get my shared folder directory in the /mnt/hgfs. What is the work around.
    Stopping VMware Tools services in the virtual machine:
    Guest operating system daemon: done
    Guest filesystem driver: done
    Trying to find a suitable vmhgfs module for your running kernel.
    None of the pre-built vmhgfs modules for VMware Tools is suitable for your
    running kernel. Do you want this program to try to build the vmhgfs module for
    your system (you need to have a C compiler installed on your system)? [yes]
    Using compiler "/usr/bin/gcc". Use environment variable CC to override.
    What is the location of the directory of C header files that match your running
    kernel? [/lib/modules/2.6.22-ck/build/include]
    Extracting the sources of the vmhgfs module.
    Building the vmhgfs module.
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-config0/vmhgfs-only'
    make -C /lib/modules/2.6.22-ck/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-2.6.22-ck'
    CC [M] /tmp/vmware-config0/vmhgfs-only/cpName.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/cpNameLinux.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/dev.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/driver.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/hgfsUtil.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/main.o
    CC [M] /tmp/vmware-config0/vmhgfs-only/staticEscape.o
    LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o
    LD [M] /tmp/vmware-config0/vmhgfs-only/vmhgfs.ko
    make[1]: Leaving directory `/usr/src/linux-2.6.22-ck'
    cp -f vmhgfs.ko ./../vmhgfs.o
    make: Leaving directory `/tmp/vmware-config0/vmhgfs-only'
    The module loads perfectly in the running kernel.
    pcnet32 29828 0
    Unloading pcnet32 module
    Extracting the sources of the vmxnet module.
    Building the vmxnet module.
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-config0/vmxnet-only'
    make -C /lib/modules/2.6.22-ck/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-2.6.22-ck'
    CC [M] /tmp/vmware-config0/vmxnet-only/vmxnet.o
    /tmp/vmware-config0/vmxnet-only/vmxnet.c: In function 'vmxnet_open':
    /tmp/vmware-config0/vmxnet-only/vmxnet.c:674: warning: 'deprecated_irq_flag' is deprecated (declared at include/linux/interrupt.h:66)
    /tmp/vmware-config0/vmxnet-only/vmxnet.c: In function 'vmxnet_netpoll':
    /tmp/vmware-config0/vmxnet-only/vmxnet.c:1058: error: too many arguments to function 'vmxnet_interrupt'
    make[2]: *** [/tmp/vmware-config0/vmxnet-only/vmxnet.o] Error 1
    make[1]: *** [_module_/tmp/vmware-config0/vmxnet-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-2.6.22-ck'
    make: *** [vmxnet.ko] Error 2
    make: Leaving directory `/tmp/vmware-config0/vmxnet-only'
    Unable to build the vmxnet module.
    The fast network device driver (vmxnet module) is used only for our fast
    networking interface. The rest of the software provided by VMware Tools is
    designed to work independently of this feature.
    If you wish to have the fast network driver enabled, you can install the driver
    by running vmware-config-tools.pl again after making sure that gcc, binutils,
    make and the kernel sources for your running kernel are installed on your
    machine. These packages are available on your distribution's installation CD.
    [ Press Enter key to continue ]
    Thanks in advance.
    saa_1973.

    You shouldn't need the kernel sources, just point vmware tools to the right location :
    What is the location of the directory of C header files that match your running
    kernel? [/lib/modules/2.6.22-ck/build/include]
    Replace with usr/src/linux-2.6.22-ck/include/
    If you still get this error /tmp/vmware-config0/vmxnet-only/vmxnet.c:1058: error: too many arguments to function 'vmxnet_interrupt'
    see vmware tools 5.5.3, linux 2.6.19, vmxnet compile fix
    as mentioned at the bottom of the wiki page.

  • Text keeps disappearing when I select it to make type at all / make changes / edit. Type tool is not working. I am running CS6 on a Macbook Pro Retina (which I am hating!) 10.9.4 - wish I'd never upgraded.

    Text keeps disappearing when I select it to make type at all / make changes / edit. Type tool is not working. I am running CS6 on a Macbook Pro Retina (which I am hating!) 10.9.4 - wish I'd never upgraded.
    Photoshop General Discussion

    The RAM needs specs as shown below.
    Maximum Memory
    16 GB (Actual) 8 GB (Apple)
    Memory Slots
    2 - 204-pin PC-10600 (1333 MHz) DDR3 SO-DIMM

  • For Acrobat 9. TouchUp Text tool does not work.

    Acrobat 9. TouchUp text tool does not work --- even on documents created with my computer using installed fonts. Problem 2: when trying to export to Word 2010 there is no option for format .dox, only .doc which belonged to earlier versions of Word.

    Hi Begin,
    I have the same issue, I am not sure which version so I had on my old computer but when I got a new windows 7 64bit, and asked IT to install Adobe, my life turned upside down. now they asked if I need X or 9pro and I though 9pro is the latest and greatest.. they installed the standard first then could not edit then asked for the pro and could not edit ... now I search and maybe version X will edit but if the document is signed and we do need to do lots of editing after the signature then what is the solution??
    I hope the Guru in Adobe can help here soon please :-)!!
    Joseph

  • Lion Server DNS service not working for locally created zones. Caching working fine.

    OS Lion Server DNS service not working for local zones. Was fine under Snow leopard server but Lion server upgrade has severely broken my DNS and web sites. Zones look fine under Server Admin but keep getting "query failed (SERVFAIL) for xxxx at /SourceCache/bind9/bind9-42/bind9/bin/named/query.c:3921" in the logs. BTW - Server Admin cant seem to see the log file either.
    Surely someone actually tested that DNS still worked on Lion?

    I upgraded from Snow Leopard Server to Lion Server on day 01.  I hit the same issue where, after the upgrade, my Lion Server stopped serving names for my private local domain.
    I finally took a few minutes to figure out what was wrong.  After turning on debug logging and looking through the logs, I found my particular issue, now resolved.
    The issue I had was, when the domain initially was setup when I installed Snow Leopard Server, for some reason it created a zone just for the server (in my case, something like zone "s-01.mydomain.priv"), and a separate zone for all the other machines (zone "mydomain.priv", containing all the private IPs for my local domain).  I never messed with it because it worked, but generally I would have put all of them in the same zone.
    My zone "mydomain.priv" had a nameserver and mail exchanger entry for my server, s-01.mydomain.priv.  I could see this in the Server Admin app on the DNS bubble, Zones tab, mydomain.priv selected, and the General Info panel.  This was fine in Snow Leopard.  This was failing the zone load in the updated bind for Lion Server, though.  The issue was that the "mydomain.priv" zone was referencing the s-01.mydomain.priv server, which was not defined in the "mydomain.priv" zone but rather in the "s-01.mydomain.priv" zone.
    My fix:
    1. In Server Admin, add the server to the zone "mydomain.priv".  I put an A record (Add Machine) in the "mydomain.priv" zone for my server named s-01.mydomain.priv.
    2. shut down DNS on the OS X Lion Server (hit the Stop DNS button on Server Admin).
    3. edit /etc/named.conf by hand, removing the specialized zones that contianed just the server.  In this case, it would be the section titled 'zone "s-01.mydomain.priv"' and the section titled 'zone "3.10.1.10.in-addr.arpa"'.  Your in-addr.arpa zone name will change based on whatever your server IP address was.  My internal one happened to have s-01.mydomain.priv mapped to 10.1.10.3.
    4. Once the specialized zones for just the server were removed, I started the DNS up again.  Instead of serving four zones as it had in OS X Snow Leopard Server, it now servers two zones.  And, now, it is resolving my local machines for the mydomain.priv zone.
    YMMV.  I did note that it wasn't totally necessary to do step 3, but I never really understood the need for the specialized domain, and keeping it around would have a copy of data that would just confuse things.
    Hope that helps.  That's been the only hiccup I've noticed updating to OS X Lion Server thus far.

  • "no serializer is registered..." error with a web service not working

    I'm using JDeveloper 10.1.3
    EJB 3.0
    I'm having issues with the web service not working after I create a client for it. The web service works fine up until I generate the proxy on the other side.
    ERROR An error occurred for port: {http://buslogic/}MyWebService1SoapHttpPort: no serializer is registered for (class buslogic.runtime.....
    I saved the file before I added the proxy and the wsdl looks the same between the working one and the non working one. I can not pin point the when the change to the web service is occuring. It seemed to work once all the way up until I had a ADF page trying to retrieve data, another time it failed when the proxy was created.
    I can get the version that I saved to work immediately after the version that does not fails.
    Any help would be greatly appreciated,
    Dan

    I'm using JDeveloper 10.1.3
    EJB 3.0
    I'm having issues with the web service not working after I create a client for it. The web service works fine up until I generate the proxy on the other side.
    ERROR An error occurred for port: {http://buslogic/}MyWebService1SoapHttpPort: no serializer is registered for (class buslogic.runtime.....
    I saved the file before I added the proxy and the wsdl looks the same between the working one and the non working one. I can not pin point the when the change to the web service is occuring. It seemed to work once all the way up until I had a ADF page trying to retrieve data, another time it failed when the proxy was created.
    I can get the version that I saved to work immediately after the version that does not fails.
    Any help would be greatly appreciated,
    Dan

  • When i paint either black or white on layer mask it erases picture pixels also path selection tool does not work

    when I paint either in black or white on layer mask it erases picture pixels also path tool does not work

    I would try resetting your preference file first:  http://www.lightroomforums.net/showthread.php?14226-Resetting-(or-Trashing-)-the-Lightroom -Preferences-file
    Also, install the latest version 4.4.1 would probably be a good idea.

  • [svn] 4226: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

    Revision: 4226<br />Author:   [email protected]<br />Date:     2008-12-03 15:25:17 -0800 (Wed, 03 Dec 2008)<br /><br />Log Message:<br />-----------<br />Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working. <br />QA: Yes<br />Doc: No<br />Checkintests Pass: Yes<br /><br />Details:<br />* Make sure the <reliable/> option is treated as a nested element rather than an attribute of its parent <network> element.<br /><br />Ticket Links:<br />------------<br />    http://bugs.adobe.com/jira/browse/LCDS-517<br /><br />Modified Paths:<br />--------------<br />    blazeds/trunk/modules/core/src/flex/messaging/Destination.java

    Revision: 4226<br />Author:   [email protected]<br />Date:     2008-12-03 15:25:17 -0800 (Wed, 03 Dec 2008)<br /><br />Log Message:<br />-----------<br />Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working. <br />QA: Yes<br />Doc: No<br />Checkintests Pass: Yes<br /><br />Details:<br />* Make sure the <reliable/> option is treated as a nested element rather than an attribute of its parent <network> element.<br /><br />Ticket Links:<br />------------<br />    http://bugs.adobe.com/jira/browse/LCDS-517<br /><br />Modified Paths:<br />--------------<br />    blazeds/trunk/modules/core/src/flex/messaging/Destination.java

  • [svn] 4195: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

    Revision: 4195
    Author: [email protected]
    Date: 2008-11-26 13:08:23 -0800 (Wed, 26 Nov 2008)
    Log Message:
    Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
    QA: Yes
    Doc: No
    Checkintests Pass: Yes
    Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-517
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ServerConfig.as

    Revision: 4195
    Author: [email protected]
    Date: 2008-11-26 13:08:23 -0800 (Wed, 26 Nov 2008)
    Log Message:
    Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
    QA: Yes
    Doc: No
    Checkintests Pass: Yes
    Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-517
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ServerConfig.as

  • [svn] 4193: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

    Revision: 4193
    Author: [email protected]
    Date: 2008-11-26 11:40:05 -0800 (Wed, 26 Nov 2008)
    Log Message:
    Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
    QA: Yes
    Doc: No
    Checkintests Pass: Yes
    Details:
    * Foundational update to include destination config in what we collect for runtime config exchange with new clients for destinations with network/reliable=true (LCDS only).
    * Also typo in comment in AbstractConnectionAwareSession fixed.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-517
    Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/AbstractConnectionAwareSession.java
    blazeds/trunk/modules/core/src/flex/messaging/Destination.java
    blazeds/trunk/modules/core/src/flex/messaging/services/AbstractService.java

    Revision: 4193
    Author: [email protected]
    Date: 2008-11-26 11:40:05 -0800 (Wed, 26 Nov 2008)
    Log Message:
    Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
    QA: Yes
    Doc: No
    Checkintests Pass: Yes
    Details:
    * Foundational update to include destination config in what we collect for runtime config exchange with new clients for destinations with network/reliable=true (LCDS only).
    * Also typo in comment in AbstractConnectionAwareSession fixed.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-517
    Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/AbstractConnectionAwareSession.java
    blazeds/trunk/modules/core/src/flex/messaging/Destination.java
    blazeds/trunk/modules/core/src/flex/messaging/services/AbstractService.java

  • Is their a fix for photoshop elements 11 move tool? Not working with Yosemite OS upgrade.

    Is their a fix for photoshop elements 11 move tool? Not working with Yosemite OS upgrade.

    Hi,
    We sincerely apologize for the problem customers are facing while using a trackpad with Photoshop Elements 11 & 12 on Mac OSX 10.10 (Yosemite).
    We have been actively working with Apple to resolve this problem as quickly as possible. We're hopeful this will get completely resolved in an upcoming update of Yosemite(MAC 10.10).
    In the meanwhile, you have two options to work around this problem:
    1. Option1: Use a mouse instead of the trackpad
    2. Option2: Install a plug-in which should workaround the problem
    Plug-in installation instructions:
    1. Close Photoshop Elements
    2. Download this zip file to a location you can easily find (e.g. your desktop)
    3. Unzip the file, WhiteWindowWorkaround.plugin, and move it to the Plug-In folder:
    • For Elements 12 – //Applications/Adobe Photoshop Elements 12/Support Files/Plug-Ins/
    • For Elements 11 - //Applications/Adobe Photoshop Elements 11/Support Files/Plug-Ins/
    You can verify the plug-in is installed by launching the Photoshop Elements Editor and choosing Help > System Info... Scroll to the bottom of the text in the dialog and look for the plug-in name "WhiteWindowWorkaround.plugin".
    Note: This plugin is a temporary workaround and should be used until this issue is addressed in Mac OSX 10.10 (Yosemite). Please remove this plugin once the issue is officially resolved by Apple.
    If you are using a stylus in conjunction with a trackpad, you might see issues with your trackpad. Workaround in this particular case is to use mouse instead of the trackpad.
    Hope this helps!
    Regards,
    vaishali

  • I have a comment.  I am very upset with Photoshop and all your tutorials regarding the quick select tool.  I have watched many tutorials and read instructions until I am blue in the face.  This tool does not work.  It is all over the place and all of your

    I have a comment.  I am very upset with Photoshop and all your tutorials regarding the quick select tool.  I have watched many tutorials and read instructions until I am blue in the face.  This tool does not work.  It is all over the place and all of your tutorials make it look so simple.  How can you advertise this as a viable tool when it just doesn't work?

    It is all over the place and all of your tutorials make it look so simple.
    This is a user to user Forum, so you are not really addressing Adobe here, even though some Adobe employees thankfully have been dropping by.
    How can you advertise this as a viable tool when it just doesn't work?
    Concluding something does not work because you fail at using it is not necessarily always justified.
    The Quick Selection Tool certainly has limitations, but your post seems to be more about venting than trouble-shooting – otherwise you might have posted an image where you failed to get an expected result.

  • People anyone know because the logo in title tool is not working?

    people
    anyone know
    because the logo in title tool is not working?

    A little more information, please:
    Version of PPro?
    Operating system?
    Exactly what are you doing and what happens?
    A screen shot would be helpful.

  • Brush Tool is not working with Layer Mask

    Working with Windows platform, using Photoshop CS4, Brush Tool is not working with Layer Mask, how can I resolve this challenge?

    Also, do you have any Selections active - maybe hidden?
    When you have your Layer Mask's Channel active, do your Colors change to black and white?
    Good luck,
    Hunt

Maybe you are looking for