Urbackup 1.4.7 server chrashes if client reaches 100%

Server
1

Hy- my urbackup Server 1.4.7 crashes sometime - it looks like the server chrashes if a xp client finishes the image backup.
Problem ist that other client also backups at the same time - so no client finishes the backup process - after some time alle clients tries to repeat the backup - but the server chrashes again.
Error in Administrative events

Faulting application name: urbackup_srv.exe, version: 0.0.0.0, time stamp: 0x54a5691c
Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: Faulting application name: urbackup_srv.exe, version: 0.0.0.0, time stamp: 0x54a5691c
Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2bcac
Exception code: 0x40000015
Fault offset: 0x00000000000761c9
Faulting process id: 0xf58
Faulting application start time: 0x01d052933dd891e4
Faulting application path: C:\Program Files\UrBackupServer\urbackup_srv.exe
Faulting module path: C:\Windows\SYSTEM32\MSVCR100.dll
Report Id: 3515d123-be8a-11e4-80fc-00155d046c01
Faulting package full name:
Faulting package-relative application ID:

It would be nice if there is no chrash - but i think whats was more important is the error handling on client.
If the client wasn’t able to backup more then x times within a specified time range - it should warn the server - and only keeps trying if the admin allows it.
So the server doesn’t poluttes with corrupted hdd images.
For now i disabled the image backup for the specific client - but if i don’t remember this client - it was hard to find the specific client - because i can’t see all the client with disabled image backup - i must go through over 100 settings to check if there is a different setting.

How can i solve the server crash ?
Kind regards

Fogo
PS: very nice peace of software - the best programm i have found in the last 2 years.

2

Sorry that it is crashing.

When crashing it should have written a crash dump somewhere. Can you have a look into C:\Program files\UrBackupServer\urbackup.log ? It should have written where it saved the crash dump there.

Can you send me the C:\Program files\UrBackupServer\urbackup.log file and the crash dump zipped to martin@urbackup.org ? That usually helps with finding bugs.

3

Hy - unfortunately on the server there was no entry in urbackup.log which references to the crash - so i think also a crashdump wasn’t written at that time.
I solved the problem by looking in debug.log on the client.

There are many warnings like this
WARNING: Writer MSDEWriter has failure state VSS_WS_STABLE with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.

so i decided to follow these instructions (partly)
http://support.microsoft.com/kb/940184/en-us

I just use the follwing commands on the XP Client

cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 /i eventcls.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll

two of the commands throwed out a error message - but after all - this client was able to backup again.

So my question is - why i can’t find a crashdump on server -but in server event log - the crash will be logged.
there was also no log in the error log which everyone can view in the Urbackup Server Browser interface.

I think it would be nice if every client has a failure control - if the client wasn’t able to complete the backup for 3 times it should stop - but should sent the errors to the server after the server was able to receive the errors again (after automatic urbackup server service restarted)

Kind regards

Sorry for not mailing the log - but as i told you the log was empty at crashtime.

Thanks