Hello.  We have 2 ESX 4.0 U2 hosts that are now obsolete, but still powered up.  The license used on them was downgraded from ESXi 5 Enterprise to ESX 4.0 Enterprise.  We need to upgrade that license..... back

to 5.0.  We see how to do that through My VMware License Keys.  Do the old hosts need to be powered down first before we do the license upgrade and remove the licenses from them ?  Would removing the hosts from

inventory remove the association of the ESX 4.0 key so that we can upgrade it to 5.0 and apply to the newer hosts we just built ?  Thanks in advance.

Hi,

When I try to delete the snapshot of the replication virtual machine, I have the next error message: "Error vim.fault.GenericVMConfigFault"

And i can't do anything.

Thanks.

Hi,  currently i'm doing house keeping on VC and i believe there is some VM which did't not in use or ADD to inventory.

this vm i believe still keep in some datastore without using, is the anyway to find out all VM which not in use on VC? (not added to inventory)

Hi , i facing issue where meet some vm which with unknow(inaccessible) .

I'm plan to remove it but i cant edit the virtual machine due to grey out on setting.

i only can use ssh to display vmid but cant find the location, looking for help is any commend or way to find out where does these vm located on datastore.

Getting an error when unregistering a PSC.

Our environment has 4 sites running Linked-Mode.  Each site has 3 guests.... 1 vCenter, 1 PSC and 1 SQL.  Sites 2, 3 and 4 partner back to the PSC at site 1.  We are shutting down site 2.

I'm following VMware KB 210736.  I stopped the PSC service at site 2, then  on that PSC ran cmsso-util to unregister the vCenter, which was successful.  Then I went to the PSC at site 4 and ran cmsso-util to unregister the PSC at site 2, but received an error.  A bit confusing..... displays error 1, but then shows Success.

Below is the cmsso-util output.  I believe I need to run vdcleavefed -h -u -w to force a rip-out of the machine account, but need someone to verify if that is correct.  If it is, where do I run vdcleavefed ?  From the PSC at site 4 or on the PSC at site 2 (the one being removed) ?  Thanks in advance for any help.

D:\Program Files\VMware\vCenter Server\bin>cmsso-util unregister --node-pnid km-

001-psc01.minoltana.minolta.com --username administrator@vsphere.local --passwd

Admin01$

D:\Program Files\VMware\vCenter Server\python-modules\identity\vmkeystore.py:4:

RuntimeWarning: to-Python converter for struct client already registered; second

conversion method ignored.

  import identity.vmafd as vmafd

D:\Program Files\VMware\vCenter Server\python-modules\identity\vmkeystore.py:4:

RuntimeWarning: to-Python converter for class vmafd_exception already registered

; second conversion method ignored.

  import identity.vmafd as vmafd

WARNING! This step is irreversible!

Are you sure you want to unregister host km-001-psc01.minoltana.minolta.com ? (Y

or N) Y

2018-01-31T21:51:05.712Z   Running command: ['D:\\Program Files\\VMware\\vCenter

Server\\vmafdd\\dir-cli.exe', 'service', 'list', '--login', 'administrator@vsph

ere.local']

2018-01-31T21:51:06.012Z   Done running command

2018-01-31T21:51:06.848Z   RC = 1

Stdout = vdcleavefd offline for server km-001-psc01.minoltana.minolta.com

Leave federation cleanup failed. Error[1] - Operations error

Stderr = password:

ERROR unregistering computer account.

Success

Guys, I am having an issue with another task is already in process, i am not able to stop, reset, sutdown and move the systems.

there are many KB articles on this issues but nothing is working out any idea??

Thanks

Yoonus

Hi All,

Soon I've got to add more RAM to our 3 ESXI hosts, however I've never had to shut down these at once before, does anyone have a good source for an order of operation to performing such maintenance.

Many thanks!

Sorry for the newbie question, but I'm performing an update to our VSCA from u1 to u3. Are there any precautions I need to take prior to installing the update, such as shutting down VM's, putting hosts in maintenance mode, etc.? Or can I just run the upgrade while everything else is running?

Thanks in advance,

Chris

Hello.

vCenter and external PSC 6.0U3 - both on Windows 2012R2. 7464194 version.

Using latest release VCSA 6.5 7515524 I successfully migrated Windows PSC 6.0 to VCSA PSC 6.5.

Then I tried migrating the vCenter portion and encountered this problem:

"Error occurred while stopping source vpxd service: Service cannot be stopped. Error: INFO:root:Service: vpxd, Action: stop

2018-02-07T08:09:55.511Z ERROR stopping service: vpxd, Exception: (1051, 'ControlService', '\xca\xee\xec\xe0\xed\xe4\xe0 "

After this I tried stopping vpxd via "service-control --stop vpxd" with the same result. "service-control --stop --all" works fine.

As I understand, migration tries to stop service and then probably shutdown the server, but just can't and thus fails. Is there any solution to this?

I tried on my production vCenter server to stop this service but it obviously couldn't since all other dependent services are running giving me the same error.

Hello community,

I'm testing the ability of vCenter server 6.5 to export/import ovf templates.

As requirements, I want to keep the same BIOS UUID and MAC address of nics when I export/import a VM.

In the export form, I tick the checkbox for exporting UUID and MAC address. When I inspect the exported ovf file, I only see the UUID and MAC are not exported. When I import the OVF (after having deleted the VM), a new bios UUID is used (UUID in OVF file is ignored?) and MAC address are regenerated (obvious since not present in OVF file). So have I misunderstood those concepts or is it a bug?

Thanks for help

From the perspective of availability, I am trying to obtain best practice guidance on running VCSA / PSC on VVOL's or should it be avoided and placed on a traditional LUN?  The VASA is not a VM but embedded into the storage (EMC Unity).

Thanks!

Hi all

I have a problem with EAM.  We have been using NSX guest introspection and it started playing up recently, which attracted our attention.

In vSphere Web Client, under Administration\vSphere ESX Agent Manager \ Solution I get the following error:

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x7fdc140fea00] _serverNamespace = /eam _isRedirect = false _port = 15005)

On VCSA, the VMware-eam service is not running.  Starting it results in an error, the details of which are found in /var/log/VMware-eam/wrapper.log

STATUS | wrapper  | 2017/09/06 15:45:55 | --> Wrapper Started as Daemon

STATUS | wrapper  | 2017/09/06 15:45:55 | Java Service Wrapper Professional Edition 64-bit 3.5.24

STATUS | wrapper  | 2017/09/06 15:45:55 |   Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.

STATUS | wrapper  | 2017/09/06 15:45:55 |     http://wrapper.tanukisoftware.com

STATUS | wrapper  | 2017/09/06 15:45:55 |   Licensed to VMware Global, Inc. for VMware vCenter ESX Agent Manager

STATUS | wrapper  | 2017/09/06 15:45:55 |

INFO   | wrapper  | 2017/09/06 15:45:55 | Event Command 'wrapper_start': Command line[0] : /usr/sbin/cloudvm-ram-size

INFO   | wrapper  | 2017/09/06 15:45:55 | Event Command 'wrapper_start': Command line[1] : -J

INFO   | wrapper  | 2017/09/06 15:45:55 | Event Command 'wrapper_start': Command line[2] : vmware-eam

INFO   | wrapper  | 2017/09/06 15:45:55 | Event Command 'wrapper_start': Command line[3] : -O

INFO   | wrapper  | 2017/09/06 15:45:55 | Event Command 'wrapper_start': Command line[4] : /etc/vmware/java/vmware-eam_jvm.conf

INFO   | wrapper  | 2017/09/06 15:45:55 | Event Command 'wrapper_start': Command launched (pid: 23310), blocking for up to 3600 seconds...

INFO   | wrapper  | 2017/09/06 15:45:56 | Event Command 'wrapper_start': Command completed with exit code: 0

INFO   | wrapper  | 2017/09/06 15:45:56 | Event Command 'wrapper_start': Command completed with exit code: 0  Continuing.

INFO   | wrapper  | 2017/09/06 15:45:56 | Event Command 'jvm_prelaunch': Command line[0] : /opt/vmware/bin/python

INFO   | wrapper  | 2017/09/06 15:45:56 | Event Command 'jvm_prelaunch': Command line[1] : ../wrapper/bin/update_pnid.py

INFO   | wrapper  | 2017/09/06 15:45:56 | Event Command 'jvm_prelaunch': Command line[2] :

INFO   | wrapper  | 2017/09/06 15:45:56 | Event Command 'jvm_prelaunch': Command line[3] :

INFO   | wrapper  | 2017/09/06 15:45:56 | Event Command 'jvm_prelaunch': Command line[4] :

INFO   | wrapper  | 2017/09/06 15:45:56 | Event Command 'jvm_prelaunch': Command launched (pid: 23313), blocking for up to 15 seconds...

INFO   | wrapper  | 2017/09/06 15:45:56 | Event Command 'jvm_prelaunch': Command completed with exit code: 1

INFO   | wrapper  | 2017/09/06 15:45:56 | Event Command 'jvm_prelaunch': Command completed with exit code: 1  Continuing.

STATUS | wrapper  | 2017/09/06 15:45:56 | Launching a JVM...

INFO   | jvm 1    | 2017/09/06 15:45:56 | Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M

INFO   | jvm 1    | 2017/09/06 15:45:56 | WrapperManager: Initializing...

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp:

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error: Encountered an error running main:

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error: org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'esxAgentMgr' defined in class path re                                   source [eam-server-beans.xml]: Could not resolve placeholder 'eam.hostd_restart_timeout'

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.processProperties(PropertyPlaceholderConfigurer.java:268                                   )

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:75)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:                                   554)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:                                   528)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:363)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:83)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at com.vmware.eam.util.Main.main(Main.java:50)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at java.lang.reflect.Method.invoke(Unknown Source)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:290)

INFO   | jvm 1    | 2017/09/06 15:45:57 | WrapperSimpleApp Error:       at java.lang.Thread.run(Unknown Source)

STATUS | wrapper  | 2017/09/06 15:45:59 | <-- Wrapper Stopped

So following my nose, a potentially relevant snip from the aforementioned eam-server-beans.xml found in /usr/lib/VMware-eam/conf is:

<!-- ESX Agent Manager beans -->

   <bean id="esxAgentMgr"

         class="com.vmware.eam.EsxAgentManagerImpl"

         lazy-init="false"

         depends-on="springContext,

                  vcInventory,

                  vcListener,

                  httpNfcLeaseTimeoutHandler,

                  nameManager,

                  vcDatastoreManager,

                  vcEventManager,

                  vcKeyValueStore,

                  l10n">

      <constructor-arg ref="adapterServer" />

      <constructor-arg value="${vc.proxy.host}" />

      <constructor-arg value="${vc.proxy.port}" />

      <constructor-arg value="${vc.tunnelSdkUri}" />

      <constructor-arg ref="clientAuthenticator" />

      <constructor-arg value="${eam.clear_db_on_startup}" />

      <constructor-arg value="${eam.support_linked_clone}" />

      <constructor-arg value="${eam.debug_ref_count}" />

      <constructor-arg value="${vum.integration}" />

      <constructor-arg value="${Net.DVFilterBindIpAddress}" />

      <constructor-arg value="${Net.TrafficFilterIpAddress}" />

      <constructor-arg value="${Net.DVFilterVswifIpAddress}" />

      <constructor-arg ref="commonMapStore" />

      <constructor-arg ref="vpxdConnection" />

      <constructor-arg ref="vumConnection" />

      <constructor-arg ref="nameManager" />

      <constructor-arg ref="vibPackageDepots" />

     <property name="hostdRestartTimeout" value="${eam.hostd_restart_timeout}" />

   </bean>

I'm struggling as I need to get my NSX piece back up and running (ironically so I can gracefully remove it), but believe I need the EAM to be working properly first.

Any ideas before I open a ticket?

Thanks.

vDave

Hi everyone,

I'm running VCSA 6.5.0.14000 Build Number 7515524 with ESXi 6.0.0 Update 3 (Build 5050593) hypervisors - is there any downside, any incompatibilities that one should be aware of?

On the surface all seems to run just fine, the product intself functions but I was wondering if there was any unwritten (or written and I missed it) rule somewhere to match the major release of one's hypervisor with the major release of the vCenter?

Thanks~B

I've got ESXi running on a server, so I'm trying to clean up some rack space.  I have an old XP installation that I have to keep around for an old application we still support.  So I need to get this running XP installation converted to a VM so the program can still be enhanced and compiled, etc.

But, I can never get past 1%.  I keep running into:

FAILED: Unable to create a VSS snapshot of the source volume(s). Error code:  2147754776 (0x80042318).

Now, I HAVE determined that in the event viewer I do see issues with the VSS system:

Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers.  Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.

And, I also see some COM+ errors as well:

The COM+ Event System failed to fire the RequestWriterInfo method on subscription {F865A9A1-1E43-4688-8742-18E82CAFAFE6}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}.  The subscriber returned HRESULT C0000005.

But, it seems that all of the links to Microsoft on how to fix this are now defunct.  I've found a number of things including some registry edits, stop some services and re-registering a bunch of dlls, and more... but nothing has worked.  And I can't do too much to this system, because it is a living environment with all of the right drivers and configurations to build the product.

So... looking for anyone who has had the same issue.  Or, is there another process that can be used to get this physical installation into a VM?  I've spent the last few days trying just about everything I can think of to make this work and keep ending up back in the same spot.

Anyone got some words of help and/or wisdom?

Rich

P.S. - Attached are the diagnostics from the most recent run, if anyone wants to peruse them.  Also, running the latest Converter Standalone 6.2.0 build-7348398

Hello,

I am having a problem when trying to deploy an OVA file. The message "Transfer failed: The OVF descriptor is not available" is displayed. Any suggestions? Much appreciated.

Hi,

Want to forward all logs to the Log Insight appliance, have logged in to the appliance and added the vcenter authentication (tested ok).

However the Log Insight platform (Evaluation License) remain like this, is there anything I can check to make sure vcenter is forwarding the logs?

Hi ,

i want to migrate windows vcenter server 6.0 to vcsa 6.0 , its failed because its not supported yet to migrate vcenter 6.0 to vcsa 6.0 . is that true?

if i migrate to vcsa 6.5 , then i can use existing licence in appliance or not?

Thanks

I'm wondering if anyone has run into this scenario.

A PSC (PSC1) was deployed and a vCenter (vCenter1) was connected to it but had issues and got deleted etc.

A new vCenter was stood up and also named vCenter1 and was connected to PSC1

Upon logging into the web client, there is a warning message stating "Could not connect to one or more vCenter Server Systems: https://vCenter1.domain.local/sdk"

Now, there are documented measures to remove a vCenter from a PSC, Using the cmsso command to unregister vCenter Server from Single Sign-On (2106736) | VMware KB

but those instructions seem to conclude that you can use the vCenter server name as the ID:

cmsso-util unregister --hostId host_Id --node-pnid vCenter_Server_System_Name --username administrator@your_domain_name --passwd vCenter_Single_Sign_On_password

Question being this, if I were to run this with vCenter1 as the vCenter_Server_System_Name won't it remove both the orphaned vCenter as well as the existing working vCenter?

Does anyone have a better way to remove just the orphaned vCenter?

Hi all,

I hope you can assist me with an issue I'm having.

I have uploaded a script to my vCenter Server(VCSA 6.0) that I want to run when an alarm triggers. I have no problem running the script from the vCenter terminal - it works. However when I run the script from the alarm I get an error message in the events log i vSphere Client:

"Host did not complete a script: A general system error occurred: Failed to run script: Failed to invoke command: Stream is not initialized".

The script is located in /bin and the command I'm adding to the alarm is /root/bin/script.sh

If I add /script.sh or /bin/script.sh to the alarm the error message is the same.

Note: if I add #!/bin/bash to the top of my script the error message changes to:

"A general system error occurred: Failed to run script: Command exited with non-zero status 127"

/root/bin is in $PATH and the script has execution permissions for all users (755).

Have you seen this issue before or do you have any suggestions for me?

Thank you all!

Hi,

I have this alarm in my vCenter:

Anyone knows how to fix this?