gooseandbull's Posts

We experienced the same issues at our site. Copilot stated we need to upgrade so they sent technicians onsite to prepare and execute the SAN OS firmware upgrade to 6.7.4. No one from Dell onsite ... See more...
We experienced the same issues at our site. Copilot stated we need to upgrade so they sent technicians onsite to prepare and execute the SAN OS firmware upgrade to 6.7.4. No one from Dell onsite bothered to check release notes nor any best practice updates about the significant changes from 6.6 or later now mentioned throughout their best practices for vsphere 5.x and 6.x. we spent almost 2 weeks trying to diagnose why a rebooted host would no longer communicate with datastores and a very lengthy boot time trying to discover LUNs witje the wrong prescribed multipathing commands. So frustrating. Phone support took almost 2 weeks prior to finally suggesting the ALUA and RR changes. Glad to know we were not the only victims of such casual tomfoolery by support and faulty documentation.
I am having a very strange issue that I cannot seem to resolve. Current System: Running VCSA 5.5 Future system Windows vCenter 5.5 Right now I have a environment that is running the vC... See more...
I am having a very strange issue that I cannot seem to resolve. Current System: Running VCSA 5.5 Future system Windows vCenter 5.5 Right now I have a environment that is running the vCenter Appliance. Due to growth in the system and the overly priced Oracle suite, it has been decided that we will move to the windows install of vCenter. No matter the version of windows I try to install vCenter on (2008 R2 and 2012 R2) it always fails out at the same point (VMwareVCMSDS failed: AD LDS setup did not complete because one or more LDIF files could not be imported). I am running the install as a Service Account which has full access to the SQL server and is a Domain Administrator. I am starting to believe the issue might be the Fact that I already have a vCenter 5.5 running in the environment, but I cannot confirm. Has anyone else ran into this and found a solution? First, take a look at this KB article and let me know if helps: VMware KB: Upgrading or Installing vCenter Server 4.x (or later) fails with the error: Setup cannot create vCenter S… The errors that is shows are not present in the Jointool log or the status log. Below is the actual log file: [2014-08-04 13:59:09,906  com.vmware.vim.jointool] Failed to find instance config at: "C:\ProgramData\VMware\VMware VirtualCenter\instance.cfg", assuming defaults [2014-08-04 13:59:09,908  com.vmware.vim.jointool] Storage directory not found in instance.cfg. [2014-08-04 13:59:10,051  com.vmware.vim.jointool] Initializing DB datasource from: vcdb with dsn: VCDB as user: [2014-08-04 13:59:10,057  com.vmware.vim.common.vdb.VdbConfig] Config name=vcdb [2014-08-04 13:59:10,057  com.vmware.vim.common.vdb.VdbConfig] Property file=C:\ProgramData\VMware\VMware VirtualCenter\vcdb.properties [2014-08-04 13:59:10,058  com.vmware.vim.common.vdb.VdbConfig] Loaded url from props=jdbc:sqlserver://SVDBM12R01.cloud.abl.navy.mil;databaseName=VCDB;integratedSecurity=true [2014-08-04 13:59:10,058  com.vmware.vim.common.vdb.VdbConfig] Overrides= [2014-08-04 13:59:10,058  com.vmware.vim.common.vdb.VdbConfig]  prop:password [2014-08-04 13:59:10,058  com.vmware.vim.common.vdb.VdbConfig]  prop:dsn [2014-08-04 13:59:10,058  com.vmware.vim.common.vdb.VdbConfig]  prop:username [2014-08-04 13:59:10,252  com.vmware.vim.jointool] DB datasource initialized. [2014-08-04 13:59:10,252  com.vmware.vim.jointool] JoinTool started [2014-08-04 13:59:10,253  com.vmware.vim.jointool] Storage directory for LDAP instance: C:\ProgramData\VMware\VMware VirtualCenter\\VMwareVCMSDS [2014-08-04 13:59:10,254  com.vmware.vim.jointool] Operation Mode: initialize [2014-08-04 13:59:10,271  com.vmware.vim.jointool] Creating directory services instance VMwareVCMSDS [2014-08-04 13:59:10,272  com.vmware.vim.jointool]   LDAP port = 389 [2014-08-04 13:59:10,272  com.vmware.vim.jointool]   Base DN = dc=virtualcenter,dc=vmware,dc=int [2014-08-04 13:59:10,272  com.vmware.vim.jointool]   Storage dir = C:\ProgramData\VMware\VMware VirtualCenter\VMwareVCMSDS [2014-08-04 13:59:42,429  com.vmware.vim.jointool] Operation "Create standalone instance VMwareVCMSDS" failed: : Action: Create Standalone Instance Action: Creation of standalone instance Action: Create Instance Problem: Creation of instance VMwareVCMSDS failed: AD LDS Setup did not complete because one or more LDIF files could not be imported successfully. [2014-08-04 13:59:42,430  com.vmware.vim.jointool] Recovering from failed Operation "Create standalone instance VMwareVCMSDS" [2014-08-04 13:59:42,430  com.vmware.vim.jointool] Recovery successful [2014-08-04 13:59:42,432  com.vmware.vim.jointool] Execution error. Have you found a solution for this issue? I am running in to the same problem. I believe it is a security setting or policy that is causing the issue. After days of attempting to find an solution, I've discovered what was preventing the LDIF importing for me. Ensure the following registry setting is set: Key: HKCU\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing Value: State Type: REG_DWORD Data: 0x00023c00 Our security policy mandates made us set this to 0x00010000 which was causing the failed import issues. j_pickj_pickHey j_pick, Did you ever find a solution to this problem? I am having the same problem. We are installing vCenter 5.5 U2 over W2K8 R2 and the DB is running on SQL 2014 x64 Standard (installed locally). Here the log [2015-03-18 19:29:45,389  com.vmware.vim.jointool] Failed to find instance config at: "C:\ProgramData\VMware\VMware VirtualCenter\instance.cfg", assuming defaults [2015-03-18 19:29:45,396  com.vmware.vim.jointool] Storage directory not found in instance.cfg. [2015-03-18 19:29:46,052  com.vmware.vim.jointool] Initializing DB datasource from: vcdb with dsn: VCenter as user: vpxuser [2015-03-18 19:29:46,073  com.vmware.vim.common.vdb.VdbConfig] Config name=vcdb [2015-03-18 19:29:46,074  com.vmware.vim.common.vdb.VdbConfig] Property file=C:\ProgramData\VMware\VMware VirtualCenter\vcdb.properties [2015-03-18 19:29:46,074  com.vmware.vim.common.vdb.VdbConfig] Loaded url from props=jdbc:sqlserver://VCENTER1;databaseName=VCDB [2015-03-18 19:29:46,075  com.vmware.vim.common.vdb.VdbConfig] Overrides= [2015-03-18 19:29:46,075  com.vmware.vim.common.vdb.VdbConfig]  prop:password [2015-03-18 19:29:46,076  com.vmware.vim.common.vdb.VdbConfig]  prop:dsn [2015-03-18 19:29:46,076  com.vmware.vim.common.vdb.VdbConfig]  prop:username [2015-03-18 19:29:46,708  com.vmware.vim.jointool] DB datasource initialized. [2015-03-18 19:29:46,708  com.vmware.vim.jointool] JoinTool started [2015-03-18 19:29:46,710  com.vmware.vim.jointool] Storage directory for LDAP instance: C:\ProgramData\VMware\VMware VirtualCenter\\VMwareVCMSDS [2015-03-18 19:29:46,713  com.vmware.vim.jointool] Operation Mode: initialize [2015-03-18 19:29:46,767  com.vmware.vim.jointool] Creating directory services instance VMwareVCMSDS [2015-03-18 19:29:46,768  com.vmware.vim.jointool]   LDAP port = 389 [2015-03-18 19:29:46,768  com.vmware.vim.jointool]   Base DN = dc=virtualcenter,dc=vmware,dc=int [2015-03-18 19:29:46,769  com.vmware.vim.jointool]   Storage dir = C:\ProgramData\VMware\VMware VirtualCenter\VMwareVCMSDS [2015-03-18 19:30:06,227  com.vmware.vim.jointool] Operation "Create standalone instance VMwareVCMSDS" failed: : Action: Create Standalone Instance Action: Creation of standalone instance Action: Create Instance Problem: Creation of instance VMwareVCMSDS failed: AD LDS Setup did not complete because one or more LDIF files could not be imported successfully. [2015-03-18 19:30:06,229  com.vmware.vim.jointool] Recovering from failed Operation "Create standalone instance VMwareVCMSDS" [2015-03-18 19:30:06,231  com.vmware.vim.jointool] Recovery successful [2015-03-18 19:30:06,236  com.vmware.vim.jointool] Execution error. Creation of instance VMwareVCMSDS failed: AD LDS Setup did not complete because one or more LDIF files could not be imported successfully. so.. any suggestion? This did it for me.  Not sure how you found this one but good find! This document was generated from the following discussion: Installing Windows vCenter 5.5 along side a VCSA 5.5 install