VMware Cloud Community
infosysvmware
Contributor
Contributor

What could be causing this -A problem occurred during RPM installation Return code=256 output ver VCSA 6.7?

pastedImage_0.png

Reply
0 Kudos
15 Replies
daphnissov
Immortal
Immortal

There could be several things, but as you've provided no other details at all it's impossible to know. Please show screenshots of your deployment process on VMware Workstation that contains the values you're providing to the wizard. Know that you must have A and PTR records created in local DNS for the hostname of vCSA *before* you begin deployment. If you do not have local DNS which can accommodate custom records, you cannot install vCSA.

Reply
0 Kudos
infosysvmware
Contributor
Contributor

Forward lookup zones sbm.local contains

VCSA01.SBM.local :192.168.0.13

ESX01.SBM.local :192.168.0.28

Except, I didn't have ptr enabled in the VCSA01.sbm.local. Could that be causing it?

Thanks,

Reply
0 Kudos
daphnissov
Immortal
Immortal

Yes, you need forward and reverse lookup records for the vCSA to find it self properly.

Reply
0 Kudos
infosysvmware
Contributor
Contributor

It's still coming up with the same error even when vCSA is in the forward and reverse lookup records.

Reply
0 Kudos
daphnissov
Immortal
Immortal

Please show screenshots of your entire installation process.

Reply
0 Kudos
infosysvmware
Contributor
Contributor

pastedImage_0.png

pastedImage_1.png

pastedImage_2.png

pastedImage_3.png

pastedImage_4.png

pastedImage_5.png

pastedImage_6.png

pastedImage_7.png

pastedImage_8.png

pastedImage_9.png

pastedImage_10.pngpastedImage_11.png

pastedImage_12.png

pastedImage_13.pngpastedImage_14.png

pastedImage_15.png

pastedImage_16.png

pastedImage_17.png

pastedImage_18.png

pastedImage_19.png

Reply
0 Kudos
daphnissov
Immortal
Immortal

Ok, this is helpful. It looks like you might not have communication from the network you're presenting to your nested ESXi host to your DC. But, in the first place, why are you deploying vCSA to an ESXi host which is nested inside Workstation? Did you know that you can deploy directly to VMware Workstation and it supports the OVA properties? If you haven't enabled promiscuous mode inside your ESXi host, this might be the cause. That said, you'd probably see better performance if you deploy it directly to Workstation and skip a second layer of virtualization overhead.

Reply
0 Kudos
infosysvmware
Contributor
Contributor

Thank you.

I've installed the vsca 6.7 (esxi) using the installer its iP:192.168.0.19. When I'm trying to access it through web client

A server error occurred.

Unable to login because you do not have permission on any vCenter Server systems connected to this client.

Check the vSphere Web Client server logs for details.

When I'm trying to install the VCSA 6.7 in a virtual machine WINDOWS 2012 SERVER STD it comes with

pastedImage_2.png

Reply
0 Kudos
daphnissov
Immortal
Immortal

Need clarification. You said you've deployed an ESXi host on 6.7 and now you're trying to install the vCSA 6.7 on top of that ESXi host? Is that correct?

Reply
0 Kudos
infosysvmware
Contributor
Contributor

I think so. How do I get access to the esxi host to configure the vm and so forth? Correct me if I'm wrong. As to my understanding you install an esxi host and to configure it you install vCenter Server or VCSA 6.7 ?

Thanks,

Reply
0 Kudos
daphnissov
Immortal
Immortal

But if you're already running Workstation 14, you don't strictly *need* to deploy vCSA into a nested ESXi host. You can deploy as a VM to Workstation directly. This is not only simpler but more performant.

Reply
0 Kudos
infosysvmware
Contributor
Contributor

How do I deploy vCSA as a VM to workstation directly? My pc has 8.1 and I've created  a VM with 2012 server to install the vCSA, and it's coming up with an error. The host is locked down. Permission to perform this operation was denied.

Reply
0 Kudos
daphnissov
Immortal
Immortal

Reply
0 Kudos
infosysvmware
Contributor
Contributor

Thank you.

Reply
0 Kudos
francotiale
Contributor
Contributor

I was able to install the vcenter after have done few changes in my own computer.

I had to set the dns server of my physical computer to point to a DNS server created in the VMware Workstation.

I created two entries in this DNS one for the ESX host that will host the vcenter machines and other that is pointing to the vcenter machines that will be created.

 

Reply
0 Kudos