Discussions specific to the VMware vSphere hypervisor
Post Reply
SGalbincea
Enthusiast
Posts: 55
Liked: 6 times
Joined: May 25, 2012 2:09 pm
Full Name: Steve Galbincea
Location: Houston, TX
Contact:

Re: Unable to retrieve next block transmission command

Post by SGalbincea » Jan 28, 2015 9:20 pm 2 people like this post

Disabling IPv4 Offload on all of our 10Gb NICs in both physical proxy servers (SAN and LAN sides) seems to have resolved this issue for us - 30TB server backup complete!
Senior Solutions Engineer, SLED - VMware

andnym
Influencer
Posts: 10
Liked: 2 times
Joined: Jul 13, 2011 8:04 am
Full Name: Anders Nyman
Contact:

Re: Unable to retrieve next block transmission command

Post by andnym » Feb 03, 2015 8:42 am 1 person likes this post

I have managed to solve the issue for my problem. After requesting a FW opening in order to have the possibility to use other Veeam proxies on a different network for troubleshooting I found out that IPS in our firewall suddenly started to reject the traffic. Checkpoint IPS watches the entire communication, not just the start of the transmission. Then probably somewhere into the job the IPS found a code that was suspect to one if the IPS detections and blocked the traffic.

All my servers affected was identical (cloned from one) and that is why only those was rejected.

In my case it happened around the same time for each vm, around 28-30% into the disk.

BR
Anders

VenoX
Influencer
Posts: 11
Liked: 1 time
Joined: Mar 12, 2012 11:29 am
Full Name: L33t rul0r
Contact:

[MERGED] : Backup not Working

Post by VenoX » Feb 25, 2015 7:35 am

Hello,

I have a production critical Problem - Case 00812606 - Backup of one of my Servers in the job is not working.

Since customer support seems to be overstrained, i ask the community instead:

I tried ctb reset, readd the server to the job, but nothing helps.
Error Message:
24.02.2015 20:45:11 :: Processing FILESERVER Error: Thread not finished within [1800000] milliseconds.
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.
Exception from server: Thread not finished within [1800000] milliseconds.
Unable to retrieve next block transmission command. Number of already processed blocks: [76327].
Failed to download disk.


Any ideas?

BR
VenoX

v.Eremin
Veeam Software
Posts: 15077
Liked: 1133 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Unable to retrieve next block transmission command

Post by v.Eremin » Feb 25, 2015 8:11 am

Hi,

Your post has been merged into existing discussion. While waiting for an answer from support team, it might be worth checking posts provided above for possible solutions.

Thanks.

Andreas Neufert
Veeam Software
Posts: 2825
Liked: 478 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Unable to retrieve next block transmission command

Post by Andreas Neufert » Aug 06, 2015 7:23 am 1 person likes this post

Hi,

I had random job failures with the message

Code: Select all

"Error: Application is shutting down. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Application is shutting down. Unable to retrieve next block transmission command. Number of already processed blocks: [34664]. Failed to download disk."
Thanks to support 00985273 it was fixed by updating the correct time at ESXi host.

In this case the ESXi host had a windows NTP server configured but ESXi expect NTP v4 while windows work on NTP v3.
After updating /etc/ntp.conf on the ESXi hosts
server <ip>
to
server <ip> version 3
the ESXi worked with correct time and Job run now without random failures.

Thank you Veeam Support.

loelly
Enthusiast
Posts: 51
Liked: 10 times
Joined: Apr 17, 2014 8:25 am
Full Name: Jens Siegmann
Contact:

Re: Unable to retrieve next block transmission command

Post by loelly » Aug 19, 2015 7:20 am

Andreas,

that's new to me. My ESXi (5.5) hosts are all configured to poll NTP at Windows domain controllers. Time is OK, no issues.

Is this something specific to ESXi 6?

Thanks!

Maik.

Andreas Neufert
Veeam Software
Posts: 2825
Liked: 478 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Unable to retrieve next block transmission command

Post by Andreas Neufert » Aug 20, 2015 1:31 pm

I don´t know if this is "new". I used another NTP Service before. I use a lot of nested ESXi servers and suspend them from time to time. Without NTP the ESXi host will run out of sync and backup is not possible.

In this case it was a 5.5 with latest patch level. All ESXi time diagnostic command showed a successful test with NTP. But the time never updated. After I changed it to "version 3" in the ntp.conf it worked immediatelly flawless since a month.

You can try to change the time manually (change date) (no VMs running on the ESXi host) and test if after a reboot the time will update automatically.

Andreas Neufert
Veeam Software
Posts: 2825
Liked: 478 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Unable to retrieve next block transmission command

Post by Andreas Neufert » Aug 20, 2015 1:32 pm

At least this NTP setting fixed my random problem with "Unable to retrieve next block transmission command"

manasar
Lurker
Posts: 1
Liked: 1 time
Joined: Aug 06, 2015 1:35 am
Full Name: Mana Saringkanratana
Contact:

Re: Unable to retrieve next block transmission command

Post by manasar » Oct 04, 2015 1:18 pm 1 person likes this post

I have the save problem and follow to edit ntp.conf. (Before edit ntp.conf that my ntp service on esxi is ok)

It'work.Error has gone.

Thank you very much

haslund
Veeam Software
Posts: 428
Liked: 86 times
Joined: Feb 16, 2012 7:35 am
Full Name: Rasmus Haslund
Location: Denmark
Contact:

Re: Unable to retrieve next block transmission command

Post by haslund » Feb 14, 2016 1:32 am

loelly wrote:Andreas,

that's new to me. My ESXi (5.5) hosts are all configured to poll NTP at Windows domain controllers. Time is OK, no issues.

Is this something specific to ESXi 6?

Thanks!

Maik.
Nothing new, please see VMware KB 1035833
Rasmus Haslund
Principal Technologist, Global Education Services @ Veeam Software
Veeam Certified Architect #1 | Veeam Certified Trainer #4 [v7,v8,v9] | Veeam Certified Trainer Mentor #1
Twitter: @haslund
Blog: www.perfectcloud.org

schmad27
Lurker
Posts: 2
Liked: never
Joined: Dec 30, 2016 1:38 pm
Full Name: David P Schmalzer
Contact:

Re: Unable to retrieve next block transmission command

Post by schmad27 » Dec 30, 2016 1:45 pm

I have the same error and it only happens on the same server out of 10 servers. It's over a vpn WAN connection and the connection is stable, so I don't know why Veeam is reporting that it is not. We have users at that site who connect to our terminal servers and they never complain about network performance.

Andreas Neufert
Veeam Software
Posts: 2825
Liked: 478 times
Joined: May 04, 2011 8:36 am
Full Name: @AndyandtheVMs Veeam PM
Location: Germany
Contact:

Re: Unable to retrieve next block transmission command

Post by Andreas Neufert » Dec 30, 2016 5:36 pm

Please check if B&R, Proxy and Repositiry Server have same time and timezone setting, just for a test.

schmad27
Lurker
Posts: 2
Liked: never
Joined: Dec 30, 2016 1:38 pm
Full Name: David P Schmalzer
Contact:

Re: Unable to retrieve next block transmission command

Post by schmad27 » Jan 03, 2017 2:46 pm

Yes, they both have the same time zone settings. Still the same 1 server out of 10 servers is failing. Here is the full error:

Processing MyServerName Error: Unstable connection: unable to transmit data. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: read: End of file Unable to retrieve next block transmission command. Number of already processed blocks: [11377]. Failed to download disk.

foggy
Veeam Software
Posts: 16702
Liked: 1343 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Unable to retrieve next block transmission command

Post by foggy » Jan 03, 2017 3:05 pm

David, please contact technical support for logs investigation.

kingsize
Influencer
Posts: 17
Liked: 1 time
Joined: Apr 21, 2017 6:28 pm
Full Name: King Size
Contact:

[MERGED] VDDK ERROR 13

Post by kingsize » Oct 01, 2017 3:03 pm

Hi Team,

A little bit information about my environment:
*There are 2 servers, both running vmware esxi 6.0 licensed fully patched update 2 HPE
*Rebooted the host
*Fully patched firmware on the HPE host
*This is not a domain controller.
*I do have VEEAM installed on this VM.

I am getting the below error on 1 VM.

VDDK error: 13 (You do not have access rights to this file). Value: 0x000000000000000d
Failed to read from a virtual disk
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.
Exception from server: VDDK error: 13 (You do not have access rights to this file). Value: 0x000000000000000d
Failed to read from a virtual disk
Unable to retrieve next block transmission command. Number of already processed blocks: [3053].
Failed to download disk

ticket id: #02328800


Support is telling me to update to the latest VEEAM version, I am 100% sure that this is not the issue. Anyone here can maybe help to fix this issue?
I searched the net and the forum section, tried every possible solution. I am stuck!

Thanks!

Post Reply

Who is online

Users browsing this forum: Baidu [Spider] and 34 guests