Search: Advanced search

Knowledgebase

Known Issues & fixes

...

Enterprise Report - Backup Variance: No dialog window present in SP Console to specify a Variance value

Restore fails for files containing non-Latin characters (e.g. Chinese)

MirrorServer log: "Unable to perform a roll-up since some required files have not been mirrored yet"

ReportServer Properties (Enterprise Reports) – The option ‘Enforce retention period’ is still enforced when disabled

Storage Platform Console closes when selecting Help > Product Help or Help > About

"Unable to load data index" error on the StorageServer during a backup

A scheduled report for a very large number of Backup Accounts fails to send

How to upgrade a branded Storage Platform to the Attix5 Pro brand using the Attix5 Pro SP Installer

Microsoft HotFix KB976769v2 cause service not to start on Windows Server 2003

Patches and full files with same resulting hashes causes dedupe errors

Error when calling the RestoreDatabase method on net.tcp://0.0.0.0:50148/sys/transfer

Attix5 Pro V6.1.x and above on Mac OS X (10.7 and 10.8)

Backup Account unable to back up when StorageServer IP address overridden on V6.2.2

WSB plug-in troubleshooting

Email Notification plug-in not working after upgrade to Attix5 Pro SE V6.1.0.4 (if using SMTP authentication)

Backup client UnsatisfiedLinkError fault finding on Unix/Linux

MAC client patching unchanged data with every backup

Warning in Client log: "Could not move backup file to cache"

Manual Account Server DB backup shows successful in the SP Console but failed in the AS log (V6)

Roll-up failing since some required files have not been mirrored yet

Automatic Backups stop after Mac auto update

Missing files or folders when doing a remote restore on Linux client

Files with extended characters on a Linux client gives a RPC error in the SP Console.

Remote connection with SP Console to client failing after client upgrade from V5 to V6

SIMS Discover backup hangs after upgrading to the SIMS Summer 2012 release

Show all...

WSB plug-in troubleshooting

Article ID: 72

Last updated: 21 Jun, 2012

Export to PDF

Email to friend

Add comment

Comments: 0

Posted: 28 Jul, 2011
by Van Rensburg J.

Updated: 21 Jun, 2012
by Harnekar T.

There are various reasons why the WSB plug-in could fail, such as:

WSB plug-in failure due to missing VSS writer
WSB plug-in failure due to SCSI controller drivers
WSB plug-in failure due to corrupt VHD file
WSB plug-in installed but not shown in GUI

For a list of other possible reasons, check out the Note section below.

WSB plug-in failure due to missing VSS writer

Symptom

One such reason is that the required VSS writer is missing. The System State plug-in using WSB fails during the back up with the following error in the Server Edition backup log:

Message: 19:00:02 Performing system state backup
Message: 19:00:02 Waiting for wbadmin to complete.
Warning: 19:00:34 [System State (WSB)]: System state backup failed: Exit Code = -3

Cause

To confirm the staus of the System State backup and help determine the failure, run the following command:

C:\>wbadmin get status

Example of output:

C:\>wbadmin get status
wbadmin 1.0 - Backup command-line tool

(C) Copyright 2004 Microsoft Corp.

Creating the shadow copy of volumes requested for backup.

Creating the shadow copy of volumes requested for backup.

Summary of backup:

------------------

Backup of system state failed [7/21/2011 5:16 PM]

Log of files successfully backed up

'C:\Windows\Logs\WindowsServerBackup\SystemStateBackup 21-07-2011 17-16-27.log'

Log of files for which backup failed

'C:\Windows\Logs\WindowsServerBackup\SystemStateBackup_Error 21-07-2011 17-16-27

.log'

System writer is not found in the backup.

C:\>

Note the last line in the output above.
The System State VSS writer is not found and is the cause of the failure.

Solution

Full Microsoft Knowledge Base article: http://support.microsoft.com/kb/2009272

To resolve this issue, type the following commands from an elevated Command Prompt:

Takeown /f %windir%\winsxs\temp\PendingRenames /a
icacls %windir%\winsxs\temp\PendingRenames /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\temp\PendingRenames /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\temp\PendingRenames /grant BUILTIN\Users:(RX)
Takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)

net stop cryptsvc
net start cryptsvc

Run the following command to verify that the system writer is now listed:
vssadmin list writers

WSB plug-in failure due to SCSI controller drivers

Symptom

Another reason why the WSB plug-in could fail is specific to Windows 2008 R2 machines running within VMWare, and relates to the SCSI controller drivers. The System State plug-in using WSB fails during the back up (after some time) with the following error in the Server Edition backup log:

Message: 19:00:02 Performing system state backup
Message: 19:00:02 Waiting for wbadmin to complete.
Warning: 19:15:28 [System State (WSB)]: System state backup failed: Exit Code = -3

In the event logs, an event ID 517 sourced from 'Backup' is logged, containing the following:
"The backup operation that started at 'time' has failed with following error code '2155347997' (The operation ended before completion.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."

Cause

This issue is specific to Windows 2008 R2 machines running within VMware, and relates to the SCSI controller drivers.

Solution

Using Regedit, open the registry key HKLM\System\CurrentControlSet\service\LSI_SAS
Modify the “String Value” of IMAGEPATH from \SystemRoot\system32\drivers\lsi_sas.sys to system32\drivers\lsi_sas.sys
Reboot the machine and clear the WindowsImageBackup path, then run a backup.

More details can be found on the following Technet page:
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/088fa0fd-6290-4250-bf63-f53fbb974298/

Further discussion of the problem can be found here:
http://networkadminkb.com/KB/a467/how-to-fix-windows-2008-r2-system-state-backup-fails.aspx

WSB plug-in failure due to corrupt VHD file

Symptom

System State backup fails at the SplitVHD stage with the following messages:

Error: 11:16:50 [System State (using WSB) Plug-in] SplitVHD.exe has an error (exit code = 2). See backupservice.log for more detail.
Error: 11:16:52 could not create backup: File collection interrupted

The backupservice.log file shows a stack trace of the file collection error, but no other details:

2012-06-18 11:16:52,372 ERROR errorlog - could not create backup: File collection interrupted
java.lang.InterruptedException: File collection interrupted
    at com.letsbackup.fileutils.BackupProcessor.processSelection(BackupProcessor.java:2095)
    at com.letsbackup.fileutils.BackupProcessor.doBackupCommand(BackupProcessor.java:1153)
    at com.letsbackup.fileutils.BackupProcessor.run(BackupProcessor.java:578)

The SplitVHD.log shows a "Substream extends beyond end of parent stream" error:

Reading 4,481 VHD allocation blocks
Analysing Master File Table
System.ArgumentException: Substream extends beyond end of parent stream
   at DiscUtils.SubStream..ctor(Stream , Int64 , Int64 )
   at DiscUtils.Ntfs.MasterFileTable..ctor(INtfsContext )
   at DiscUtils.Ntfs.NtfsFileSystem..ctor(Stream )
   at SplitVHD.Program.GetDataExtentsFromVhd()
   at SplitVHD.Program.DoRun()

Cause

SplitVHD is failing as the Master File Table (MFT) of the VHD file is corrupt. The most likely cause of this is due to corruption in the MFT of the actual system volume. Running a ChkDsk in read-only mode (which is possible without rebooting) will reveal if this is the cause of the problem.

Run the command "chkdsk" from the Command Prompt to run a read-only check.

Solution

If errors are found, run "chkdsk" with "/f" to fix errors.
More details can be found on the following MS Technet page: http://technet.microsoft.com/en-us/library/cc730714%28v=ws.10%29.aspx

When the MFT of the system volume is fixed, allow a fresh backup to run. After Windows Server Backup (WSB) writes out the VHD to disk, SplitVHD will be able to read the .VHD file successfully and split this into its component parts. This in turn will allow Attix5 Pro to de-duplicate the contents of the VHD and back up successfully.

WSB plug-in installed but not shown in GUI

Symptom

The System State (using WSB) plug-in is installed, but is not shown in the Backup Client's plug-in menu. Therefore it cannot be configured.

Cause

Java is used to detect the operating system version, and this is used to determine which System State plug-in is loaded. If Java is an older version it might identify the operating system incorrectly, e.g. it might identify Windows 2008 as Windows Vista. The incorrect operating system is then presented to Attix5 Pro which does not have a corresponding System State plug-in for the OS and therefore does not load one.

Solution

If Java is an older version, the solution is to update the Java installation so that the correct OS version is detected. With the correct OS detected, Attix5 Pro loads the correct System State plug-in. If the Java version is earlier than 1.6.0_16, Windows 2008 is identified as Windows Vista. Java will need to be updated to 1.6.0_16 or a later Java 6 version.

Note: Java 7 is not yet supported by Attix5 Pro.

Follow the solution section of FAQ 141 for details on updating Java: http://v6.attix5.com/kb/?View=entry&EntryID=141.

Note

The System State plug-in using WSB could fail due to other reasons, such as:

A failed SharePoint upgrade - See this article for more information.
Microsoft Exchange having circular logging enabled - See this article for more information.

This article was:

Helpful | Not helpful

Prev		Next
Article 156 - Backup Account unable to back up when StorageServer IP address...		Article 73 - Email Notification plug-in not working after upgrade to Attix5...