Hello,

I have been building a lab environment using the hardware below with VMware Workstation 8.

Physical Hardware:

Dell Precision 690

Intel Xeon CPU 3.73GHz (2 processors)

Memory: 12GB

Windows 7 Pro 64bit

Virtual Setup:

Workstation 8

VM for a DC

VM for vCenter

VM for FreeNAS 8

VM for ESXi5 1

VM for ESXi5 2

I have everything built out but after configured the HA.  I have been getting the following errors:

1. Under summery tap of the ESXi5 host.

            vSphere HA State:  Host Failed

The vSphere HA Master Agent connected to vCenter Server cannot reach the host over the management network or via the configured heartbeat datastores.

It will attempt to restart the vSphere HA protected VMs that were running on this host at the time that the failure was observed.

2. Under Tasks & Events of the ESXi5 host.

            Configuring vSphere HA:

A general system error occurred: Failed to increase memory reservation and limit for host/vim/vmvisor from -1 to 100.  HA may not configure on the host.

I have tried searching the forum and haven't had any luck.  I have also search Google and no luck.

Any help would be greatly appreciated!

Thanks in advance!

BB

Creating a Host Profile from a host gives on most of our hosts, but not all, the following error:

A general system error occurred:

 

See the error stack for details on the cause of this problem.

 

Error Stack

 

Call "HostProfileManager.CreateProfile" for object "HostProfileManager" on vCenter Server <vCenter Server Name> failed.

Error: Unexpected language: .

Does anybody have a clue how to solve this problem?

We are running ESXi and vCenter Server version 5.1 Update 1.

Hello,

Please excuse for any points missed as I am a newbie trying to learn vSphere in lab environment.

I have two vCenter servers VC01 and VC02. VC01 being the primary. I was able to successfully setup LINKED mode but I think my understanding of it was something different.

Trying to achieve:

I am trying to achieve that both servers show the same inventory when i login to either of the servers.

What I got:

What i got was that VC02 now shows in vSphere client when i log on to VC01. That is not what I wanted. How can i make it so I see the same inventory for both of the servers? Is it because I don't have a a shared SQL database? I chose to install the bundled SQL database for both of the vCenter installations. If someone and please clarify for me...it would be MUCH appreciated.

Thanks Much.!!

Hi all,

We have deployed vCenter 5.0 u1 with Oracle 11g R2. Couple of weeks later onwards we started hitting the Temp table space issue (Error: Error[VdbODBCError] (-1) "ODBC error: (HY000) - [Oracle][ODBC][Ora]ORA-01652: unable to extend temp segment by 128 in tablespace TEMP

" is returned when executing SQL statement) and vCenter is doing down regularly (Once in 2 weeks).  We approached VMware support and they provide fix. And this script will create a Stored Procedure and SQL job, which will clean sessions using TEMP segments. This runs in once in 12 hours But the issue is not fixed we are still hitting the issue also jobs runs with out any issues.

can any one help on this please?

Thanks

Jithin

Hello

When user logon on web console vcenter 5.1 and provide a bad password or login information the notifications are in french. Also if the user add on the link address ?locale=en_US.

Waht I can do to change to English ? I will change the locale on the server (Server installed in English wndows 2008 R2 Std)

Screen shoot pdf file

Thanks in advance.

Tiberias

vCenter Simple Install 5.1 continues to fail with error 29114. I choose the SQL 2008 Express installation, because it's already installed for another app.

I've looked at this help, but did not work.

VMware KB: Installing vCenter Single Sign On in an IPv6 environment fails with the error: Error 29114.Cannot connect…

Any help would be greatly appreciated.

Hi,

I want to switch the language of our email alerts from German to Englisch. I followed the steps described in the KB:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015646

Now vCenter comes up with mixed-languaged email alerts like:

#########################################

Target: <CLUSTERNAME>

Previous Status: green

New Status: yellow

Alarm Definition:

([Event alarm expression: vSphere HA hat eine Failover-Aktion initiiert; Status = yellow] OR [Event alarm expression: vSphere HA hat eine Failover-Aktion abgeschlossen; Status = green])

Event details:

vSphere HA hat eine Failover-Aktion einer virtuellen Maschine im Cluster <CLUSTERNAME> im Datencenter <DATACENTERNAME> initiiert

#########################################

How can I fix it so we'll receive email alerts only in English?

Regards

I am running vSphere 5.1 with all patches applied to everything.

When Windows Server 2012 was RTMed I started building a primary server to use for clones for all of our other ones.  This worked fine and we have slowly been deploying 2012 VMs for a while.

Recently my backup administrator came to me with a question about an extra disk it is seeing on the 2012 VMs that is not shown anywhere else.

It looks like this:

No label, 0MB, Healthy Primary Partition.  And NOT the system partition that I know should be there.

I went back and converted my template back to a VM to see if this disk was included in the original clone that has been used for all of the VMs showing it and it is not showing there.  Nor is it showing on any of the physical 2012 hosts which we installed Windows Server 2012 on.

So it seems like there is something during the clone and/or sysprep process that is adding this extra unnecessary disk for server 2012 VMs.  Server 2008 Template still works fine for everything - no  extra disks shown.

Anyone else seeing this?  We talked to Commvault, our backup platform, and they say they are seeing this in their labs as well.

Hi guys,

I am attempting to perform a sanity check of our vCenter 5.1 server to the most recent version of 5.1.  To accomplish this I have created an isloated lab and cloned the production vCenter and its SQL back-end machine into it.  They have connectivity to each other however vCenter services will not start.

I strongly believe that this is because SSO requires AD in order for the vCenter services to start, however I do not have AD in my islolated lab.

Is there any way to accomplish this without bringing a production AD controller into the lab?

Thanks.

Hi, I upgraded vCenter 4.1 to 5.1 update 1a over the weekend, which I might add was fun!!   I got there in the end though.  Today, I was messing with the Groups/Users in the web client and accidentaly deleted the Administrators Group from the SSO Users and Groups.  when logged in as Admin@system-domain, I can create a new group but how do i give it the admin priveledges to be able to administer SSO.  At the moment I have a domain account which is in the _Regular_Users_ and LSAAdministators group but if I log into the Web Client with that account, it won't let me administer SSO... it will let me administer vCenter cos it has the Administrators Role assigned to it.   I don't want to just rely on the single Admin@system-domain account, I want to add another admin account.

Appreciate any help.

Thanks in advance

Chris

Hello!

It's just a question about how to make correct snapshot and revert to it for VM where vCenter was installed, in case vCenter's DB was installed on another VM...

I mean, vCenter has use it's own database and in case we revert vCenter VM to snapshot - is it possible to have problems with database data? Can we have  corrupted data or  something like  this?

Or  it's necessary to make 2 snapshots at the same time - from vCenter VM and from DB VM?

Let's assume latest virtual environment - ESXi 5.1, vCenter 5.1, full database from MS SQL 2008 R2 or Oracle...

Can anybody describe his suggestion or knowledge?

I use ESX5.1 and vCenter .

I could not start vCenter service and vpxd log is the below.

I tried restart of SQL service and inventry service but still in problem.

2013-07-14T17:29:44.423+09:00 [04060 error 'Default'] Found dangling SSL error: [0] error:00000001:lib(0):func(0):reason(1)

2013-07-14T17:29:44.423+09:00 [04060 error 'Default'] Found dangling SSL error: [1] error:00000001:lib(0):func(0):reason(1)

2013-07-14T17:29:44.501+09:00 [04060 error '[SSO][SsoFactory_CreateFacade]'] Unable to create SSO facade: vmodl.fault.SystemError.

2013-07-14T17:29:44.517+09:00 [04060 warning 'VpxProfiler'] Vpxd::ServerApp::Init [Vpx::Common::Sso::SsoFactory_CreateFacade(sslContext, ssoFacadeConstPtr)] took 1453 ms

2013-07-14T17:29:44.517+09:00 [04060 error 'vpxdvpxdMain'] [Vpxd::ServerApp::Init] Init failed: Vpx::Common::Sso::SsoFactory_CreateFacade(sslContext, ssoFacadeConstPtr)

--> Backtrace:

--> backtrace[00] rip 000000018018aa3a

--> backtrace[01] rip 0000000180102b18

--> backtrace[02] rip 0000000180103f3e

--> backtrace[03] rip 000000018008d6db

--> backtrace[04] rip 0000000000395c2c

--> backtrace[05] rip 00000000003b6512

--> backtrace[06] rip 0000000140912821

--> backtrace[07] rip 000000014090c63c

--> backtrace[08] rip 0000000140b2cbeb

--> backtrace[09] rip 000007fefe31a82d

--> backtrace[10] rip 00000000771c652d

--> backtrace[11] rip 00000000773fc521

-->

2013-07-14T17:29:44.532+09:00 [04060 warning 'VpxProfiler'] ServerApp::Init [TotalTime] took 46812 ms

2013-07-14T17:29:44.532+09:00 [04060 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down...

2013-07-14T17:29:44.548+09:00 [04060 info 'vpxdvpxdSupportManager'] Wrote uptime information

2013-07-14T17:29:46.079+09:00 [04124 warning 'VpxProfiler' opID=SWI-b41d76d0] VpxUtil_InvokeWithOpId [TotalTime] took 12016 ms

2013-07-14T17:29:58.095+09:00 [04124 warning 'VpxProfiler' opID=SWI-ab3cdc2c] VpxUtil_InvokeWithOpId [TotalTime] took 12016 ms

2013-07-14T17:30:04.157+09:00 [04060 info 'Default'] Forcing shutdown of VMware VirtualCenter now

we are in the process of preparing for the upgrade of our existing environment from vSphere 5.0 to vSphere 5.1.  I’ve attempted a mock installation of SSO Server and have also run the SSO pre-installation check script and we have discovered an issue in our environment.  In order to explain the issue I’ll need to provide a bit of background information on DNS configuration in our environment.

There are two DNS solutions in our environment, Corporate DNS (UNIX) and DDNS (Dynamic DNS – Active Directory).  DDNS was deployed with introduction of AD, prior to than all systems were using Corporate DNS.  When DDNS was introduced DNS services were not migrated to it, instead DDNS is used solely by AD and Windows Server/Client environment. Additionally DDNS is not configured for reverse lookup DNS resolution, all such requests are forwarded to Corporate DNS. 

As you may or may not be aware one of the requirements for SSO deployment is to have reverse lookup DNS configured and for each DC and SSO server to have a properly configured PTR records (http://kb.vmware.com/kb/2033880) .  Since we are not using DDNS for reverse lookup resolution PTR records are non-existent.  Consequently the installation of SSO throws warning regarding the reverse lookup DNS failure and the SSO pre-installation check script displays warnings re “IP Address to Name Check” for the SSO Server and every DC in the domain.

we are just wondering if anybody else had come across this issue? and if so what they did to resolved the issue

any help would be appreciated 

ESX5.1とｖCenterの評価版を使用してGuestOSのWindows2008R2をインストールしようとするのですが、

電源をいれても途中でPowerOffになります。

エラーメッセージには　

当社はお客様

のサポート資格に基づいて対応します。

とかいてあります。これは何でしょうか？

192.168.0.8 からのエラー メッセージ: 当社はお客様

のサポート資格に基づいて対応します。

エラー

2013/07/15 16:46:54

win2008R2

User

Since the upgrade of vSphere server from version 5.0 to 5.1 some users are no longer able to login, but the vSphere web client works fine.

They get the error: The server 'xxx' took to long to respond. (The command was timed out as the remote server was taking too long to resond.)

The client log file shows this:

at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName, Object[])
   at Vmomi.SessionManager.LoginBySSPI(String, String)
   at VmomiSupport.VcServiceImpl.LoginBySSPI(LoginSpecInternal2)
   at VmomiSupport.VcServiceImpl.Login(LoginSpec)
   at VirtualInfrastructure.LoginMain.Process(BackgroundWorker, DoWorkEventArgs)
   at VirtualInfrastructure.LoginWorkerImpl.Worker_DoWork(Object, DoWorkEventArgs)
...
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object)
[viclient:Error   :P: 3] 2012-09-18 10:06:52.925  RMI Error Vmomi.SessionManager.LoginBySSPI - 5
<Error type="VirtualInfrastructure.Exceptions.RequestTimedOut">
  <Message>The request failed because the remote server 'esxvc02' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)</Message>
  <InnerException type="System.Net.WebException">
    <Message>The command has timed out as the remote server is taking too long to respond.</Message>
    <Status>Timeout</Status>
  </InnerException>
  <Title>Connection Error</Title>
  <InvocationInfo type="VirtualInfrastructure.MethodInvocationInfoImpl">
    <StackTrace type="System.Diagnostics.StackTrace">
      <FrameCount>17</FrameCount>
    </StackTrace>
    <MethodName>Vmomi.SessionManager.LoginBySSPI</MethodName>
    <Target type="ManagedObject">SessionManager:SessionManager [esxvc02]</Target>
    <Args>
      <item></item>
      <item></item>
    </Args>
  </InvocationInfo>
  <WebExceptionStatus>Timeout</WebExceptionStatus>
  <SocketError>Success</SocketError>
</Error>
[viclient:Critical:M: 7] 2012-09-18 10:06:52.940  Connection State[esxvc02]: Disconnected
[viclient:SoapMsg :M: 7] 2012-09-18 10:06:52.940  Attempting graceful shutdown of service ...
[viclient:SoapMsg :M: 7] 2012-09-18 10:06:52.956  Pending Invocation Count: 0
[viclient:SoapMsg :M: 7] 2012-09-18 10:06:52.956  Graceful shutdown of service: Success
[        :Error   :M: 7] 2012-09-18 10:06:52.956  Error occured during login
VirtualInfrastructure.Exceptions.LoginError: The server 'esxvc02' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
   at VirtualInfrastructure.LoginMain.Process(BackgroundWorker worker, DoWorkEventArgs e)
   at VirtualInfrastructure.LoginWorkerImpl.Worker_DoWork(Object sender, DoWorkEventArgs e)
...
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server 'esxvc02' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
   at VirtualInfrastructure.Soap.SoapServiceWrapper.DoInvokeSync(ManagedObject mo, MethodName methodName, Object[] parameters, Int32 timeoutSecs)
   at VirtualInfrastructure.Soap.SoapTransport.VirtualInfrastructure.Transport.InvokeMethod(ManagedObject mo, MethodName methodName, Object[] pars)
   at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName methodName, Object[] pars)
   at Vmomi.SessionManager.LoginBySSPI(String base64Token, String locale)
   at VmomiSupport.VcServiceImpl.LoginBySSPI(LoginSpecInternal2 loginSpec)
   at VmomiSupport.VcServiceImpl.Login(LoginSpec loginSpec)
   at VirtualInfrastructure.LoginMain.Process(BackgroundWorker worker, DoWorkEventArgs e)
System.Net.WebException: The command has timed out as the remote server is taking too long to respond.

In my vpxd.log file I see at the same time:

2012-09-18T10:06:53.036+02:00 [11704 error 'SoapAdapter.HTTPService'] HTTP Transaction failed on stream TCPStreamWin32(socket=TCP(fd=16104) local=127.0.0.1:8085,  peer=127.0.0.1:59602) with error class Vmacore::SystemException(An established connection was aborted by the software in your host machine. )

Someone knows how to resolve this?

Thanks,

Bart

Hi,

we're monitoring our vSphere 5.1 environment with Nagios. Most of the checks (cpu, memory, hardware, etc.) are performed against the hosts and not through the vCenter. The checks use a local user "monagent" that has been created on each ESXi host.

Unfortunately these checks are filling up the Events list of the ESXi in our vCenter. Is there a way to suppress these entries?

#####################################################################################

User monagent@ logged out (login time: , number of API invocations: , user agent: )
info
13.12.2012 09:27:13
esxihost.domain.local
monagent

User monagent@IPAdress logged in as
info
13.12.2012 09:27:12
esxihost.domain.local
monagent

User monagent@ logged out (login time: , number of API invocations: , user agent: )
info
13.12.2012 09:27:03
esxihost.domain.local
monagent

User monagent@IPAdress logged in as
info
13.12.2012 09:27:03
esxihost.domain.local
monagent

User monagent@ logged out (login time: , number of API invocations: , user agent: )
info
13.12.2012 09:20:51
esxihost.domain.local
monagent

User monagent@IPAdress logged in as
info
13.12.2012 09:20:50
esxihost.domain.local
monagent

#####################################################################################

Any help appreciated...

Hello,

we update 2 vsphere 5.0 Hosts to 5.1 and the vcenter too. Now we connect new Storage to the vsphere Hosts and migrate some of the VMs on the new Store.

(all of them have latest VMtools installed, are the latest VM HW-Version, they have no ISO, Floppy-Images or something else attached) Cause of Vsphere Essential we made the Storage Migration when then VMs were offline.

After the successfull storage-migration of all VMs, we saw that 3 VMs show us under Resources of the VM the old and the new datastore, also on the inventory of the datastore we saw on both datastore the vm, but when we browse the datastore the VMS are only (correct) on the new datastore.

I know that happens if some iso, images etc. are connected when the VM ist migrated, but we checked that double an there is no reference to the old datastore at the settings of the VM. When we connect direct to the host the VM datastore is show us correct only the new datastore.

How can we fix this????

Best regards

Werner St.

hi guys

I have vCenter Appliance 5.1 U1a build 1123961

Active Directory W2012

I have this account for read-only access - controlit - . All of a sudden the person reported he was not able to log in error:

cannot complete login due to an incorrent username or password

Ok no problem I though maybe I forgot to disable account expiration or something. But no account is working I can log in using a Windows machine and I get into the domain using controlit

doing and testing I created: controlit1  and controlit2 same password all 3 accounts and guest what I am able to login using those two accounts to vCenter.

important all other existing accounts admin and read only are able to log in to vCenter

any idea what logs I can check in the vCenter login process?

Active Directory Logins are OK.

thanks a lot

Hi everyone

We had a scheduled maintenance window over the weekend while some work was carried out elsewhere in the building. As a precaution we shutdown the infrastructure that we we still keep onsite (the rest is in colo). So all we have is a 2 node ESXi cluster, managed by vCenter Server Appliance (Novell SUSE Linux Enterprise 11 64bit). It only has 6 VMs running on it as most of them have been migrated offsite.

This morning we started up the OpenFiler NFS storage box and the ESXi nodes. All VMs started ok, including the vCenter Server Appliance.

However I was unable to connect to the vCenter Appliance using vSphere Client. I could connect to the ESXi nodes directly without problems. DNS hostnames all resolve to the IP addresses without problems.

Looking at the vSphere Client logs I see the following message each time I tried to connect:

System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.10.0.205:443

So I connected to the vCenter Appliance over SSH and it looks like it's run out of disk space. Here's the df and mount output:

vlevcenter01:/ # df -h

Filesystem            Size  Used Avail Use% Mounted on

/dev/sda3             9.8G  9.8G     0 100% /

devtmpfs              4.0G  104K  4.0G   1% /dev

tmpfs                 4.0G  4.0K  4.0G   1% /dev/shm

/dev/sda1             130M   18M  105M  15% /boot

/dev/sdb1              20G  3.8G   15G  21% /storage/core

/dev/sdb2              20G  717M   18G   4% /storage/log

/dev/sdb3              20G   19G     0 100% /storage/db

vlevcenter01:/ # mount -l

/dev/sda3 on / type ext3 (rw,acl,user_xattr)

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

debugfs on /sys/kernel/debug type debugfs (rw)

devtmpfs on /dev type devtmpfs (rw,mode=0755)

tmpfs on /dev/shm type tmpfs (rw,mode=1777)

devpts on /dev/pts type devpts (rw,mode=0620,gid=5)

/dev/sda1 on /boot type ext3 (rw,acl,user_xattr)

/dev/sdb1 on /storage/core type ext3 (rw)

/dev/sdb2 on /storage/log type ext3 (rw)

/dev/sdb3 on /storage/db type ext3 (rw)

So the database and root partitions have run out of space. Looking in /var/log/localmesages:

Jul 15 10:10:51 vlevcenter01 startproc: startproc: Empty pid file /var/run/slapd/slapd.pid for /usr/lib/openldap/slapd
Jul 15 10:10:51 vlevcenter01 startproc: startproc:  exit status of parent of /usr/lib/openldap/slapd: 1
Jul 15 10:10:52 vlevcenter01 checkproc: checkproc: Empty pid file /var/run/slapd/slapd.pid for /usr/lib/openldap/slapd
It looks like it can't create the pid files for the services because there is no disk space.

We already have 60GB of vmdks allocated to this VM though we do have space on our datastore to add more. But I'm concerned that the vCenter Appliance will just grow and grow.

1) Is there any scheduled maintenance that runs on the vCenter Appliance to keep disk usage under control? This is what I would expect from an enterprise product, I'm very surprised to see such a problem happen.

2) Where should I start looking to clear some disk space so we can get the vCenter service back up and running?

I'd like to find a longer term solution to this otherwise we might have to just keep adding vmdks until our datastore runs out of space.

Cheers, B

I received a removable disk containing a large number of VMware guests.  These need to be added to our corporate vCenter (ver 5) inventory.  I can do that by using the vCenter browser to copy

the .VMDKs to our SAN.  Afterward I can right click each .vmdk and do a add to inventory.  Is there anything else I need to do, especially with the .vmx files or does the add create a new

.VMX for each .vmdk ?   Some of the guests may have multiple .vmdk files.  Thanks.