glib-2.0.dll crash 0xc0000005

[emachabert]

Hi all,

Before opening a support case, because the problem seems to be related to the environment, not to veeam itself.

Has anybody encountered such a behaviour in the past ? :

- VSS fails at first pass with an RPC error (8007706BE)
- VSS is OK at second or third pass
- When looking at Windows event log on the backup server itself, for each VSS failure I have an APP CRASH on glib-2.0.dll (see below)
- any SQL log truncation fails with 8007706BA (but no app crash logged on these)

Setup :
- Veeam 7.0R2 On Windows 2012 virtual machine (using vmxnet3)
- many networks protected by CheckPoint firewalls
- InverseVSSProtocolOrder set to 1
- no antivirus on backup server
- no Windows firewall
- a temporary rule on the checkpoint to allow any communication between the backup server and all the servers (we are in debugging mode)


APP Crash summary

Nom de l’application défaillante VeeamGuestAgentControl.exe, version : 7.0.0.764, horodatage : 0x5281462e
Nom du module défaillant : glib-2.0.dll, version : 2.16.4.0, horodatage : 0x48801db1
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0005a870
ID du processus défaillant : 0x1080
Heure de début de l’application défaillante : 0x01cf0a48fdb98ed4
Chemin d’accès de l’application défaillante : C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestAgentControl.exe
Chemin d’accès du module défaillant: C:\Program Files\Veeam\Backup and Replication\Backup\VSS\glib-2.0.dll
ID de rapport : efdc8b2a-763c-11e3-940a-005056a407a4
Nom complet du package défaillant :
ID de l’application relative au package défaillant :

I have already checked that KB, but does not apply to this context: https://supportcenter.checkpoint.com/su ... id=sk41208

Any idea ?

[Vitaliy S.]

Hello Eric,

Do you have these failures on the backup server that is trying to backup itself with VSS (AAIP) enabled? Did I get it right? Have you tried manually initiating Windows VSS backup on this server? Do you see the same symptoms?

Thank you!

[emachabert]

Hi,

No, it's not when trying to backup the server itself, it's when backuping other servers...

[Vitaliy S.]

In this case I would suggest reviewing VeeamGuestAgent logs for better understanding on what's going on, as I couldn't find any similar error messages reported before.

[emachabert]

I'll open a case tomorrow.

[emachabert]

Case #00499178

[veremin]

Thanks, Eric, for providing ticket number. Let's wait and see what support team says about this, as we haven't seen similar issues previously.

[masonit]

Hi

We have the same issue. For us vss backup seems to work fine but the problem starts when truncating logs. Tonight we had about 10 jobs with vms that had this issue:

2014-01-20 23:17:52 :: Unable to truncate transaction logs. Details: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

I have looked at a couple of jobs and they all match up with the error I see local on the Veeam backup server:

Code: Select all

Faulting application name: VeeamGuestAgentControl.exe, version: 7.0.0.764, time stamp: 0x5281462e
Faulting module name: glib-2.0.dll, version: 2.16.4.0, time stamp: 0x48801db1
Exception code: 0xc0000005
Fault offset: 0x0005a870
Faulting process id: 0x176c
Faulting application start time: 0x01cf1604ebfb2d22
Faulting application path: C:\Program Files\Veeam\Backup and Replication\VSS\VeeamGuestAgentControl.exe
Faulting module path: C:\Program Files\Veeam\Backup and Replication\VSS\glib-2.0.dll
Report Id: d912951e-821f-11e3-8ad6-005056af0bc3

Veeam backup server = Windows server 2008 R2 std.
Case id: 00505452

\Masonit

[emachabert]

For the moment, we have no feedback from Veeam Support, they are still working on it.

Did you change anything on your servers ? Did a Windows update ?

[masonit]

No nothing changed. I only see the event log error on the backup server. All is fine on the proxy servers.
I have only got this problem one time when I was running 6.5. Now I have got it 8 times during 1 month with version 7. I have got this error 3 nights in row. But last night everything has worked fine. No errors at all. But it happens more and more often. It only happens during peak hours but that is pretty much expected. But the Veeam server is not congested.

\Masonit

[masonit]

I think my problem is solved now. At least I haven't had the error for over a week now. The fix was to update som dll files that I got from Veeam support.

\Masonit

[veremin]

Thanks, Magnus, for coming back and updating the topic with the resolution; much appreciated.

[emachabert]

Same here.
After pushing the dlls obtained from Veeam, everything is green again