Veeam Failed to connect to the port [xx.xx.xx.xx:2501].

If you are using Veeam for HyperV and onhost mode enabled you may receive an error like below.

Processing ‘VMName’ Error: Client error: Failed to connect to the port [ProxyIPAddress:2501].
Guest processing skipped (check guest OS VSS state and integration components version)
Error: Client error: Failed to connect to the port [ProxyIPAddress:2501].

Actually it is strange that it was working yesterday but today I met this error for the same job. anyway, to investigate the issue I check firewall traffic to see what traffic is passing through veeam proxy.
Continue reading “Veeam Failed to connect to the port [xx.xx.xx.xx:2501].”

Veeam – Unable to truncate transaction logs RPC 1726

After Veeam 6.5 to 7.0 upgrade, some VMs which have application aware enabled gave the following error.

Unable to truncate transaction logs. Details: RPC function call failed. Function name: [BlobCall]. Target machine:
[xx.xx.xx.xx]. RPC error:The remote procedure call failed. Code: 1726

Also you may see Veeam guest agent services are terminating unexpectedly in your windows event logs..

Faulting application name: VeeamGuestAgent.exe, version: 7.0.0.690, time stamp: 0x520b81e7
Faulting module name: dbghelp.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c5ac
Exception code: 0xc00000fd

I checked ( permissions, VSS writers etc etc ) on VM side but no success.

In my solution,
I disabled application aware processing on backup job. Took a backup. Then re-enabled application aware processing and it is now working fine. I think veeam server pushed a new guest agent on VM side. Now I see no more service termination events and logs are truncated successfully. Hope this helps in your case.