VMware Cloud Community
glousteau
Enthusiast
Enthusiast

unfortunately we hit an error that we weren't expecting

Newbee here,

I'm tinkering with VMWare 6.5 and have ESXi up and running.  I keep getting this error "unfortunately we hit an error that we weren't expecting" when I try to created a new datastore.  I cant' find a resolution and am therefor halted in my progress of building a few VMs.

Any ideas on how to solve?

thanks

Reply
0 Kudos
18 Replies
daphnissov
Immortal
Immortal

What version of the host client are you using? If it's stand-alone ESXi, it would be best to update the host client via the latest fling available here. You can use the Update functionality built into the client and point it at the published latest VIB for even easier updating:  http://download3.vmware.com/software/vmw-tools/esxui/esxui-signed-latest.vib

Reply
0 Kudos
Finikiez
Champion
Champion

Can you post vmkernel.log from your host and provide timestamp when you got the error?

Can you also describe a bit more abour what storage you use and how it's connected to your host?

Reply
0 Kudos
glousteau
Enthusiast
Enthusiast

I'm using the webui as my older Vsphere client from a 5.0 server will NOT connect.

I'm not following your question if my answer doesn't make sense?

Reply
0 Kudos
daphnissov
Immortal
Immortal

Update the host client using the process I mentioned and try your operation again.

Reply
0 Kudos
glousteau
Enthusiast
Enthusiast

ok, can you point me how to update my host?  I'm reading the link, but it doesn't tell me how to perform the update?

Reply
0 Kudos
daphnissov
Immortal
Immortal

Reply
0 Kudos
glousteau
Enthusiast
Enthusiast

Applied the update and tried again, same error (pasted below)

This is a 3TB SATA drive, nothing complicated imho Smiley Happy

Cause: TypeError: Cannot read property 'index' of null

Version: 1.21.0

Build: 5724747

ESXi: 6.5.0

Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Exception stack:

TypeError: Cannot read property 'index' of null

  at $scope.wizardOptions.currentPage.onCommit (https://192.168.1.10/ui/scripts/main.js:359:13125)

  at onCommit (https://192.168.1.10/ui/scripts/main.js:462:3976)

  at Object.onNextClick (https://192.168.1.10/ui/scripts/main.js:462:4168)

  at b.$scope.onNextClick (https://192.168.1.10/ui/scripts/main.js:462:7155)

  at https://192.168.1.10/ui/scripts/main.js:321:23160

  at https://192.168.1.10/ui/scripts/main.js:428:24773

  at b.$eval (https://192.168.1.10/ui/scripts/main.js:320:17497)

  at b.$apply (https://192.168.1.10/ui/scripts/main.js:320:17723)

  at HTMLButtonElement.<anonymous> (https://192.168.1.10/ui/scripts/main.js:428:24755)

  at HTMLButtonElement.dispatch (https://192.168.1.10/ui/scripts/main.js:317:14464)

Reply
0 Kudos
daphnissov
Immortal
Immortal

The latest version is 1.23. Click on About and make sure it reports that version.

Reply
0 Kudos
glousteau
Enthusiast
Enthusiast

its still showing 1.21.0

I'm getting this from Help, about, Client Version

Its like the update isn't taking??

1.21.0

5724747

6.5.0

5969303

Reply
0 Kudos
daphnissov
Immortal
Immortal

Use the offline package instead, upload to the host, and upgrade that way.

Reply
0 Kudos
glousteau
Enthusiast
Enthusiast

i put it on my boot datastore, but how do I point the ui to that directory? it wants a http or https link, not a path?

Reply
0 Kudos
daphnissov
Immortal
Immortal

You don't, you use esxcli to upgrade using that path. Guide available here.

Reply
0 Kudos
glousteau
Enthusiast
Enthusiast

I can't see how this matters, but i executed the command from a ssh session versus on the host itself and got this error

esxcli software v

ib update esxui-signed-6360286.vib

Error: Unknown command or namespace software vib update esxui-signed-6360286.vib

Reply
0 Kudos
glousteau
Enthusiast
Enthusiast

nevermind, worked this time

[root@dot10:/vmfs/volumes/5a01c772-921df7a5-24b9-d8d385c049ea] esxcli software v

ib update -d esxui-signed-latest.vib

[MetadataDownloadError]

Could not download from depot at esxui-signed-latest.vib/index.xml, skipping (('esxui-signed-latest.vib/index.xml', '', 'file not found'))

        url = esxui-signed-latest.vib/index.xml

Please refer to the log file for more details.

[root@dot10:/vmfs/volumes/5a01c772-921df7a5-24b9-d8d385c049ea]

shows 1.23 as my version and my problem is solved

Thanks!!!  mighty quick service, I'm thoroughly impresssed Smiley Happy

Reply
0 Kudos
daphnissov
Immortal
Immortal

That's not the right command. You need to upload the offline bundle from the Flings site as shown here.

pastedImage_0.png

Once you've uploaded that, you need to execute esxcli software vib update -d "/vmfs/volumes/<my_datastore>/patch-directory/esxui-offline-bundle-6.x-6360286.zip"

Reply
0 Kudos
daphnissov
Immortal
Immortal

Ok, good, so that's what I was thinking. Your issue was addressed in 1.22 or 1.23, so that solved it.

Reply
0 Kudos
glousteau
Enthusiast
Enthusiast

ok, next challenge, how do I copy multiple files to this machine.  I had copied VMs from another server and want to copy them over.  it appears that the webui doesn't have the upload a directory option like the client had??

Reply
0 Kudos
daphnissov
Immortal
Immortal

No directory or multi-file-selection upload possible right now.

Reply
0 Kudos