VM Explorer Practitioner Forum
cancel

Failed: [path to disk].vmdk cannot be downloaded, 'HTTP/1.1 500 Internal Server Error'.

Highlighted
Michael Jankows
Contributor.

Failed: [path to disk].vmdk cannot be downloaded, 'HTTP/1.1 500 Internal Server Error'.

Hi,

I'm a newby here and we are evaluating HPE VM Explorer® 6.1.005 (64-bit).

During a scheduled backup of a VM we get the following error: 

Failed: [path to disk].vmdk cannot be downloaded, 'HTTP/1.1 500 Internal Server Error'.
 
I found KM02235440 but I'm not able to acces because of permission denied. 
Can you help to solve this error?
Best regards,
Michael 
5 REPLIES
Sandeep Kumar S
Micro Focus Expert

Re: Failed: [path to disk].vmdk cannot be downloaded, 'HTTP/1.1 500 Internal Server Error'.

Hello Michael,

Cause
This problem is caused by an ESXi WebService connection lost during the files transfer. Since the problem is outside VM Explorer it cannot be solved by HPE.

Fix
Enable the VM Explorer Agent for the affected hypervisor to change the transport method
Edit Server -> SSH / VM Explorer Agent -> Try to use VM Explorer Agent on ESXi.

Hope this helps.

Regards,

Sandeep

Michael Jankows
Contributor.

Re: Failed: [path to disk].vmdk cannot be downloaded, 'HTTP/1.1 500 Internal Server Error'.

Hi,

I've changed as requested but it doesn't help. Any other hint to fix it?

Michael

Sandeep Kumar S
Micro Focus Expert

Re: Failed: [path to disk].vmdk cannot be downloaded, 'HTTP/1.1 500 Internal Server Error'.

Hello,

Please share us the logs and task report for further analysis. 

In the VMX Web Interface, go to "admin" -> "Settings" -> "Support" and click to "Generate New Debug Report". Download the zip file and provide it to us.

We shall look into it and suggest.

Regards,

Sandeep

Michael Jankows
Contributor.

Re: Failed: [path to disk].vmdk cannot be downloaded, 'HTTP/1.1 500 Internal Server Error'.

Hi,

Sorry for the delay. You can find the zip under https://dl.dropboxusercontent.com/u/2459192/VMXDebugReport-20160809-095854.zip

Regards,

Michael

Sandeep Kumar S
Micro Focus Expert

Re: Failed: [path to disk].vmdk cannot be downloaded, 'HTTP/1.1 500 Internal Server Error'.

Hello Michael,

 

Thanks for the info. Below are my observation and comments:

 

Affected ESXi:

 

===================================================

Server: California

ESXi: VMware ESXi 6.0.0 build-3073146 (U1)

 

Affected VMs:

 

CA-WIN12R2-EM9

CA-APSDC1

CA-APS-VEEAM

ca-win12-tfs13

CA-APSGIT

CA-APSRDS

NETZ_VM

===================================================

 

VMExplorer.log:

===================================================

[5384] 07.08.2016 02:01:13                           [7466051] Snapshot created on VM: California/CA-APSDC1

[5384] 07.08.2016 02:01:16                           Folder "Z:\CA-APSDC1\2016-08-07-020001" created, but could not set AccessControl [2] to: Z:\CA-APSDC1\2016-08-07-020001

[5384] 07.08.2016 02:01:16                           [7466051] Creating target .vmx file...

[5384] 07.08.2016 02:01:16                           [7466051] Target File 'Z:\CA-APSDC1\2016-08-07-020001\CA-WIN12R2-APSDC1.vmx.080702000110.tmp' created

[5384] 07.08.2016 02:01:16                           [7466051] Target File "Z:\CA-APSDC1\2016-08-07-020001\CA-WIN12R2-APSDC1.vmsd.080702000110.tmp" created

[5384] 07.08.2016 02:01:16                           [7466051] Copying [Datastore1] CA-WIN12R2-APSDC1/CA-WIN12R2-APSDC1.vmxf

[5384] 07.08.2016 02:01:20                           [7466051] Copying [Datastore1] CA-WIN12R2-APSDC1/CA-WIN12R2-APSDC1.nvram

[5384] 07.08.2016 02:01:20                           [7466051] Copying [Datastore1] CA-WIN12R2-APSDC1/CA-WIN12R2-APSDC1-Snapshot5.vmsn

[5384] 07.08.2016 02:01:21                           [7466051] Copying [Datastore1] CA-WIN12R2-APSDC1/CA-WIN12R2-APSDC1-Snapshot6.vmsn

[5384] 07.08.2016 02:01:22                           [7466051] Copying [Datastore1] CA-WIN12R2-APSDC1/CA-WIN12R2-APSDC1.vmdk

[5384] 07.08.2016 02:01:23                           [7466051] Copying [Datastore1] CA-WIN12R2-APSDC1/CA-WIN12R2-APSDC1-flat.vmdk

[5384] 07.08.2016 02:01:23 [ERROR]         : Unexpected end of network stream.

[5384] 07.08.2016 02:01:34 [ERROR]         : Unexpected end of network stream.

[5384] 07.08.2016 02:01:45 [ERROR]         : Unexpected end of network stream.

[5384] 07.08.2016 02:01:56 [ERROR]         Error opening web service stream (ESXSDKService) : CA-WIN12R2-APSDC1/CA-WIN12R2-APSDC1-flat.vmdk cannot be downloaded, 'HTTP/1.1 500 Internal Server Error'

[5384] 07.08.2016 02:02:08 [ERROR]         Error opening web service stream (ESXSDKService) : CA-WIN12R2-APSDC1/CA-WIN12R2-APSDC1-flat.vmdk cannot be downloaded, 'HTTP/1.1 500 Internal Server Error'

[5384] 07.08.2016 02:02:20 [ERROR]         Error opening web service stream (ESXSDKService) : CA-WIN12R2-APSDC1/CA-WIN12R2-APSDC1-flat.vmdk cannot be downloaded, 'HTTP/1.1 500 Internal Server Error'

===================================================

 

California Hostd.log:

 

===================================================

2016-08-07T01:01:56.594Z info hostd[2F6C2B70] [Originator@6876 sub=Libs] FileIOErrno2Result: Unexpected errno=12, Cannot allocate memory

2016-08-07T01:01:56.594Z info hostd[2F6C2B70] [Originator@6876 sub=Libs] read failed, errno=12, Cannot allocate memory

2016-08-07T01:01:56.594Z warning hostd[2F6C2B70] [Originator@6876 sub=HTTP server /folder] Reader or Writer failure: Cannot allocate memory

===================================================

 

Issue is seen only on a particular ESXi server during backup which happens occasionally.

 

Other ESXi Servers don’t have the issue.

 

VMware ESXi 5.0.0 build-469512

VMware ESXi 5.0.0 build-702118

VMware ESXi 5.5.0 build-1623387

VMware ESXi 5.5.0 build-1623387

VMware ESXi 5.5.0 build-1331820

 

This is mainly connectivity issue between ESXi Management NW and VMX server. It also looks like your ESXi server wasn't able to allocate enough memory for the file transfer and the network connection was for this reason probably aborted.

 

Would advise to consult the VMware admin or support and get the logs checked from ESXi 6 end.

 

Hope this helps.

 

Regards,

Sandeep