Highlighted
Contributor
Contributor

vCenter deployment error

Jump to solution

Hello,

I am trying to deploy the vcenter 6.7 ISO to my esxi1 lab hypervisor.

However during deployment at 80% i am getting this error:

Capture.JPG

2018-12-29T12:33:27.908+01:00 verbose OVFTool[03768] [Originator@6876 sub=Default] Closing writer. Locator: https://esxi1.labor.local:443/ha-nfc/52b3776c-afa6-677f-8483-093452f5d7db/disk-1.vmdk (Written bytes: 1979236352)

2018-12-29T12:33:27.908+01:00 verbose OVFTool[03768] [Originator@6876 sub=Default] Upload disk do no convert done

2018-12-29T12:33:27.908+01:00 verbose OVFTool[03768] [Originator@6876 sub=Default] Curl session torn down

2018-12-29T12:33:27.908+01:00 verbose OVFTool[03768] [Originator@6876 sub=Default] Locator: VMware-vCenter-Server-Appliance-6.7.0.14000-9451876_OVF10-disk2.vmdk, expected digest: 50699bccc15449fe188f802ad3791e45639fa317

2018-12-29T12:33:27.908+01:00 verbose OVFTool[03768] [Originator@6876 sub=Default] Got digest from reader factory: locator = VMware-vCenter-Server-Appliance-6.7.0.14000-9451876_OVF10-disk2.vmdk, digest = 0506e086b2d81416022a5f4747c5a2f8eff40f1f

2018-12-29T12:33:27.924+01:00 verbose OVFTool[05656] [Originator@6876 sub=Default] Exception thrown: class boost::exception_detail::clone_impl<struct boost::exception_detail::error_info_injector<class OvfToolException> >(SHA digest of file VMware-vCenter-Server-Appliance-6.7.0.14000-9451876_OVF10-disk2.vmdk does not match manifest)

--> [context]zKq7AUsEAQAAAHxHeQART1ZGVG9vbAAAoxYadm1hY29yZS5kbGwAADlrBQArjwUAPRUCAUMUAW92ZnRvb2wuZXhlAAF0NwwBJlAQAcl/BQE6nwUBJKIFANYfFwBXOhcAW3QbAl/aA3VjcnRiYXNlLmRsbAADxGIBS0VSTkVMMzIuRExMAARpHwZudGRsbC5kbGwABDQfBg==[/context]

2018-12-29T12:33:27.940+01:00 verbose OVFTool[05656] [Originator@6876 sub=Default] Backtrace:

--> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-7948156, tag: OVFTool, cpu: x86, os: windows, buildType: release

--> backtrace[00] vmacore.dll[0x001A16A3]

--> backtrace[01] vmacore.dll[0x00056B39]

--> backtrace[02] vmacore.dll[0x00058F2B]

--> backtrace[03] vmacore.dll[0x0002153D]

--> backtrace[04] ovftool.exe[0x00011443]

--> backtrace[05] ovftool.exe[0x000C3774]

--> backtrace[06] ovftool.exe[0x00105026]

--> backtrace[07] ovftool.exe[0x00057FC9]

--> backtrace[08] ovftool.exe[0x00059F3A]

--> backtrace[09] ovftool.exe[0x0005A224]

--> backtrace[10] vmacore.dll[0x00171FD6]

--> backtrace[11] vmacore.dll[0x00173A57]

--> backtrace[12] vmacore.dll[0x001B745B]

--> backtrace[13] ucrtbase.dll[0x0003DA5F]

--> backtrace[14] KERNEL32.DLL[0x000162C4]

--> backtrace[15] ntdll.dll[0x00061F69]

--> backtrace[16] ntdll.dll[0x00061F34]

--> [backtrace end]

2018-12-29T12:33:27.940+01:00 verbose OVFTool[05656] [Originator@6876 sub=Default] [Vi4Target::Abort] started.

2018-12-29T12:33:28.143+01:00 trivia OVFTool[05052] [Originator@6876 sub=HttpConnectionPool-000000] [PopPendingConnection] No pending connections to <cs p:018444f8, TCP:esxi1.labor.local:443>

2018-12-29T12:33:30.221+01:00 trivia OVFTool[05656] [Originator@6876 sub=HttpConnectionPool-000000] [PopPendingConnection] No pending connections to <cs p:018444f8, TCP:esxi1.labor.local:443>

2018-12-29T12:33:30.221+01:00 verbose OVFTool[05656] [Originator@6876 sub=Default] [Vi4Target::Abort] HttpNfcLease->Abort() is called.

2018-12-29T12:33:30.221+01:00 trivia OVFTool[05656] [Originator@6876 sub=HttpConnectionPool-000000] [PopPendingConnection] No pending connections to <cs p:018444f8, TCP:esxi1.labor.local:443>

2018-12-29T12:33:30.221+01:00 trivia OVFTool[05656] [Originator@6876 sub=HttpConnectionPool-000000] [PopPendingConnection] No pending connections to <cs p:018444f8, TCP:esxi1.labor.local:443>

2018-12-29T12:33:30.221+01:00 trivia OVFTool[05656] [Originator@6876 sub=HttpConnectionPool-000000] [PopPendingConnection] No pending connections to <cs p:018444f8, TCP:esxi1.labor.local:443>

2018-12-29T12:33:30.221+01:00 trivia OVFTool[05656] [Originator@6876 sub=HttpConnectionPool-000000] [PopPendingConnection] No pending connections to <cs p:018444f8, TCP:esxi1.labor.local:443>

2018-12-29T12:33:30.221+01:00 trivia OVFTool[05656] [Originator@6876 sub=HttpConnectionPool-000000] [PopPendingConnection] No pending connections to <cs p:018444f8, TCP:esxi1.labor.local:443>

2018-12-29T12:33:30.221+01:00 verbose OVFTool[05656] [Originator@6876 sub=Default] [Vi4Target::WaitForEntityDestroyDone] The entity 'VMware vCenter Server Appliance' is gone or even not created yet.

2018-12-29T12:33:30.236+01:00 verbose OVFTool[05656] [Originator@6876 sub=Default] Destruction of ViTarget

Any ideas why?

Windows Server 2016, and have cleared the ...appdata\Temp\ folder

Thank you

Kind regards

Norbert

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Immortal
Immortal

Here are the file hashes. Verify that your file is complete.

MD5SUM: 0fd4bd9a2e37393f69c716e9397059c3

SHA1SUM: 9c30c265ed584b1626e6e44e137d2e11d6dbfb82

SHA256SUM: 7f3437b1c661b2a83effb39d9afc23d2bd152937b8995f6becad09afb0a4da87

View solution in original post

0 Kudos
13 Replies
Highlighted
Immortal
Immortal

Please show screenshots of the installation steps and more importantly the values you're providing the wizard.

0 Kudos
Highlighted
User Moderator
User Moderator

Did you already verify the installation image's checksum to ensure that it is genuine?

André

0 Kudos
Highlighted
Contributor
Contributor

Okay, well this is the summary:

Capture2.JPG

Since my post, I have redeployed the hypervisor itself to exclude some left over config data from there and then tried again but the same happens.

What I can think of is that the iso damaged maybe… it is on the server 2016 desktop which is also virtualized.

0 Kudos
Highlighted
Immortal
Immortal

Re-download and check the checksum against what is published on the MyVMware site.

0 Kudos
Highlighted
Contributor
Contributor

Unfortunately my evaulation is ended so myvmware is not offering me to download the iso again or to download the newer U1 version. Seems like game over here.

0 Kudos
Highlighted
Enthusiast
Enthusiast

Please refer below link. May be the ISO is not properly downloaded.

VMware Knowledge Base

Thanks

Jahid Khan

0 Kudos
Highlighted
Immortal
Immortal

What is the exact file name of this ISO you have? I can paste in the checksums for you to verify on your end.

0 Kudos
Highlighted
Immortal
Immortal

LUCKY1011​ this has nothing whatsoever to do with OP's issue. The KB you referenced has to do with VIC and not vCenter.

0 Kudos
Highlighted
Contributor
Contributor

Hi,

The iso name is VMware-VCSA-all-6.7.0-9451876.ISO

Thank you!

0 Kudos
Highlighted
Immortal
Immortal

Here are the file hashes. Verify that your file is complete.

MD5SUM: 0fd4bd9a2e37393f69c716e9397059c3

SHA1SUM: 9c30c265ed584b1626e6e44e137d2e11d6dbfb82

SHA256SUM: 7f3437b1c661b2a83effb39d9afc23d2bd152937b8995f6becad09afb0a4da87

View solution in original post

0 Kudos
Highlighted
Contributor
Contributor

seems like this is the problem...

it differs from yours

Capture3.JPG

0 Kudos
Highlighted
Immortal
Immortal

Ok, so you've got a partial download. Not sure what to suggest other than a re-download which, if you are no longer entitled, seems like that's it since we can't share those files with you openly.

0 Kudos
Highlighted
Contributor
Contributor

very strange because i deployed this 2 weeks ago approximately without issues.

I was doing the cbtnuggets lab practices. but yesterday the vcenter went into an infinite reboot loop with the security audit service, so I deleted it from the hypervisor and thought of redeploying it.

And then now I see the iso is corrupted as well. maybe the new 860 EVO Samsung ssd cannot keep up with the 3 hyperv + server 2016 and starting to make mistakes.

Too much to troubleshoot Smiley Happy Thank you for the help anyway.

0 Kudos