VeeamGuestAgent crashes

[rfn]

Hi,

We have just started using Veeam Backup & Replication in our small VMware environment and I'm having problems with one VM. It's running Windows Small Business Server 2003 and has a SQL Server 2000 installed.

For some reason Veeam can't control VSS on this VM properly and I get this error in the log:

Code: Select all

Backing up object "GuestIndexData.zip"
VSSControl: FinishSnapshot failed. Transaction logs will not be truncated.
RPC function call failed. Function name: [FinishSnapshot]. Target machine: [192.168.0.3].
RPC error:The remote procedure call failed.
 Code: 1726

On the VM itself I can see that VeeamGuestAgent.exe crashes with this error:

Code: Select all

Event Type:	Error
Event Source:	Application Error
Event Category:	(100)
Event ID:	1000
Date:		31-10-2010
Time:		22:09:35
User:		N/A
Computer:	SERVER1
Description:
Faulting application VeeamGuestAgent.exe, version 5.0.0.179, faulting module VeeamVssSupport.dll, version 5.0.0.179, fault address 0x0000e4e4.

This is the only VM that I'm experiencing this with. I have contacted support but some reason the have gone silent and I haven't heard from them since 25/10 (ticket #535451), so does anyone inhere have a clue about what's happening here?

[Gostev]

This is a known issue - I heard about this from someone else already, and then devs confirmed it last week (this is related to SQL 2000 I believe). My understanding is that the hotfix is already produced, and is in testing.

[rfn]

OK, I'll await that then...

[toreagan]

Any update to when this hotfix will be released? Is the VM or SQL Databases(transactionally) at risk due to the FinishSnapshot failing? I've got a few VM's that are reporting this error on every backup... since upgrading to v5.

VSSControl: FinishSnapshot failed. Transaction logs will not be truncated.
RPC function call failed. Function name: [FinishSnapshot]. Target machine: [172.20.61.8].
RPC error:The remote procedure call failed.
Code: 1726

[Gostev]

It was released a few days ago.

[Aaron@EN-IT]

Where do I get the hot fix at? I am getting this same error on a Windows 2003 Domain Controller after upgradign to v5.

[tsightler]

Contact support and ask for the latest cumulative rollup.

[stevil]

I had the same issue, I applied the above patch but I still have the problem. The VMs in question are XP, would that make any difference?

Cheers

[Vitaliy S.]

Hi Steve,

I don't believe that XP machines would matter, could you tell me your support ticket number? By the way have you already informed our support team about the hotfix results?

[stevil]

Hi, ticket is, 540900, I've not responded back to support yet. I'll do a couple of other tests first to make sure I can reproduce the error.


Regards
Steve

[Mopad]

I'm also getting this error in veeam and on the vm. I got the hotfix from support, and the issue still exists. I replied back to support with my info. Just a FYI.
ticket #541133

VSSControl: FinishSnapshot failed. Transaction logs will not be truncated.
RPC function call failed. Function name: [FinishSnapshot]. Target machine: [192.168.0.3].
RPC error:The remote procedure call failed.
Code: 1726

[Adlantec]

Any news on this? Got the same problem and the hotfix did not help...

Regards,
André

[Vitaliy S.]

Andre, if the hotfix didn't help, please continue working with our support team. Thanks!

[Gostev]

We have investigated the logs from one occasion, and found that hotfix was not properly installed (hotfix files were copied into the root installation folder, instead of VSS subfolder where they would have replaced original files). Thus, old versions of files are still used. We assume all other occasions above have the same issue.

Feel free to contact our support for assistance with proper hotfix installation. I do recommend obtaining latest version of the hotfix instead of using the one you have, because it fixes a few more bugs.

Thanks!

[stevil]

It looks like I may be one of the ones who extracted these files to the wrong folder. The email that comes with the patch just says " Extract to the folder where Veeam Backup is installed", there's no mention of extracting to the VSS folder :/

Oh well, I have a backup running now that hasn't errored where it normally would have done, hopefully this will now be closed

[tsightler]

Another possible issue, I received the hotfix from support last week and installed it, but was still having the problem. I was getting ready to open a support case again but decided to do my own quick investigation to make sure I had the new files. Well, it turns out, I received "Hotfix #3 Build 183" which all seemed fine, except there was one minor issue. The hotfix included both X86 and x64 folders for 32 and 64 bit versions of Veeam, however, the DLL's in the x64/Backup and Replication/VSS/veeamguestagents folder were just the same files that shipped with V5 RTM built on Oct 18th, while the DLL's in the x86/Backup and Replication/VSS/veeamguestagents were newer, build on Oct 28th.

So basically, the x64 tree in the Hotfix didn't have the VSS fixes while the x86 tree did. Since these DLL's are used for the remote agents and are built for the target agent architecture not the Veeam server architecture, I figured they would be identical between the 32 and 64 bit versions of Veeam, so I just copied the x86 versions of the DLL into my x64 install and things seem to be working fine now.

[Vitaliy S.]

Just wanted to mention that for those who have RPC errors even after the hotfix was applied (or after upgrading to 5.0.1), the issue might be on Guest OS's side (the VM you're trying to backup), so please check out your Event logs for any RPC errors.

[HenrikS]

I also got this error on the first backup of one VM today:

Backing up object "GuestIndexData.zip"
VSSControl: FinishSnapshot failed. Transaction logs will not be truncated.
KeepSnapshot error: [Cannot finish snapshot. No job found.]

VM is Windows 2008 R2 with SQL Server 2008 R2 installed.
Veeam is running 5.0.1.198 (64bit)

However, on the next run, no errors occured.

[Alexey D.]

Hello Henrik,

Was this first run successful or backup job failed in the end?

[HenrikS]

Hello Alexey!

Hard to say, since it was not successfull nor failed...:
Status Warning Start time 19.01.2011 09:04:05 Details
Total VMs 1 End time 19.01.2011 09:37:33
Processed VMs 1 Duration 0:33:27
Successful VMs 0 Total size 100,00 GB
Failed VMs 0 Processed size 100,00 GB
VMs in progress 0 Processing rate 51 MB/s

[Alexey D.]

Actually, the job was successful, but with warning. This warning showed up because of abovementioned VSS error - something went wrong with VSS writer inside guest OS itself. If you see this message again, feel free to contact our support and send them the job's log for investigation. Thanks!