Bacula-users

Re: [Bacula-users] Shadow Copy issue - Fatal error: VssOject is NULL

2015-04-21 19:16:28
Subject: Re: [Bacula-users] Shadow Copy issue - Fatal error: VssOject is NULL
From: "John Stoffel" <john AT stoffel DOT org>
To: Luc Van der Veken <lucvdv AT wimionline DOT com>
Date: Tue, 21 Apr 2015 19:13:38 -0400

>> On the client, these entries are logged in C:\Program 
>> Files\Bacula\working\zhfs01.trace
>> fs01: vss_generic.cpp:366-0 VSSClientGeneric::Initialize: CoInitialize 
>> returned 0x80070008

Luc> Is one of the server's disks full or nearing its capacity?

Luc> 0x80070008 means "Not enough storage is available to process this command."

Luc> This message does not always indicate a lack of disk space, but that is 
the first thing to check if you get it.



Luc> Tip: to quickly translate a Windows error code like 0x80070008 to
Luc> a readable message, take the lower half - the last 4 digits, in
Luc> this case 0008, convert it from hexadecimal to decimal - in this
Luc> case 8, and then pass that value after 'net helpmsg ' at a
Luc> command prompt.  Works for most error codes, up to a decimal
Luc> value of a few hundreds.

God, this is so damn useful to know!  Thanks a ton for showing this.
Too bad we can't have Bacula do this translation for us and log it,
along with the original error code just in case.   That would be a
huge help for people debugging prblems like this.


Luc> C:\>net helpmsg 8
Luc> Not enough storage is available to process this command.


Luc> Some other common ones:
Luc> C:\>net helpmsg 3
Luc> The system cannot find the path specified.

Luc> C:\>net helpmsg 5
Luc> Access is denied.

Luc> The upper part - 0x8007 - gives info about where the error originated, and 
the sort of message (first digit 8 or C = error), but there's no such way to 
quickly decode it at a command prompt.


Luc> -----Original Message-----
Luc> From: global16 [mailto:bacula-forum AT backupcentral DOT com] 
Luc> Sent: 21 April 2015 2:03
Luc> To: bacula-users AT lists.sourceforge DOT net
Luc> Subject: [Bacula-users] Shadow Copy issue - Fatal error: VssOject is NULL

Luc> I have been running the same version of Bacula on a Windows 2k12 server 
for over a year (5.2.10).  A few weeks ago, we started getting all our jobs 
failing over the weekend due to an apparent issue with VSS.  Has anyone 
encountered the following fatal error:

Luc> 20-Apr 19:30 bacula-zha JobId 5546: Start Backup JobId 5546, 
Job=Software_Share_Backup_-_Encrypted.2015-04-20_19.30.00_41
Luc> 20-Apr 19:30 bacula-zha JobId 5546: Using Device "FileStorage-software" to 
write.
Luc> 20-Apr 19:30 bacula-zha JobId 5546: Sending Accurate information.
Luc> 20-Apr 19:30 bacula-sd JobId 5546: Volume "zha-software-encrypted-vol0360" 
previously written, moving to end of data.
Luc> 20-Apr 19:30 bacula-sd JobId 5546: Ready to append to end of Volume 
"zha-software-encrypted-vol0360" size=1775302040
Luc> 20-Apr 19:30 fs01 JobId 5546: Fatal error: VSS API failure calling 
"CoInitialize". ERR=Unexpected error. The error code is logged in the error log 
file.
Luc> 20-Apr 19:30 fs01 JobId 5546: Fatal error: VSS was not initialized 
properly. ERR=Cannot create a file when that file already exists.

Luc> 20-Apr 19:30 fs01 JobId 5546: Fatal error: VssOject is NULL.
Luc> 20-Apr 19:30 bacula-sd JobId 5546: Elapsed time=00:00:06, Transfer rate=0  
Bytes/second
Luc> 20-Apr 19:30 bacula-zha JobId 5546: Error: Bacula bacula-zha 5.2.13 
(19Jan13):

Luc> The only way to "fix" this is to reboot the client.  Items I have tried:

Luc> * Restarted the Bacula service on the client - backups still failed
Luc> * Tested connection to client using the 'estimate' command, success. Issue 
isolated to Windows server. 
Luc> * List current VSS instances via cmd prompt (vssadmin list writers) - All 
states reported as Stable / No writers reporting errors 
Luc> * Manually create a shadow copy on the client (vssadmin create shadow 
/for=e: ) and then manually remove all shadow copies (vssadmin delete shadows 
/all) - backup still fails
Luc> * Ran System File Checker (sfc /scannow) - No issues found, backups still 
fail


Luc> After rebooting the client, backups using VSS work fine for a few days and 
then start failing with the same FATAL error.  It is not always the same job 
that fails first.

Luc> On the client, these entries are logged in C:\Program 
Files\Bacula\working\zhfs01.trace
Luc>   fs01: vss_generic.cpp:366-0 VSSClientGeneric::Initialize: CoInitialize 
returned 0x80070008


Luc> If anyone has any ideas on how to further troubleshoot this issue, or have 
encountered this before, I'd greatly appreciate it.[/img]


Luc> 
------------------------------------------------------------------------------
Luc> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Luc> Develop your own process in accordance with the BPMN 2 standard
Luc> Learn Process modeling best practices with Bonita BPM through live 
exercises
Luc> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
Luc> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
Luc> _______________________________________________
Luc> Bacula-users mailing list
Luc> Bacula-users AT lists.sourceforge DOT net
Luc> https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users