Backup fails because of (50) client process aborted.

[amit4465]

Backup Details :

File List : ALL_LOCAL_DRIVES

Status : (50) client process aborted 

Policy : Daily_Inc/Weekly

Server Details :

Windows Server 2008 R2 Enterprise

NOTE : This server is also one of the media server.

Everytime i login to client and restart "Windows Management Instrumentation" service and then runs the backup manually. It completes successfully. 

I want a permanent fix. Please help me to fix this issue.

Error LOGS : 

04/07/2016 03:14:52 - Info nbjm (pid=10689) starting backup job (jobid=6802111) for client ALP-NBUMED-01, policy AL_LAN_WIN_SET1, schedule Daily_Inc
04/07/2016 03:14:52 - Info nbjm (pid=10689) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=6802111, request id:{83118B5E-FC66-11E5-855C-00144F43C41C})
04/07/2016 03:14:52 - requesting resource OM-DSSUG-2
04/07/2016 03:14:52 - requesting resource nbumaster.NBU_CLIENT.MAXJOBS.ALP-NBUMED-01
04/07/2016 03:14:52 - requesting resource nbumaster.NBU_POLICY.MAXJOBS.AL_LAN_WIN_SET1
04/07/2016 03:15:04 - granted resource  nbumaster.NBU_CLIENT.MAXJOBS.ALP-NBUMED-01
04/07/2016 03:15:04 - granted resource  nbumaster.NBU_POLICY.MAXJOBS.AL_LAN_WIN_SET1
04/07/2016 03:15:04 - granted resource  MediaID=@aaabb;Path=/Staging02;MediaServer=nbuom01
04/07/2016 03:15:04 - granted resource  OM01-DSSU-S4
04/07/2016 03:15:05 - estimated 1831220 kbytes needed
04/07/2016 03:15:05 - Info nbjm (pid=10689) started backup (backupid=ALP-NBUMED-01_1459995304) job for client ALP-NBUMED-01, policy AL_LAN_WIN_SET1, schedule Daily_Inc on storage unit OM01-DSSU-S4
04/07/2016 03:15:19 - started process bpbrm (pid=20605)
04/07/2016 03:15:24 - Info bpbrm (pid=20605) ALP-NBUMED-01 is the host to backup data from
04/07/2016 03:15:24 - Info bpbrm (pid=20605) reading file list from client
04/07/2016 03:15:24 - connecting
04/07/2016 03:15:26 - Info bpbrm (pid=20605) starting bpbkar on client
04/07/2016 03:15:26 - connected; connect time: 0:00:00
04/07/2016 03:15:30 - Info bpbkar (pid=7224) Backup started
04/07/2016 03:15:30 - Info bpbrm (pid=20605) bptm pid: 20666
04/07/2016 03:15:47 - Info bptm (pid=20666) start
04/07/2016 03:15:51 - Info bptm (pid=20666) using 262144 data buffer size
04/07/2016 03:15:51 - Info bptm (pid=20666) using 128 data buffers
04/07/2016 03:16:30 - Error bpbrm (pid=20605) from client ALP-NBUMED-01: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.
04/07/2016 03:16:33 - Info bptm (pid=20666) start backup
04/07/2016 03:16:34 - Info bptm (pid=20666) backup child process is pid 20746
04/07/2016 03:16:34 - begin writing
04/07/2016 03:17:05 - Info bpbkar (pid=7224) change journal NOT enabled for <C:\>
04/07/2016 03:49:33 - Info bpbkar (pid=7224) change journal NOT enabled for <D:\>
04/07/2016 04:10:50 - Info bpbkar (pid=7224) change journal NOT enabled for <F:\>
04/07/2016 04:32:19 - Info bpbkar (pid=7224) change journal NOT enabled for <G:\>
04/07/2016 04:53:29 - Info bpbkar (pid=7224) change journal NOT enabled for <H:\>
04/07/2016 05:19:20 - Info bpbkar (pid=7224) change journal NOT enabled for <I:\>
04/07/2016 05:19:23 - Error bpbrm (pid=20605) from client ALP-NBUMED-01: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification
04/07/2016 05:19:23 - Warning bpbrm (pid=20605) from client ALP-NBUMED-01: WRN - archive bits will NOT be cleared
04/07/2016 05:19:24 - Error bptm (pid=20746) system call failed - Connection reset by peer (at child.c.1298)
04/07/2016 05:19:24 - Critical bpbrm (pid=20605) unexpected termination of client ALP-NBUMED-01
04/07/2016 05:19:26 - Error bptm (pid=20666) media manager terminated by parent process
04/07/2016 05:19:29 - Error bptm (pid=20746) unable to perform read from client socket, connection may have been broken
04/07/2016 05:19:39 - Error bpbrm (pid=20605) could not send server status message
04/07/2016 05:19:40 - Info bpbkar (pid=7224) done. status: 50: client process aborted
04/07/2016 05:19:40 - end writing; write time: 2:03:06
04/07/2016 08:19:43 - Info bpbrm (pid=28862) Starting delete snapshot processing
04/07/2016 08:19:43 - Info bpfis (pid=0) Snapshot will not be deleted
04/07/2016 08:19:46 - Info bpfis (pid=7260) Backup started
04/07/2016 08:19:46 - Critical bpbrm (pid=28862) from client ALP-NBUMED-01: FTL - cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.ALP-NBUMED-01_1459995304.1.0
04/07/2016 08:19:46 - Info bpfis (pid=7260) done. status: 1542
04/07/2016 08:19:46 - Info bpfis (pid=0) done. status: 1542: An existing snapshot is no longer valid and cannot be mounted for subsequent operations
client process aborted  (50)
**********************************************************************************************************************************************

[Will_Restore]

ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.

On the client, Run As Administrator cmd.exe, then vssadmin list writers

Probably will show some error or "waiting" in which case reboot the client & retry the backup.

[amit4465]

This is the output, i cant find any errors.

C:\Users\adm_56434>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {c89128c3-e404-419e-a0d8-c826229ae40b}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {81f629d0-d5e9-42d1-8062-6db01e26dff0}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {cb5f17ea-b783-45ca-94c8-8145d22944a3}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {0234b60a-5587-4283-b947-8fa071332214}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {4fc164a6-88c1-4ccc-ac16-b3aba5a4e314}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {e6b321dd-51b1-43d3-91ba-6ab24f119af2}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {ecdfd93b-929e-41dd-82df-226f77699a52}
   State: [1] Stable
   Last error: No error

[Will_Restore]

OK, looks good.  If trouble persists, see https://www.veritas.com/support/en_US/article.TECH224229

EXIT STATUS 69: invalid filelist specification 

* Contact Microsoft for further troubleshooting *