Hi,
after restart of the VCSA I can`t connect with the vc-client to the VCSA. When I connet over the GUI, I have no entries in the vCenter Server, Services and Authentication window. Only in the Network, System and Update window are entries.
What could be the reason or witch logfile I could check?
Best Regards
Bernd
Hi ,
can't connect to internal DB after hard reboot to VC ,
can't login any more to vcenter unless root , but all my database deleted no HOST / cluster exist .
i try to reboot many services like vmware-vpxd , vmware-inventoryservice , and data store service without any benefit ...
VPX log file :
-->
2013-10-27T15:24:07.513Z [7FDC2CB6D740 info 'utilvpxdVdb'] Registry Item DB 5 value is ''
2013-10-27T15:24:07.513Z [7FDC2CB6D740 info 'utilvpxdVdb'] [VpxdVdb::SetDBType] Logging in to DSN: VMware VirtualCenter with username vc
2013-10-27T15:24:07.666Z [7FDC2CB6D740 warning 'Default'] [Vdb::LockRepositoryHelper] Failed to get exclusive lock: P0001:7:ODBC error: (P0001) - ERROR: Failed Lock
--> Failed to exclusively lock vCenter Repository!!;
--> Error while executing the query
2013-10-27T15:26:37.669Z [7FDC2CB6D740 error 'Default'] Unable to get exclusive access to vCenter repository. Please check if another vCenter instance is running against the same database schema.
2013-10-27T15:26:37.669Z [7FDC2CB6D740 error 'vpxdvpxdDaemon'] Unhandled exception <Error[VdbError] (-24) Vdb instance is not initialized or terminated>
can anybody help me , I am facing some problem related to v center server 5.5 connectivity . we are using esxi 5.5 and on this esxi5.5 we are running VM . On this single vm we have installed v center server , single sign on , inventory services (without any error) . when I am trying to connect vcenter server through v center client one error occurred vsphere client could not connect to ip add .you don't have a permission to login to the server ip.
We are reconfiguring and redesigning our virtual infrastructure and got a problem about security issues in the SSO installation of vcenter 5.1.
First of all we are using oracle databases with several schemata on each of them. We are using vCenter 5.0 U1 until today, therefore we didn´t get in contact with this special feature of SSO before.
We have prepared the three schemata for the new vcenter 5.1 installation as mentionned in the "Install and Upgrade guide", but, as we were using several other productive schemata on the same database, we granted the user privileges not to the whole database, but only to the schema RSA.
To our suprise we weren´t able to install the vCenter Single Sign On Service, because we have " sufficient privileges" for the user RSA_DBA in concern. Several installation tries after the first one, we granted the RSA_DBA the "privileges" to the whole oracle database, and we could install the service.
Up to now we have a logistic problem, because of several orders in our enterprise we are not allowed to install with full rights to the oracle database, because afterwards the user RSA_DBA is able to delete all schematas of the database.
Therefore my questions:
Has someone in the community managed to install the RSA as Oracle schema with only the privileges to the schema and not the whole database?
Is it possible to change the setup to bypass the privileges?
I migrated my databases to a new SQL server successfully. I am now recreating the SQL jobs per article 2006097. All worked except for the following:
I am getting error:
Msg 208, Level 16, State 1, Line 36 (lines very depending on the job)
Invalid object name 'vpx_job_log'.
Thoughts?
Hi all,
I recently upgrade my vcenter from v4.1 to v5.1. Now, I am trying to install the Syslog collector (vCenter integrated), but keep on getting : Error 29456: vCenter Extension could not be found. How can something this simple cause such a headache?
I can install it as a standalone, but have tried many different ways to deploy it, but no luck. What am I doing wrong?
Anyone have any ideas?
When I was building a vSphere 5.1 environment. The prevailing recommendation seemed to be to install SSO and vCenter on seperate servers. Some recommendations were based on environment size while other physical seperation seemed based more on seperating this young, essentially v1.0 product from the other core vCenter services. As I look at planning a new vSphere 5.5 environment I am seeing slightly different recommendations. Most seem to suggest keeping vCenter and SSO on the same VM. I wanted to make sure this is now the prevailing wisdom and what (if any) types of environments would seperation still be preferred. I'm looking for the appropriate architecture for this environment. A couple vCenters instances, 100 Hosts, 2000-3000 VMs.
We are using a“Route based on the originating virtual switch port ID” LB policy with "failback" and "link status" failover detection. We had an outage recently where a planned switch reboot turned into a switch replacement. Had I known about the switch replacement plans, I would have prepared the Host by removing those pNICs from the teams while the switch was being configured. Instead, the switch was replaced, the team detected a link, and some VMs began to move back to the yet unconfigured switch as expected.
My question is about "link status" failover detection with respect to disabled switch ports. In this case, the switch was brought up with all ports enabled. I wondered how the team would have reacted if they were brought up disabled. Will link status failback to a disabled port or does it treat a disabled port as down.
Hi folks, forgive me if this is the wrong place.
We are running vCenter Server 5 Essentials with three hosts all running ESXi 5.0.0, 504890. I attempted to install a VM with the guest operating system Windows 2012 Server, however I learned it will not install and repeats itself rebooting over and over again. Anyways after some googling I learned I needed a patch to allow Server 2012 to be a guest O/S however I don't have update manager installed on my VCenter Server (which is virtualized 2008 R2 Server).
So I proceeded to download the VMware vCenter Installer (Version 5.0) onto my VCenter server and attempted to install update manager, however I get this error message
"The vCenter Server is incompatible with the VMware vSphere Update Manager you are installing. Please selection a compatible vCenter Server."
At first I was mistakenly using version 5.5 Installer and getting the error. However I went back and downloaded the correct version (5.0) to match my environment and I still get the same error. Then I read briefly that you cannot use update manager on vCenter virtualized server. So I tried using another virtual server but still receive the same error message.
Any info to shed some light or point me in the right direction would be greatly appreciated. I thank you in advice for your time and help!
Message was edited by: Cbaur88 Version of VMware Installer I downloaded and tried 5.0.0-1343691 my version is 5.0.0-504890 did I just answer my own question? Do I need to physically update those three hosts with a newer build and or version of ESxi? Thanks!
Hi,
I've just upgraded my VirtualCenter to U3, and I have noticed that my Map Relationships are now blank for all clusters/hosts etc?
Anyone know what's going on?
Thanks
Mike
I upgraded my vCenter to 5.5 from 5.1 and it works except the Web Client has incorrect inventory data. It is missing some VMs and has some ghost VMs that don't actually exist. There aren't any error messages that suggest the server is malfunctioning. The really strange thing is that when I connect with the vSphere Client on Windows, everything is correct there. Also Veeam shows all the correct inventory when it connects to the vCenter server. So its only the Web Client that is wrong. Has anyone experienced this or have any ideas on how to force the Web Client to refresh?
edit: forgot to mention this is VCSA
My map relationships are blank for everything (data centers/clusters/hosts/VMs ect). There is an error report and a screenshot of the error attached. They are from storage views maps. I'm on version 5.1. Any help will be appreciated!
Hello everyone,
I'm having an issue with templates. I created a Windows Server 2008 VM and then I converted it to a template. From there, I deployed a VM and customized it to have the proper hostname, IP, etc. Everything looks and performs great. I wanted to head back into the template in order to add some more applications, but when I attempted to start it (after converting it back to a VM) it yelled at me "Cannot open the disk '/vmfs/volumes/51142c9e-d2ce05cd-fc00-3085a9a227c3/New WinServer 08 Template/New WinServer 08 Template.vmdk' or one of the snapshot disks it depends on.".
This is because the VM I deployed from it is running and for some reason it is using the same vmdk. Why and how would this occur? If I browse the datastore, I can see that the new VM has its own vmdk file, so why is it using the template?
I have also tried to remove that VM from my inventory and then readding it to the inventory via its vmx file and I run into the same situation.
Any help would be great, thanks!
I have a number of hypervisors running with the vSphere Essentials license. I set up a VC server in trial license mode and added all these hosts. Once I purchase and apply the VC server license, and VC is not in trial mode anymore, will the Essentials hosts still be able to remain connected? I have heard conflicting answers. Logically, it should work since there is only one license level for VC server in this case, so there are no additional features that I might lose when I apply a license and take it out of trial. If anyone has a _licensed_ working VC environment, I can provide an Essentials hypervisor license key for testing.
I am having some issue deploying a VM from template with guest customization. I have not been able to find any answers on the web.
Here is my setup:
vSphere 5.1.0
Build 1064983
1) Create a VM (WIN2K8R2) based on Windows Server 2008 R2 with Administrator password as P@ssw0rd
2) Install VMware Tools
3) Activate Windows
4) Shutdown VM (WIN2K8R2)
5) Clone VM (WIN2K8R2) to a template (WIN2K8R2T1)
6) Deploy a VM (WIN2K8R2T1S1) from template (WIN2K8R2T1) with Guest Customization Spec
7) VM (WIN2K8R2T1S1) successfully created from template (WIN2K8R2T1)
- Issue is, if i don't set "Automatically Logon as Administrator" in the Guest Customization Spec, i cannot logon to windows.
- If I set "Automatically Logon as Administrator", the VM automatically logon, but if i log-off, i cannot logon
- If I set "Automatically Logon as Administrator", the VM somehow removes the "Administrator" password. And if I go to "Edit Local Users", i get option "Set New Password" for the Administrator user. Once I set a new password, then i can use the new password to logon.
- I also see that the Windows is no longer activated.
- If i specify domain credentials in the customization spec for the VM to be joined to a domain, it does not join it.
- it looks like the guest customization is not really working?
Any idea what is going on here? I have been able to reproduce this with Windows Server 2008 R2 and Windows Server 2012.
Hi,
I'm trying to make VDP work in my env.
I installed and configured it - but after restart there were no VDP visible in vSphere Web Client.
So I unregistered VDP extension, restarted VDP and Web Client - and I could see VDP option in vSphere Web Client.
But now I've got message : "The most recent request has been rejected by the VDP appliance" with additional info about wrong time zones.
I've checked it - on vCenter and VDP the same time zone is set - so this is probably not the issue.
I looked over VDP logs - but there is no information about rejecting anything.
Has anybody such problem?
Regards
Jarek
I’m having a problem with updating VCenter 5.1 to 5.1 update 1.
I downloaded the ISO then mounted it on the VCenter server at our D/R site (it’s not gone “live” yet, so it makes a good test).
I opened up the disk, then started with the SSO install. I went through the opening screens, entered the master password, etc. It then got to the “copying files” screen. It then popped up a dialog to “insert disk 1” with the option to “retry” or “cancel”. After retrying a couple of times, I hit “cancel” it then “backed out”.
I did some searching and found an article where that error showed up if you were doing an upgrade on a VCenter system that had originally been installed by using the files on the drive, but were using an ISO/DVD for the upgrade. I copied the files from the DVD to a folder on the hard drive and was going to restart the install. However, the update would fail before it got to the copying files section. The install log seemed to indicate the directory rename was failing.
Also, after that, the SSO service wouldn’t restart, it was giving me file not found type errors. Looking at the VMWare “program files” folders, I found that the install had started renaming various directories, adding a hex number to the end of certain folders.
I removed the hex string from the folders and was able to start the SSO service. However, when I try to start the VCenter server service, it fails with an error 2.
I’ve tried rebooting, but no luck; it still won’t start the VCenter service.
Fortunately, this site isn’t active yet, so there’s not much to lose if I have to reinstall. I also have backups of the SQL database, although since the SQL system wasn’t affected, if I do a re-install it should find the database files.
Any comments or suggestions would be appreciated.
Hi, All.
We have a SATA FC LUN, presented to 3 x ESX 4.1 hosts and 1 x ESXi 4.1 host (all fully patched) from an IBM DS4800 SAN. We wanted to provision some new test VMs and noticed that the provisioned space didn't add up the total of the VMs (see attached images):
The 'Performance' view is the most revealing. It shows 266GB of 'other' data on the datastore; the question is, what is it?
Querying the datastore via the vSphere Client, ESX console and PowerCLI reveals nothing. The totals match with the total of the provisioned VMs.
Any ideas what this could be? There are no snapshots, or large data dumps (ISOs etc) on the datastore as far as I can see.
Thanks,
Carl
We have an authentication issue with our vCenter server (SSO) 5.5 and our Windows 2008 active directory. When we try to login with some AD services account we have this error message : Cannot parse subject.
Presently the user has access to vCenter from a group, we try to give the permission directly to the user and this does not work either. Same error message.
Most of our account in this AD works well.
Any idea?
Thanks in advance for your help!
Running the free Vsphere esxi 5.5 when i connect to get the client it tells me I ought use the web client if i select the link 'Download VMware vCenter' i end up on a most confusing page with literally dozen of options.
When I looked for documents i find several that start by saying things like the quote below. But can not find one that says this is the installer and this is how you get it. OR this is a link to the installer.
Is this pointless? Is it related to the free version?? should I just use the client since we have no license nor any $$ to purchase a license??
"
Install and Start the vSphere Web Client
The vSphere Web Client enables you to connect to a vCenter Server system to manage an ESXi host through a browser.
Prerequisites
■ |
"