I am constantly receiving this error when installing the SSO component on a newly installed 2008R2 server.

I have two vCenter 5.0u1 servers but would like to have the SSO, Inventory Service and Web Client all on a third server.  I have used the provisioned scripts to create the MSSQL table space on our clustered MSSQL database and to create the DB users.  I am logged into the SSO server as the domain administrator account and still get the error.  I have tried using alternative accounts that have domain admin privileges but no joy.  Each time I try a start with a fresh DB and a clean server to install SSO onto.

I know one can continue the install but when I did this I could not get my vCenter servers to link to the Web Client during their upgrade.  I am bemused that this error happens as a Domain Admin and would like to resolve this issue.

All help gratefully received.

Cheers

John

Hi,

I would like to build a lab, I need to install an NTP server appliance as a virtual machine,

Is there any Ready-to-use virtual appliance to implement it as a virtual machine in the ESXi environment ?

if there's, what is the best one, and what about the free ones ?

thanks in advanced ..

We’ve 2 Vcenters linked and I’ve upgraded one to 5.1 whilst one remains at 5.0 for a short while.

I want to use the old VI client alongside the web client on the new 5.1 server and I believed the old client was supported for a few more revisions until being retired.

Question is, when I point the VI old fat client to the new 6.1 Vcenter server I get an error which I sort of expected as now this Vcenter isn’t responsible for checking  and signing me on, it should now be the SSO server but you cant point the old client to a SSO server, only a web client I thought. The only way I can use the old client to access the 5.1 VCenter is to connect to the 5.0 server and as they’re linked I can administer it from there.

Any ideas?

I am having a requirement where we need to perform software upgrade using .pkg files.

So was curious to know if  VAMI's update service provides support for upgrade/installation of files other than RPMs like .pkg files?

Hi,

I've upgraded vCenter 5.0 to vCenter 5.1 U1a all is good, expect for the fact that when I eg. try to mirage a VM or set some settings on the cluster I get an error : The request failed because the remote server tool too long to respond. I have tried to shrink the vc database and that work for 2 min. and then backup to "The request failed because the remote server tool too long to respond".... dose anyone know what this is?

Thanks in advance

Hi

I am having issues add esx 4i base image into UM, it added my 5.1 ones. I have some 4.1.x hosts that I still manage.

Is this a feature ?

Hello,

As we know, it must to build a DNS server within vSphere 4.1 environment for HA function and so on.

If we wanna build a new vSphere 5.1 environment without AD integration and View solution, does vSphere 5.1 still need a DNS server ???

Thanks for your attention and kindly reply.

Hi all,

I'm planning an upgrade of 4.1 to 5.1.  I'm currently running MSSQL 2005 DB on a windows 2008 r2 server for vCenter. 

I just ran the 64 bit upgrade checker which has come back with a heap or warnings and quite a few errors.  I have no idea how bad this output actually is but it dosnt look good?!  Should this checker be passing with zero errors/warnings?

Here's how the results look:

2013 07/05/16 39:28

Running...

Created signature file C:\Users\duc37490\Documents\test2.zip

Warning: extra table in customer's database >> VCI_REMEDIATION_HISTORY

Warning: extra table in customer's database >> VCI_BASELINES

Warning: VCDB VPX_STAT_DEF.DEFAULT_LEVEL_SET column nullable >> NOT NULL; Customer >> NULL

Warning: VCDB VPX_STAT_DEF.DEFAULT_LEVEL_SET default value >> ((1)); Customer >> --

Warning: extra table in customer's database >> VCI_UPDATE_BASELINES

Warning: VCDB VPX_DVPORT.STATS_BYTE_IN_BROADCAST column position >> 28; Customer >> 27

Warning: VCDB VPX_DVPORT.REPUSH_NEEDED_FLG column position >> 46; Customer >> 45

Warning: VCDB VPX_DVPORT.STATS_PACKET_OUT_UNICAST column position >> 23; Customer >> 22

Warning: VCDB VPX_DVPORT.STATS_PACKET_IN_UNICAST column position >> 22; Customer >> 21

Warning: VCDB VPX_DVPORT.STATS_PACKET_IN_DROPPED column position >> 30; Customer >> 29

Warning: VCDB VPX_DVPORT.CONNECTEE_TYPE column position >> 36; Customer >> 35

Warning: VCDB VPX_DVPORT.CONNECTEE_NIC_KEY column position >> 37; Customer >> 36

Warning: VCDB VPX_DVPORT.NPT_INACTIVE_MISC column position >> 45; Customer >> 44

Warning: VCDB VPX_DVPORT.MAC_ADDRESS column position >> 17; Customer >> 16

Warning: VCDB VPX_DVPORT.RESERVED_TIME column position >> 39; Customer >> 38

Warning: VCDB VPX_DVPORT.STATS_PACKET_IN_BROADCAST column position >> 26; Customer >> 25

Warning: VCDB VPX_DVPORT.STATS_PACKET_OUT_DROPPED column position >> 31; Customer >> 30

Warning: VCDB VPX_DVPORT.STATS_BYTE_OUT_MULTICAST column position >> 21; Customer >> 20

Warning: VCDB VPX_DVPORT.POWERING_ON_FLG column position >> 40; Customer >> 39

Warning: VCDB VPX_DVPORT.STATS_PACKET_OUT_BROADCAST column position >> 27; Customer >> 26

Warning: VCDB VPX_DVPORT.PERSISTENCE_LOCATION column position >> 34; Customer >> 33

Warning: VCDB VPX_DVPORT.STATS_BYTE_IN_MULTICAST column position >> 20; Customer >> 19

Warning: VCDB VPX_DVPORT.STATS_BYTE_IN_UNICAST column position >> 24; Customer >> 23

Warning: VCDB VPX_DVPORT.CONNECTEE_ADDRESS column position >> 38; Customer >> 37

Warning: VCDB VPX_DVPORT.CONNECTEE column position >> 35; Customer >> 34

Warning: VCDB VPX_DVPORT.NPT_ACTIVE column position >> 42; Customer >> 41

Warning: VCDB VPX_DVPORT.STATS_BYTE_OUT_BROADCAST column position >> 29; Customer >> 28

Warning: VCDB VPX_DVPORT.STATS_PACKET_OUT_EXCEPTION column position >> 33; Customer >> 32

Warning: VCDB VPX_DVPORT.LAST_CONNECTEE column position >> 41; Customer >> 40

Warning: VCDB VPX_DVPORT.STATS_PACKET_OUT_MULTICAST column position >> 19; Customer >> 18

Warning: VCDB VPX_DVPORT.LINK_PEER column position >> 16; Customer >> 15

Warning: VCDB VPX_DVPORT.STATS_PACKET_IN_MULTICAST column position >> 18; Customer >> 17

Warning: VCDB VPX_DVPORT.STATS_BYTE_OUT_UNICAST column position >> 25; Customer >> 24

Warning: VCDB VPX_DVPORT.STATUS_DETAIL column position >> 15; Customer >> 46

Warning: VCDB VPX_DVPORT.NPT_INACTIVE_OTHER column position >> 44; Customer >> 43

Warning: VCDB VPX_DVPORT.STATS_PACKET_IN_EXCEPTION column position >> 32; Customer >> 31

Warning: VCDB VPX_DVPORT.NPT_INACTIVE_NET column position >> 43; Customer >> 42

Warning: extra table in customer's database >> VCI_OPERATION_HISTORY_SUBTASKS

Warning: extra table in customer's database >> VCI_TEXTFILES

Warning: extra table in customer's database >> vpx_device

Warning: VCDB VPX_VMFS_VOLUME.FORCEMOUNT_PERSIST_FLG column position >> 8; Customer >> 9

Warning: VCDB VPX_VMFS_VOLUME.VMFS_UPGRADABLE_FLG column position >> 9; Customer >> 7

Warning: VCDB VPX_VMFS_VOLUME.FORCEMOUNT_FLG column position >> 7; Customer >> 8

Warning: extra table in customer's database >> VCI_RUNNING_VC_TASKS

Warning: extra table in customer's database >> VCI_OPERATION_HISTORY

Warning: extra table in customer's database >> VCI_CONTENT_KEYS

Warning: extra table in customer's database >> VCI_LOCALES

Warning: extra table in customer's database >> VCI_TARGET_BASELINE_GROUPS

Warning: extra table in customer's database >> VCI_SCANRESULTS_TARGETS

Warning: extra table in customer's database >> VCI_PACKAGES

Warning: extra table in customer's database >> VCI_RECALL_PACKAGES

Error: VCDB VPX_USAGE_STAT.TIME_ID data type >> bigint; Customer >> int

Error: VCDB VPX_USAGE_STAT.STAT_VAL data type >> bigint; Customer >> numeric

Error: VCDB VPX_USAGE_STAT.COUNTER_ID data type >> bigint; Customer >> int

Warning: VCDB VPX_VIRTUAL_DISK.IORM_LIMIT column position >> 6; Customer >> 9

Warning: VCDB VPX_VIRTUAL_DISK.UPDATE_KEY column position >> 9; Customer >> 6

Warning: VCDB VPX_VIRTUAL_DISK.HARDWARE_DEVICE_CAPACITY_IN column position >> 7; Customer >> 4

Warning: VCDB VPX_VIRTUAL_DISK.IORM_SHARES_LEVEL column position >> 5; Customer >> 8

Warning: VCDB VPX_VIRTUAL_DISK.IORM_SHARES_SHARES column position >> 4; Customer >> 7

Warning: VCDB VPX_VIRTUAL_DISK.VM_ID column position >> 8; Customer >> 5

Warning: extra table in customer's database >> VCI_VMTOOLS_SCANRESULTS

Warning: extra table in customer's database >> VCI_VMHW_SCANRESULTS

Warning: extra table in customer's database >> VCI_BUNDLE_KEYS

Warning: extra table in customer's database >> VCI_SCANRESULTS

Warning: extra table in customer's database >> VCI_RECALL_UPDATES

Warning: extra table in customer's database >> vpx_stat_counter

Warning: extra table in customer's database >> VCI_HOST_UPGRADE_INTERFACE

Warning: VCDB VPX_DVS.UPGRADE_MODE column position >> 36; Customer >> 35

Warning: VCDB VPX_DVS.CAPAB_DVS_OPERATION column position >> 33; Customer >> 32

Warning: VCDB VPX_DVS.MAX_MTU column position >> 38; Customer >> 37

Warning: VCDB VPX_DVS.LDP_PROTOCOL_TYPE column position >> 40; Customer >> 39

Warning: VCDB VPX_DVS.PROMISCUOUS_VSPAN column position >> 39; Customer >> 38

Warning: VCDB VPX_DVS.CAPAB_DVPORTGROUP_OPERATION column position >> 34; Customer >> 33

Warning: VCDB VPX_DVS.LDP_OPERATION column position >> 41; Customer >> 40

Warning: VCDB VPX_DVS.CAPAB_DVPORT_OPERATION column position >> 35; Customer >> 34

Warning: VCDB VPX_DVS.PORT_COUNTER column position >> 37; Customer >> 36

Warning: VCDB VPX_DVS.NETWORK_RESOURCE_MGMT_ENABLED column position >> 32; Customer >> 41

Warning: extra table in customer's database >> VCI_UPDATE_PACKAGES

Warning: extra table in customer's database >> VCI_UPGRADE_OFFLINE_IDS

Warning: extra table in customer's database >> VCI_BASELINE_GROUPS

Warning: extra table in customer's database >> VCI_HOST_UPGRADE_BASELINES

Error: missing table in customer's database >> VPX_STAT_COUNTER

Warning: extra table in customer's database >> VCI_VC_CLEANUP_ACTION

Warning: VCDB VPX_DVHOST.HAS_SHADOW_PORTS column position >> 11; Customer >> 10

Warning: VCDB VPX_DVHOST.STATUS_DETAIL column position >> 10; Customer >> 11

Warning: extra table in customer's database >> VCI_TARGET_BASELINES

Warning: extra table in customer's database >> VCI_BASELINE_GROUP_BASELINES

Warning: VCDB VPX_DATASTORE_INFO.VPX_TYPE column position >> 24; Customer >> 19

Warning: VCDB VPX_DATASTORE_INFO.VMFS_MAX_BLOCKS column position >> 23; Customer >> 24

Warning: VCDB VPX_DATASTORE_INFO.VMFS_TYPE column position >> 21; Customer >> 22

Warning: VCDB VPX_DATASTORE_INFO.VMFS_CAPACITY column position >> 22; Customer >> 23

Warning: VCDB VPX_DATASTORE_INFO.VMFS_VERSION column position >> 18; Customer >> 17

Warning: VCDB VPX_DATASTORE_INFO.VMFS_NAME column position >> 20; Customer >> 21

Warning: VCDB VPX_DATASTORE_INFO.VMFS_UPGRADEABLE column position >> 19; Customer >> 18

Warning: VCDB VPX_DATASTORE_INFO.MAJOR_VERSION column position >> 16; Customer >> 15

Warning: VCDB VPX_DATASTORE_INFO.TAGGED_FOR_VMFSUPGRADE_FLG column position >> 15; Customer >> 20

Warning: VCDB VPX_DATASTORE_INFO.VMFS_UUID column position >> 17; Customer >> 16

Error: missing table in customer's database >> VPX_DEVICE

Warning: VCDB VPX_HOST.MANAGEMENT_IP column position >> 62; Customer >> 61

Warning: VCDB VPX_HOST.MAINTENANCE_MODE column position >> 54; Customer >> 53

Warning: VCDB VPX_HOST.LOCAL_IP_ADDRESS column position >> 59; Customer >> 58

Warning: VCDB VPX_HOST.POWER_STATE column position >> 55; Customer >> 54

Warning: VCDB VPX_HOST.FAULTTOLERANCE_ENABLED_FLG column position >> 63; Customer >> 62

Warning: VCDB VPX_HOST.HOST_KEY column position >> 60; Customer >> 59

Warning: VCDB VPX_HOST.ADMIN_DISABLED_FLG column position >> 61; Customer >> 60

Warning: VCDB VPX_HOST.RESOURCE_INFO column position >> 57; Customer >> 56

Warning: VCDB VPX_HOST.DAS_NODE_NAME column position >> 53; Customer >> 52

Warning: VCDB VPX_HOST.BOOT_TIME_ON_HOST column position >> 52; Customer >> 63

Warning: VCDB VPX_HOST.CONFIG_MANAGER column position >> 58; Customer >> 57

Warning: VCDB VPX_HOST.DEFAULT_VM_PATH column position >> 56; Customer >> 55

Warning: extra table in customer's database >> VCI_UPDATE_PLATFORMS

Warning: extra table in customer's database >> VCI_VERSION

Warning: extra table in customer's database >> VCI_METADATA_FILES

Warning: extra table in customer's database >> VCI_VA_APPLIANCES

Warning: VCDB VPX_COMPUTE_RESOURCE_DAS_VM.VM_COMPONENT_PROT_FT_NETWORK column position >> 14; Customer >> 13

Warning: VCDB VPX_COMPUTE_RESOURCE_DAS_VM.VM_COMPONENT_PROT_NETWORK column position >> 12; Customer >> 11

Warning: VCDB VPX_COMPUTE_RESOURCE_DAS_VM.VMHEALTH_VM_MONITORING column position >> 7; Customer >> 15

Warning: VCDB VPX_COMPUTE_RESOURCE_DAS_VM.VM_COMPONENT_PROT_STORAGE column position >> 13; Customer >> 12

Warning: VCDB VPX_COMPUTE_RESOURCE_DAS_VM.VMHEALTH_FAILURE_INTERVAL column position >> 8; Customer >> 7

Warning: VCDB VPX_COMPUTE_RESOURCE_DAS_VM.VM_COMPONENT_PROT_FT_STORAGE column position >> 15; Customer >> 14

Warning: VCDB VPX_COMPUTE_RESOURCE_DAS_VM.VMHEALTH_MIN_UPTIME column position >> 9; Customer >> 8

Warning: VCDB VPX_COMPUTE_RESOURCE_DAS_VM.VMHEALTH_MAX_FAILURE_WINDOW column position >> 11; Customer >> 10

Warning: VCDB VPX_COMPUTE_RESOURCE_DAS_VM.VMHEALTH_MAX_FAILURES column position >> 10; Customer >> 9

Warning: VCDB VPX_VM.AGGR_UNSHARED_STORAGE_SPACE column position >> 52; Customer >> 51

Warning: VCDB VPX_VM.ANNOTATION column position >> 42; Customer >> 41

Warning: VCDB VPX_VM.PENDING_ANNOT_SET_FLG column position >> 45; Customer >> 44

Warning: VCDB VPX_VM.DESCRIPTION column position >> 41; Customer >> 40

Warning: VCDB VPX_VM.AGGR_COMMITED_STORAGE_SPACE column position >> 50; Customer >> 49

Warning: VCDB VPX_VM.VAPP_CONFIG column position >> 49; Customer >> 48

Warning: VCDB VPX_VM.PENDING_ANNOTATION column position >> 44; Customer >> 43

Warning: VCDB VPX_VM.RECORD_REPLAY_STATE column position >> 55; Customer >> 54

Error: VCDB VPX_VM.ONLINE_STANDBY data type >> numeric; Customer >> decimal

Warning: VCDB VPX_VM.ONLINE_STANDBY column position >> 40; Customer >> 56

Warning: VCDB VPX_VM.FILE_LAYOUT column position >> 46; Customer >> 45

Warning: VCDB VPX_VM.FILE_LAYOUT_X column position >> 47; Customer >> 46

Warning: VCDB VPX_VM.STORAGE_SPACE_UPDATED_TIME column position >> 53; Customer >> 52

Warning: VCDB VPX_VM.DEV_RUNTIME column position >> 56; Customer >> 55

Warning: VCDB VPX_VM.AGGR_UNCOMMITED_STORAGE_SPACE column position >> 51; Customer >> 50

Warning: VCDB VPX_VM.FAULT_TOLERANCE_STATE column position >> 54; Customer >> 53

Warning: VCDB VPX_VM.UUID_INSTANCE column position >> 48; Customer >> 47

Warning: VCDB VPX_VM.PENDING_NAME column position >> 43; Customer >> 42

Warning: VCDB VPX_SN_VIRTUAL_DISK.IORM_LIMIT column position >> 6; Customer >> 9

Warning: VCDB VPX_SN_VIRTUAL_DISK.UPDATE_KEY column position >> 9; Customer >> 6

Warning: VCDB VPX_SN_VIRTUAL_DISK.HARDWARE_DEVICE_CAPACITY_IN column position >> 7; Customer >> 4

Warning: VCDB VPX_SN_VIRTUAL_DISK.IORM_SHARES_LEVEL column position >> 5; Customer >> 8

Warning: VCDB VPX_SN_VIRTUAL_DISK.IORM_SHARES_SHARES column position >> 4; Customer >> 7

Warning: VCDB VPX_SN_VIRTUAL_DISK.SN_ID column position >> 8; Customer >> 5

Warning: VCDB VPX_DVPORTGROUP.NUM_PORT column position >> 14; Customer >> 13

Warning: VCDB VPX_DVPORTGROUP.UPLINK_PORTGROUP_FLG column position >> 15; Customer >> 14

Warning: VCDB VPX_DVPORTGROUP.POLICY_UPLINK_OVERRIDE column position >> 17; Customer >> 16

Warning: VCDB VPX_DVPORTGROUP.POLICY_OVERLAY_OVERRIDE column position >> 13; Customer >> 18

Warning: VCDB VPX_DVPORTGROUP.POLICY_VLAN_OVERRIDE column position >> 16; Customer >> 15

Warning: VCDB VPX_DVPORTGROUP.POLICY_SECURITY_OVERRIDE column position >> 18; Customer >> 17

Warning: extra table in customer's database >> VCI_SCANHISTORY

Warning: extra table in customer's database >> VCI_HOST_UPGRADES

Warning: extra table in customer's database >> VCI_TARGET_ENTITIES

Warning: extra table in customer's database >> VCI_SCANHISTORY_TARGETS

Warning: extra table in customer's database >> VCI_NOTIFICATIONS

Warning: extra table in customer's database >> VCI_PLATFORM_METADATA

Warning: extra table in customer's database >> VCI_VA_PRODUCTS

Warning: extra table in customer's database >> VCI_VA_UPGRADE_BASELINES

Warning: extra table in customer's database >> VCI_RECALL_RESOLUTIONS

Error: VCDB VPX_SAMPLE_TIME4.TIME_ID data type >> bigint; Customer >> numeric

Error: VCDB VPX_SAMPLE_TIME4.ROLLUP_COUNTER data type >> bigint; Customer >> numeric

Error: VCDB VPX_SAMPLE_TIME3.TIME_ID data type >> bigint; Customer >> numeric

Error: VCDB VPX_SAMPLE_TIME3.ROLLUP_COUNTER data type >> bigint; Customer >> numeric

Warning: extra table in customer's database >> VCI_AGING_SNAPSHOTS

Error: VCDB VPX_SAMPLE_TIME2.TIME_ID data type >> bigint; Customer >> numeric

Error: VCDB VPX_SAMPLE_TIME2.ROLLUP_COUNTER data type >> bigint; Customer >> numeric

Warning: extra table in customer's database >> VCI_SCANRESULTS_BASELINES

Error: VCDB VPX_SAMPLE_TIME1.TIME_ID data type >> bigint; Customer >> numeric

Error: VCDB VPX_SAMPLE_TIME1.ROLLUP_COUNTER data type >> bigint; Customer >> numeric

Error: VCDB VPX_HIST_STAT2.TIME_ID data type >> bigint; Customer >> numeric

Error: VCDB VPX_HIST_STAT2.STAT_VAL data type >> bigint; Customer >> numeric

Error: VCDB VPX_HIST_STAT2.COUNTER_ID data type >> bigint; Customer >> numeric

Error: VCDB VPX_HIST_STAT3.TIME_ID data type >> bigint; Customer >> numeric

Error: VCDB VPX_HIST_STAT3.STAT_VAL data type >> bigint; Customer >> numeric

Error: VCDB VPX_HIST_STAT3.COUNTER_ID data type >> bigint; Customer >> numeric

Warning: extra table in customer's database >> VCI_UPDATE_BASELINES_EXPANDED

Warning: extra table in customer's database >> VCI_TASK_STATS

Error: VCDB VPX_HIST_STAT1.TIME_ID data type >> bigint; Customer >> numeric

Error: VCDB VPX_HIST_STAT1.STAT_VAL data type >> bigint; Customer >> numeric

Error: VCDB VPX_HIST_STAT1.COUNTER_ID data type >> bigint; Customer >> numeric

Warning: extra table in customer's database >> VCI_UPDATE_CONFLICT_INFO

Error: VCDB VPX_HIST_STAT4.TIME_ID data type >> bigint; Customer >> numeric

Error: VCDB VPX_HIST_STAT4.STAT_VAL data type >> bigint; Customer >> numeric

Error: VCDB VPX_HIST_STAT4.COUNTER_ID data type >> bigint; Customer >> numeric

Warning: extra table in customer's database >> VCI_VMHW_COMPATIBILITY

Warning: extra table in customer's database >> VCI_RESTORING_TEMPLATES

Warning: extra table in customer's database >> VCI_VA_UPGRADES

Warning: extra table in customer's database >> VCI_PACKAGE_LOCALES

Warning: extra table in customer's database >> VCI_UPDATES

Warning: extra table in customer's database >> VCI_PLATFORMS

Warning: extra table in customer's database >> VCI_VMHW_VERSIONS

Warning: extra table in customer's database >> VCI_SEQUENCE

Warning: extra table in customer's database >> VCI_PARAMETERS

Warning: extra table in customer's database >> VCI_SCANRESULTS_CONFRESUPD

Warning: VCDB VPX_COMPUTE_RESOURCE.DRS_VM_OVERRIDES_ENABLED_FLG column position >> 30; Customer >> 29

Warning: VCDB VPX_COMPUTE_RESOURCE.VMHEALTH_FAILURE_INTERVAL column position >> 23; Customer >> 22

Warning: VCDB VPX_COMPUTE_RESOURCE.VM_COMPONENT_PROT_FT_STORAGE column position >> 38; Customer >> 36

Warning: VCDB VPX_COMPUTE_RESOURCE.DAS_VM_MONITORING column position >> 32; Customer >> 39

Warning: VCDB VPX_COMPUTE_RESOURCE.CLUSTER_STATE column position >> 33; Customer >> 31

Warning: VCDB VPX_COMPUTE_RESOURCE.DAS_HOST_MONITORING column position >> 31; Customer >> 30

Warning: VCDB VPX_COMPUTE_RESOURCE.FAILOVER_MEM_RESOURCES column position >> 28; Customer >> 27

Warning: VCDB VPX_COMPUTE_RESOURCE.VMHEALTH_MAX_FAILURE_WINDOW column position >> 26; Customer >> 25

Warning: VCDB VPX_COMPUTE_RESOURCE.HOST_POWER_ACTION_RATE column position >> 29; Customer >> 28

Warning: VCDB VPX_COMPUTE_RESOURCE.VMHEALTH_MAX_FAILURES column position >> 25; Customer >> 24

Warning: VCDB VPX_COMPUTE_RESOURCE.VM_COMPONENT_PROT_FT_NETWORK column position >> 37; Customer >> 35

Warning: VCDB VPX_COMPUTE_RESOURCE.VM_COMPONENT_PROT_NETWORK column position >> 35; Customer >> 33

Warning: VCDB VPX_COMPUTE_RESOURCE.VMHEALTH_VM_MONITORING column position >> 22; Customer >> 38

Warning: VCDB VPX_COMPUTE_RESOURCE.VM_COMPONENT_PROT_STORAGE column position >> 36; Customer >> 34

Warning: VCDB VPX_COMPUTE_RESOURCE.GROUPS_INFO column position >> 39; Customer >> 37

Warning: VCDB VPX_COMPUTE_RESOURCE.DAS_VM_COMP_PROTECTING column position >> 34; Customer >> 32

Warning: VCDB VPX_COMPUTE_RESOURCE.VMHEALTH_MIN_UPTIME column position >> 24; Customer >> 23

Warning: VCDB VPX_COMPUTE_RESOURCE.FAILOVER_CPU_RESOURCES column position >> 27; Customer >> 26

Warning: extra view in customer's database >> VUMV_UPDATES

Warning: extra view in customer's database >> VUMV_VA_APPLIANCE

Warning: extra view in customer's database >> VUMV_ENTITY_REMEDIATION_HIST

Warning: extra view in customer's database >> VUMV_BASELINE_GROUPS

Warning: extra view in customer's database >> VUMV_UPDATE_PRODUCT_DETAILS

Warning: extra view in customer's database >> VUMV_BASELINE_UPDATE_DETAILS

Warning: extra view in customer's database >> VUMV_UPDATE_PRODUCT

Warning: extra view in customer's database >> VUMV_VA_PRODUCTS

Warning: extra view in customer's database >> VUMV_BASELINE_ENTITY

Warning: extra view in customer's database >> VUMV_ENTITY_SCAN_HISTORY

Warning: extra view in customer's database >> VUMV_HOST_UPGRADES

Warning: extra view in customer's database >> VUMV_BASELINE_GROUP_MEMBERS

Warning: extra view in customer's database >> VUMV_VERSION

Warning: extra view in customer's database >> VUMV_VMHW_SCAN_RESULTS

Warning: extra view in customer's database >> VUMV_ENTITY_SCAN_RESULTS

Warning: extra view in customer's database >> VUMV_UPDATE_PATCHES

Warning: extra view in customer's database >> VUMV_BASELINES

Warning: extra view in customer's database >> VUMV_PRODUCTS

Warning: extra view in customer's database >> VUMV_PATCHES

Warning: extra view in customer's database >> VUMV_VMTOOLS_SCAN_RESULTS

Warning: extra view in customer's database >> VUMV_VA_UPGRADES

Warning: extra routine in customer's database >> vci_queryEntityBLStatus

Warning: extra routine in customer's database >> vci_expand_patches

Warning: extra routine in customer's database >> vci_CheckBaselineConflict

Warning: extra routine in customer's database >> load_usage_stats_proc

Warning: extra routine in customer's database >> vci_populateBaselineUpdates

Warning: extra routine in customer's database >> vci_compBaselineComplianceLeaf

Warning: extra routine in customer's database >> load_stats_proc

Warning: extra routine in customer's database >> vci_MultiBLComplianceLeafList

Done!

Hello,

We are going to be moving to a new HPBLC7000 with ProLiant BL460c G7 blades. Currently We are running our environment on IBM Blade center H. The SAN will stay the same as it's fairly new. so Questions I have are regarding how to move the vm's off of IBM blade to HP blade. We are currently at esxi 4.1 and our vcenter server is a physical machine using sql server 2005 express. I would like to take this opportunity to upgrade to 5.1 and make the  VC a virtual machine with its' Database on a separate VM. So my questions are how do I accomplish this using a best practice approach. Some questions I have are:

1) do I need to even bother importing current VC DB onto new VC?

2) Do I need two virtual centers or Do I just add the new HP Host to current vcenter and vmotion(if CPU are compatible, if not what are my options?)

3) I'm just confused if I need to first move vm's onto new blade and then upgrade create new Vsphere on HP blade and then somehow migrate my vm's over?

I just need some guidance on how to best go about this. Thank You

Guys,

It has been almost 5 years of running version 4.  It is time for upgrading .  The 8 GB ram limitation on the board is past due!  Looking at these items below.  The machine is for home use for testing/production, so I don't want any power hogging machine.

CPU: Intel Core i7-3770S Ivy Bridge 3.1GHz (3.9GHz Turbo) LGA 1155 65W Quad-Core Desktop

Board: Intel BOXDQ77MK Socket LGA1155 Desktop Board - MicroATX, Socket H2 (LGA1155), DDR3 1600 MHz

Memory: 32 GB of these rams--> Corsair Vengeance 16GB (2x8GB) DDR3 1600 MHz (PC3 12800) Desktop Memory (CMZ16GX3M2A1600C10) or G.SKILL Sniper Gaming Series 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)

Drive for OS (5.1): Crucial M4 CT064M4SSD2 2.5" 64GB SATA III MLC Internal Solid State Drive (SSD)

     - The VMs are going to be housed in existing FreeNas box.  Also had run OS on USB before but it didn't last after 3 years, so going to SSD this time.

Would the CPU/Mobo combo cover most VMware features I need?  Also, what is a minimum power supply you recommend?  Btw, I did find some reviews on other forums regarding the hardware above.  Just want a confirmation here.

TIA,

tntrac

For the event error: "The VMware vSphere Web Client service terminated with service-specific error Incorrect function"

This is how I resolved:

I figured it out thx to this guy: vSphere 5.1 Web Client: Service Error | vmwiz<-- well, _he_ figured it out....

The upgrade pushed my piddly 2gb vm vcenter host over the edge and/or, java did I guess.

I pushed ram up to 4gb and now it works fine.

Thanks all

¬_¬

-----

this below was the amping I did before figuring it out:

-----

Edit: I just used this post to check ports:

http://communities.vmware.com/thread/423231?start=0&tstart=0

doing "netstat -bano | find "9443" nothing is using it.

I went through the entire upgrade today from vCenter 4.1 to 5.1, installing simple install: SSO, Inventory Server and vCenter Server.  It all went great.  Lastly, I installed the Web Server Client.  It all isntalled good.  I fully expected to be skating about now.  But I could not get to https://vcenter.domain.com:9443/.  Checking, I see the "VMware vSphere Web Client" service not started.  It will not start.

I have labored in google.com.  Based on my searches, I've tried restarting my vCenter host vm, enabled/disabled IPV6 and I ever tried this KB for 5.0, but it got me no where: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2012473

I can get to http://localhost fine and pull up the "VMware vSphere Welcome" page.  If I click on "Log in to vSphere Web Client" I get this:

I do not know what else to do.  I'm afraid my backups will now fail

After reading lots of documentation via the Update Center site and some other posts on this community I wanted to see if the plan I have is ok or is there a better way?  I've upgraded 3.5 to 4.1 before but it was using the same hardware...this time around...I'm using new hardware for the new vSphere ESXi & vCenter 5.1 infrastructure.

So, this is what I want to do and hopefully the community's input would help guide me to use the best approach for my needs.

Existing environment consists of:

vCenter 4.1 on a physical Windows Server 2008 R2 server with databases running on a separate physical SQL 2008 R2 cluster.  7 ESX 4.1 host servers.  4 of these hosts are in an EVC compatible cluster, 1 is in a DMZ EVC cluster with another host that will be moved into that cluster after upgrade is completed.  1 is a stand alone ESX 4.1 server that will be decommissioned.  VM's on this server are from our TEST/DEV environment and will be cold migrated over to new 5.1 cluster.  All shared storage (i.e. - datastores running VMFS-3) for existing environment is running on our SAN.

New environment will consist of:

4 new ESXi 5.1 host servers running in a cluster.  2 existing DMZ host servers (old current hardware) **These will be replaced later with 2 new servers identical to the existing new hardware being used.  Migrating vCenter Server to a different host machine following KB 5850444.  vCenter 5.1 on a VM running Windows Server 2012 with databases on a separate physical SQL 2008 R2 cluster.  All shared storage (i.e. - datastores running VMFS-5) for new environment is running on our SAN. 

Here is a summary of my plan:

1 - Install ESXi 5.1 on one of the new host servers

2 - Connect to SAN and Create new VMFS-5 datastores

3 - Create a new vCenter 5.1 VM running on new VMFS-5 using Windows Server 2012 OS pointing to existing databases on my physical SQL 2008 R2 cluster.  Use the temporary Eval license option for new vCenter 5.1.  **Follow KB article 5850444 instructions minus database movement since databases will stay in its existing location

4 - Remove existing ESX 4 host servers from original vCenter 4.1 into new vCenter 5.1 inventory **Not sure about this one since my new vCenter 5.1 will be pointing at the existing database, so wouldn't the ESX 4.1 host automatically show up?

5 - VM's will be moved using Enhanced vMotion to new ESXi 5.1 hosts & VMFS-5 datastores on SAN

6 - ESX 4.1 host will then be removed/retired from vCenter 5.1

7 - Upgrade all licensing to new 5.1 and apply to vCenter 5.1 & ESXi 5.1 hosts

8 - Upgrade VM's (VMware Tools then Hardware to 9) using Update Manager

That's it, any input would be greatly appreciated...thanks.

Hi,

We are currently using VMware Essentials and I a few questions on updating our vCenter appliance and ESXi.  Currently, our vCenter appliance version is 5.0.0.5480 Build 804279.  Our ESXi version is 5.0.0 Build 768111.  I would like to get everything properly updated and current.  Do I first update the appliance and then ESXi?  I logged into the web GUI for the appliance and browsed to the update tab and noticed there is an update available (5.0.0.6194 Build 920217 and it also says version 5.0.0 Update 2).  Is it safe to update from the web GUI by clicking install updates?  I am familiar with using update manager to update ESXi.  Just really need advice on the vCenter appliance.  Thanks for any help!

Help!

We have HP BL685c blade servers with esx 4.1 on them. Yesterday, I was trying to upgrade the esx4.1 to esxi5.0 with HP custom image esxi5.0 U1 ISO image. Everything seems working. except for two things.

1. Every reboot, it took around 30 minutes, it start to slow down after vmw_satp_eva loaded successfully.After this point, it took around 25 minutes.

2. Management network test fail.

We have HP BL685c and the fabric and HP fiber channel storage. I am thinking if there is something I need to configure after the esxi5.0 image was installed.

The host sees all four nics connected. I select the first one as the management nic and assign static IP to it.

Hi,

I am installing ESXi 5.1 on a HP BL460c G7 blade. It is stuck at 27% and has been for the the last hour. Previously tried yesterday and it got stuck at the same stage.

I have 6 of these blades and have successfully installed one with the same software. No hardware issues are reported in the OA, but i have swapped the HDDs with ones from one of the others and has made no difference.

Any ideas?

Janine

Hi I am trying to install esxi 5.1 but during install I get an error no physical network cards detected and then aborts instillation. i know that when installing windows my network card isnt detected until i install its driver, but i am not sure how i can install the driers for exsi.

when i try search the compatibility guide I get no results.

My specs are:

MB: FOXCONN P9657AA
BIOS VERSION: Not Sure
CPU: Intel(R) Core(TM)2 CPU
6420 @ 2.13GHz
2.13GHz, 8GB of RAM
Memory: (DDR2 240Pins) (CORSAIR)
VGA: NVIDIA GeForce 8500GT NX85T256H PCI Express X16
PSU: Not Sure
HDD: 1 MAXTOR IDE HDD 250GB
CD/DVD: LITE-ON DVDRW LH-20A1P SCSI CdROM Device
OS: N/A
Network Cards: Onboard LAN

                           LAN Chipset - Marvell 88E8056

                           Max LAN Speed - 10/100/1000Mbps

and a second network card not sure of brand, i pulled it out of an old PC I have laying around.

thanks

Hi,

I booted the latest ESXi 5 image from a USB and installed it (to the same USB stick).

Once ESXi has been installed, it will not boot at all.

When trying to start it just flickers a quick black screen and the computer reboots.

There is no text nor any visual queues that the boot sequence of ESXi started.

If I take the same USB stick put it in any other computer I see the boot sequence starting.

I'm using a mainboard (with latest Bios): Asus h87i-plus

I can boot all kinds of stuff without an issue (Win 8, Openindiana, ESXI installer). So it seems to be an issue only with the installed ESXi version.

Any idea ? I would have expected it to at least start booting and if my hw is not compatible to give me all sorts of errors.

But not getting anything is tough to troubleshoot

Thanks!

Hi

I have a query with VUM which we use to update/patch our ESXi hosts.

The build version of our hosts are currently 5.1 (799733).

The build version of our vCenters are currently 5.1 (947673).

I want to patch all the hosts using VUM - it is showing there are 20 updates to apply (17 from VMware & 3 from HP).

When i update the hosts selecting all the available patches/updates the build version of the hosts change to 1117900 which is the latest ESXi 5.1 Update 1!  When referencing VMware's interoperability matrix this configurationh apparently isn't supported!!

Hence i'm concerned that VUM is upgrading the version of ESXi instead of merely applying patches.

Is this ESXi-vCenter configuration supported/usable or should i roll back - thankfully the cluster isn't Live yet..?

The obvious route to take would be to upgrade vCenter and the numerous related components to Update1 first, but other factors don't allow this at present.

I look forward to any advice the community has.

Greg

Hi everyone....

I have a ESXi 5.1 U1 cluster with 5 AMD Opteron Processors model 2216 and I want to add a new AMD Opteron server with processor model 6272.

I want to know if it's possible to mix both cpu models and if yes, what I have to do to make this possible?

I know EVC Mode but i'm not familiar with this option.

Can someone can give me some informations of how to configure EVC Mode to do this, of course if it's the solution?

For now, if I try to migrate a vm on the new server, I receive this error message :

The virtual machine requires hardware features that are unsupported or disabled on the target host:

Carryless multiply ( PCLMULQDQ ) ( see KB 1034926 )

SSSE3

SSE4.1

SSE4.2

AES Instructions  ( AES-NI ) ( see KB 1034926 )

If possible, use a cluster with Enhaced vMotion Compatibility ( EVC ) enabled, see KB article 1003212

CPUID details : incompatibility at level 0x1 register ' ecx '.

Host bits : 0000:0010:1001:1000:0010:0010:0000:0011

Required : x0xx:xx0x:00x0:0000:001x:0000:0000:x001

Hi all, I'm planning my "simple install" upgrade from vCenter 4.1 to 5.1 running on a windows 2008 R2 x64 machine which will be running MSSQL 2005 SP4 32BIT

I have read through the install guide in the documentation centre which details how to set the single sign on database up using the scripts provided with the installer.  My question is am I safe to use these scripts to set up the SSO database on my MSSQL 2005 in advance?   i.e a week in advance, just so that there is less work to do come upgrade day? 

Also, is the SSO database OK to run from my MSSQL2005 x32 sp4 instance?  I know that this database is compatible with vCentre 5,1, but the SSO database isn't mentioned specifically.  I'm assuming it is.

Cheers,

Matt