View Full Version : ZWC Service.exe stops after running amdump

October 27th, 2010, 03:02 AM
Dear Community,

Below i've listed a few log files, concerning an amanda backup server (CentOS) polling to a Windows server 2008 R2 to back up the content of just two simple folders.


I've just recently installed ZManda on the Windows client. However the Error-Log is giving me a heap of APPCRASH Events. Zmanda is active on the Windows server as default (amandabackup)

I'm launching an AMCheck towards the server. From there i'm getting the error:

amcheck daily -c windowshostname

Amanda Backup Client Hosts Check
ERROR: windowshostname: Unauthenticated user
Client check: 1 host checked in 0.281 seconds. 1 problem found.

(brought to you by Amanda 2.6.1p1)

So with that in mind i've changed the registry setting to reflect from amandabackup to amanda, since the amanda server is using the user amanda, and not amandabackup.

After changing the Windows registry key from amandabackup to amanda, i'm no longer getting an Error as seen below:

Amanda Backup Client Hosts Check
Client check: 1 host checked in 0.290 seconds. 0 problems found.

(brought to you by Amanda 2.6.1p1)

However, when i now start a CLI dump using ambackup daily windowshostname, the ZWC Service on the windows server shuts down. Below i've listed the informational, warning and error from the logs:

"Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

2 user registry handles leaked from \Registry\User\S-1-5-21-4176737954-1905593560-1013074924-1058:
Process 4136 (\Device\HarddiskVolume2\Windows\System32\WerFault .exe) has opened key \REGISTRY\USER\S-1-5-21-4176737954-1905593560-1013074924-1058
Process 4136 (\Device\HarddiskVolume2\Windows\System32\WerFault .exe) has opened key \REGISTRY\USER\S-1-5-21-4176737954-1905593560-1013074924-1058\Control Panel\International

\\\\\Error Message

"Faulting application name: ZWCService.exe, version:, time stamp: 0x4cb2d614
Faulting module name: Common.dll, version:, time stamp: 0x4cb2d5a7
Exception code: 0xc0000005
Fault offset: 0x00000000000058b6
Faulting process id: 0x8c0
Faulting application start time: 0x01cb75bd3633ea63
Faulting application path: C:\Program Files\Zmanda\Zmanda Client for Windows Community Edition(x64)\bin\ZWCService.exe
Faulting module path: C:\Program Files\Zmanda\Zmanda Client for Windows Community Edition(x64)\bin\Common.dll
Report Id: 9b970a75-e1b0-11df-9a1b-1cc1dee67926"

\\\\\And the informational message:

"Cab Id: 0

Problem signature:
P1: ZWCService.exe
P3: 4cb2d614
P4: Common.dll
P6: 4cb2d5a7
P7: c0000005
P8: 00000000000058b6

What am i doing wrong? Since for no reason at all the ZWC Service just drops out after launching a daily disklist backup on that specific windows host..

With kind regards,


The CentOS Server is based on Amanda 2.6.1p1 whilst the Windows server has the most recent Zmanda version (3.1.3 x64)

October 27th, 2010, 04:33 PM
We have not tested with 2.6.1p2 Amanda server with 3.1.3 Windows Client. Can you upgrade the server to Amanda 3.x versions?


November 1st, 2010, 03:52 AM
Hello paddy,

None of the Zmanda Client versions (compatible with WIn2k8 R2) work with Amanda Server 2.6.1p1?
2.6.1p1 has a few features listed that the 3.X versions no longer posess.

If there's no other option, i suppose we just have to create a new amanda 3.x instance on the backup server.

Kind regards,

November 1st, 2010, 03:24 PM
Zmanda client 3.1.3 has not been tested with Amanda server 2.6.1p1.

Amanda server 3.x has more features than 2.6.1p1. Which 2.6.1p1 feature are you missing in Amanda 3.x?