Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0 :: Support Forum

JimB Donor
Joined:: 2022-02-09
Posts:: 5
Location:: Guam

Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

2022-02-09 06:46

Trying to copy a 1.1TB file from local hard drive to VMware datastore and getting the error:

Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

I copied the file from a VMware 5.5 datastore w/o incident but copying it back to VMware 7.0.2 ESXi generates the error every few seconds.
Any way to fix this? Using WinSCP v5.19.5

Reply with quote

martin◆ Site Admin
Joined:: 2002-12-10
Posts:: 41,441
Location:: Prague, Czechia

Re: Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

2022-02-10

Please post session log file.
Can you upload the file using any other SFTP client? If you can, please post its verbose log file too.

Reply with quote

JimB Donor

Re: Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

2022-02-10 21:36

I've tried a few other SFTP clients but the won't connect for some reason. I finally tried deleting the partial file transferred and started over from scratch yesterday. I came in this morning and about 160GB has copied over but WinSCP showed an out of memory error. I didn't save the log but will next time. Started it over again, had to delete the partial file.

Reply with quote

JimB Donor
Joined:: 2022-02-09
Posts:: 5
Location:: Guam

Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

2022-02-14 21:55

Here is the message that appeared today:

Stack trace:
(00407A58)
(00056FEE) ntdll.dll
(0000F13E) ntdll.dll.KiUserExceptionDispatcher
(00CF32DB)
(00CF27E6)

That was in an error message that popped up: "Invalid Access to memory". I've attached the log from the session.

root@192.168.30.35.log (6.17 MB)

Description: transfer log

Reply with quote

martin◆ Site Admin

Re: Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

2022-02-21

So what other client did you try? How did you configure it? What error did you get?

Reply with quote

JimB Donor
Joined:: 2022-02-09
Posts:: 5
Location:: Guam

Re: Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

2022-02-22 03:27

I tried bitkinex323, coreftplite64 and the solarwinds voyager software. None of them would even connect to the datastore, not sure why and I didn't spend much time on them.
What I have noticed is that it gets to 266GB then stops with a lost connection message. When I try and restart the download I get the 'Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0' message. The file size is 1.1TB.
I was able to copy the file from ESX 5.5 datastore to a hard drive w/o any problems. But copying back to ESX 7.0 is giving me grief.
thank you...

Reply with quote

martin◆ Site Admin

Re: Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

2022-02-22

Can you try some more mainstream client, like OpenSSH or FileZilla?

Reply with quote

JimB Donor
Joined:: 2022-02-09
Posts:: 5
Location:: Guam

Re: Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

2022-02-23 00:30

Hi Martin;
Ok, thanks I'll try after this weekend.
I had shutdown the server and copied the files from the ESX 5.5 datastore and was leaving the server down until I copied the files over and brought it up under ESX 7. Since I couldn't get the files copied and do this month's change on the relocated VM, I have to bring it back up under 5.5.
The server is a WSUS server and have a change scheduled for this weekend to install updates. By Monday I can shut it down and try copying it.

Reply with quote

Loeke Guest

Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

2022-03-20 11:07

I had the same problem today copying files from my Windows 10 PC to my Ubuntu server.
The cause appeared to be a full physical disc ....

Reply with quote

Georgeis Guest

2022-07-11 00:50

I suffered the same issue by trying to run an Ubuntu VM, and finally when I copied to /VMFS/volumes/ on VMware ESXi datastore folder it allows to me to do it

Reply with quote

me_2022 Guest

Not enough disk space

2022-09-19 08:58

For me the problem solved by deleting some files from remote server, and freeing up enough disk space for the file + additional space

Reply with quote

martin◆ Site Admin

Re: not enough memory

2022-09-19

@me_2022: Thanks for sharing your findings.

Reply with quote

Guest

Re: Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

2022-11-16 17:31

Please check the space on the target server.

Reply with quote

kduffy Guest

Full disc

2023-03-21 10:33

I also encountered this and it was due to a full disc on the receiving server

Reply with quote

Hara Guest

Right solution

2023-06-02 15:30

@Georgeis: Right solution, worked for me as well.

Reply with quote

juanfernet007 Guest

Re: Error: Received SSH2_MSG_CHANNEL_DATA for nonexistent channel 0

2023-06-09 01:37

Este problema ocurre porque el servidor tiene llena la partición donde desea adicionar el archivo.

Translation: This problem occurs because the server has full the partition where you want to add the file.

Reply with quote

Guest

2023-06-11 23:11

Yep didn't watch size of remote drive was problem with this for me.

Reply with quote

AKTSG Guest

FileZilla worked

2023-08-11 12:44

Got the same message, FileZilla worked fine uploading my files.

Reply with quote

martin◆ Site Admin

Re: FileZilla worked

2023-08-13

@AKTSG: Please post both WinSCP and FileZilla log files.

Reply with quote

Graham Hardy Guest

Classic error message

2023-10-24 10:41

The error displayed means that you have insufficient space available on your file system or remote storage location.
Either increase the free space or perform house keeping so that you have enough space to accommodate the file copy.

Reply with quote

roland Guest

2024-07-31 16:29

I got the same message when I transferred a large Zip Archive ~ 600MB. In my case, the message had nothing to do with free space. The target device still had enough free space to receive the same file 100 times. I continued the file transfer from the last position, but the file was corrupted afterwards. This issue is reproducible with version 6.3.4. I switched to Filezilla.

Reply with quote