Hi,
I can't Open virtual Machine folder from <vCenter-Address>/Folder url. actually it returns 500 error. My vCenter appliance version is 6.7 with build number 15129973.
Based on screenshot that I attached, I can just forward to this step, thus when I open VM folder, faced with 500 Error.
Note: It's worked on vCenter 6.5 and we can see all contents in virtual machine's folder such as *.nvram , *.vmdk , *.vmx and etc.
Also you can see error log as below:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2020-01-13T13:11:19.811+03:30 info vpxd[04730] [Originator@6876 sub=HTTP server /folder req=00007f29304b6520 user="username"] Got HTTP GET request for /folder/VM?dcPath=Cloud01&dsName=STOR01
2020-01-13T13:11:19.811+03:30 info vpxd[06403] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-72] [VpxLRO] -- BEGIN lro-3515974 -- SearchIndex -- vim.SearchIndex.findByInventoryPath -- 52cfad26-7ad3-4e5b-2043-1624611f432f(52710809-3213-0d6c-0b4c-972d37b06d37)
2020-01-13T13:11:19.811+03:30 info vpxd[06403] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-72] [VpxLRO] -- FINISH lro-3515974
2020-01-13T13:11:19.814+03:30 info vpxd[05837] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-78] [VpxLRO] -- BEGIN lro-3515977 -- ServiceInstance -- vim.ServiceInstance.retrieveContent -- 52cfad26-7ad3-4e5b-2043-1624611f432f(52710809-3213-0d6c-0b4c-972d37b06d37)
2020-01-13T13:11:19.814+03:30 info vpxd[05837] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-78] [VpxLRO] -- FINISH lro-3515977
2020-01-13T13:11:19.814+03:30 info vpxd[04769] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-10] [VpxLRO] -- BEGIN session[52cfad26-7ad3-4e5b-2043-1624611f432f]521e6dcc-4dc6-303e-a3d1-0433918449b8 -- datastoreBrowser-datastore-4981 -- vim.host.DatastoreBrowser.search -- 52cfad26-7ad3-4e5b-2043-1624611f432f(52710809-3213-0d6c-0b4c-972d37b06d37)
2020-01-13T13:11:19.950+03:30 info vpxd[04769] [Originator@6876 sub=vpxLro opID=req=00007f29304b6520-10] [VpxLRO] -- FINISH session[52cfad26-7ad3-4e5b-2043-1624611f432f]521e6dcc-4dc6-303e-a3d1-0433918449b8
2020-01-13T13:11:19.954+03:30 info vpxd[04805] [Originator@6876 sub=vpxLro opID=2a15e0ea] [VpxLRO] -- BEGIN lro-3515982 -- nfcService -- vim.NfcService.fileManagement -- 52cfad26-7ad3-4e5b-2043-1624611f432f(52710809-3213-0d6c-0b4c-972d37b06d37)
2020-01-13T13:11:19.960+03:30 info vpxd[04805] [Originator@6876 sub=vpxLro opID=2a15e0ea] [VpxLRO] -- FINISH lro-3515982
2020-01-13T13:11:20.363+03:30 info vpxd[04832] [Originator@6876 sub=vpxLro opID=261383c] [VpxLRO] -- BEGIN lro-3515983 -- ServiceInstance -- vim.ServiceInstance.retrieveContent -- 52c73ce5-b7e7-aa11-0597-256845c498b3(52505850-89cb-d5d4-5992-573892659c55)
2020-01-13T13:11:20.364+03:30 info vpxd[04832] [Originator@6876 sub=vpxLro opID=261383c] [VpxLRO] -- FINISH lro-3515983
2020-01-13T13:11:20.364+03:30 warning vpxd[04807] [Originator@6876 sub=Default] [NFC ERROR] Received fileIO error 2 from server: A file error was encountered -- NfcFssrvrRead: failed to read 73728 bytes @ 0 : Error
-->
2020-01-13T13:11:20.364+03:30 error vpxd[04807] [Originator@6876 sub=HTTP server /folder] NfcFssrvr_IO returned 4, fileIOErr: 2
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Actually it should open vm folder and show some thinng like thise :
Whould you please help me in this regard?
Thank you in Advance
Hi,
have you tried with another browser?
ARomeo
yes,same Issue
Hi,
well, have you tried to restart the vpxd service?
ARomeo
I already restart all services, clear browser cache , try another browser and also use SSO administrator and didn't worked.
Hi,
Does it allow you to access the virtual machine folder directly from the host where it resides?
let's see if it's a vCenter problem or something else ...
ARomeo
It is related to vCenter specific 6.7 version. As I told we can open it in vCenter version 6.5 ....
I can open it in my ESXi , but vCenter
Any Update...?
Hello Omid, were you able to find a solution? I have the same issue.
Can you tell me what you did before findind the issue? I updated VCSA to latest version (a few weeks ago).
I have two ESX hosts two NFS datastores and two iSCSI one
VCSA: 6.7.0, build 15976728
host1: VMware ESXi, 6.7.0, 14320388
host2: VMware ESXi, 6.7.0, 8169922
2020-04-29T13:26:30.588Z info vpxa[2099449] [Originator@6876 sub=Libs opID=lro-1850522-7ab0cf65] NfcNet_OptimizeSocketBuffer: Setting buffer size using RTT=0 ms BANDWIDTH=134000 bytes/ms BUFFER_SIZE=40KB
2020-04-29T13:26:30.588Z info vpxa[2099449] [Originator@6876 sub=vpxNfcServer opID=lro-1850522-7ab0cf65] Successfully initialized nfc callback for a write to the socket to be invoked on a separate thread
2020-04-29T13:26:30.588Z info vpxa[2099449] [Originator@6876 sub=vpxNfcServer opID=lro-1850522-7ab0cf65] Plugin started
2020-04-29T13:26:30.588Z info vpxa[2099449] [Originator@6876 sub=vpxLro opID=lro-1850522-7ab0cf65] [VpxLRO] -- FINISH lro-1850522
2020-04-29T13:26:30.810Z warning vpxa[2099391] [Originator@6876 sub=Libs] [NFC ERROR] NfcFileRawPread: Failed to read 2940 bytes at offset 0 from file '/vmfs/volumes/521e576f-82a8f646-d3cd-40f2e9078432/vmWinMdza': Success (@&!*@*@(msg.fileio.success)Success)
2020-04-29T13:26:30.811Z warning vpxa[2099161] [Originator@6876 sub=Libs] [NFC ERROR] NfcFssrvrSendResponse: Found an error in the nfc session: A file error was encountered (NFC_FILE_ERROR)
2020-04-29T13:26:30.811Z warning vpxa[2099161] [Originator@6876 sub=Libs] [NFC ERROR] Sending fileIO error 2: A file error was encountered -- NfcFssrvrRead: failed to read 2940 bytes @ 0 : Error
Hi Imanson,
I can't find any solution yet ...
Still browsing
If you find out, I would be appreciate to inform me.
Hi Guys,
we have same issue since updating our vcenters from 6.7U2 up to 6.7U3f.
Does anybody opened an issue ticket for vmware to investigate this?
best regards
Hi,
please try updating the ESXi hosts to a more recent version, which should help here based on a recent case I had.
Regards,
Patrik
Hi Patrik,
We are facing the same issue with vcsa 6.7 (Build: 17712750) and ESXi Nodes 6.7.0, 14320388 (we are still updating them to ESXi, 6.7.0, 17700523). Could you please share more details about your ESXi Version or what do you mean with "recent version"?
Many thanks in advance.
BR,
Onur
@hlo58 Unfortunately I don't remember which version caused this particular behavior nor to which version the customer updated their ESXi's to solve the issue. The latest 6.7 U3 release however should be fine. (Which might be recommended due to security fixes anyway)