Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VSS Filesystem error

Status
Not open for further replies.

v1nsr

Technical User
Oct 4, 2012
50
QA
Hi ,

We are getting the below error

Error : VSS SYSTEM FILESET: ERROR: VSS failed to add comps in pre save, writer=System Writer, error=0x80070002: The system cannot find the file specified.

7162ave: save of VSS SYSTEM FILESET:\ to lbr-bck-w01 failed
<ERROR> : Failed with error


--->performed the below steps but the issue still persists, can someone please assist


 This error is generally caused when VSS tries to search some files which has been removed by uninstallation of any software but in OS more specifically registry is still pointing to those files.
So, networker when tries to take backup, it always fails with VSS error, as VSS cannot find those files.
To avoid it, please modify the "Backup command" box in the Apps & Modules tab of the client resource. It should contain the string ... save -a '"ignore-all-missing-system-files=yes"'

Now try the backup, if issue still persists, refer the following.

 check status using vssadmin list writers , make sure they are in stable state (as we are already through with this check , would request you to perform this check once again)
If not restart the following Windows services:

"COM+ Event System"
"Microsoft Software Shadow Copy Provider"
"Volume Shadow Copy


 Please run a client initiated backup with Debug mode 3 for the failing drives. Please read the last 10-15 lines when this command finishes with whatever status.
In those 10-15 lines you will find the exact path where the backup is failing. Then please check the below things:

1) Check if the directory exists if not then please create a temporary empty directory with the same or clear the registry using registry cleaning tool
2) It may be the path is not accessible if the server is a part of cluster so please try to access the particular directory.
3) Please check if the failing path is a part of any DFS mount path.
4) More over please check the event logs once the backups get completes.

By using this way we will easily find the direction to fix the vss errors.


 This problem is also caused due to one or more profiles under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList with missing ProfileImagePath.

To check whether you have missing profiles:
1. Open regedit, navigate to the above registry key. (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList). Expand the list

2. Click on each of the profiles listed. The first 3 profiles should have ProfileImagePath value of
%SystemRoot%\System32\Config\SystemProfile,
%SystemRoot%\ServiceProfiles\LocalService, and
%SystemRoot%\ServiceProfiles\NetworkService
respectively.

3. Starting from the 4th profile, the ProfileImagePath should contain path to the user profiles on your machine, such as C:\users\Christine
4. If one or more of the profile has no profile image, then you have missing profiles.

To work around this, delete the profile in question (Caution: The registry contains critical settings that are necessary for your system to function properly. Take extra caution while making changes)

1. First, export the ProfileList key for safekeeping. (Right click on the key, choose “Export”, and save it to the desktop.)
2. Right click on the profile in question, choose delete.
3. Try backup again.
 
Would be nice to know the OS version.
 
Backup server:

Networker version: 7.6
OS: WIN 2003 r2

Client:

Networker Version: 7.6
OS: Windows NT server on Intel


 
That's what i thought.

On Windows 2008 you can fix a VSS System Write problem without a reboot. This works pretty well.

On Windows 2003 i am afraid there is no other alternative than a restart.
IMHO, anything else is just a waste of time.
 
do you mean client reboot or the server
 
The system which reports the error - usually a client.
 
As per the client the server has already been rebooted ...


We put VSS:*=off in Save operation under

Apps and modules
Backup command

right now and took a test backup but it failed

1 retry attempted
81030:save: Most VSS Save Operations values are ignored on this OS platform.
VSS SYSTEM FILESET: ERROR: VSS failed to add comps in pre save, writer=System Writer, error=0x80070002: The system cannot find the file specified.

7162:save: save of VSS SYSTEM FILESET:\ to lbr-bck-w01 failed
<ERROR> : Failed with error(s)


What should we do next..is reboot the only way out??
 
The issue is not a NW error - it is a an error with MS's VSS system writer.
I never tried this but i am pretty sure that every other application/backup software which uses it, will also have a problem.
This is what you must solve first.
 
we will reboot the client and let you know about the progress
 
Found that the System Writer was missing so we recovered it..is it still advisable to reboot

Failing with the same error
 

Tried to run client initiated backup in debug mode and below are the logs

Client initiated backup.Option '-l' is ignored and backup is performed at level
adhoc
Creating tcp RPC client handle with host LBRPECP1 :):1)
Creating TCP/IPv6 RPC client handle
Creating TCP/IPv6 RPC client handle
Attempting to bind IPv6 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv6 socket descriptor 884 to port 7938
RPC service 390109 (vers 2) not registered on ::1
Creating TCP/IPv6 RPC client handle
Attempting to bind IPv6 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv6 socket descriptor 884 to port 111
RPC service 390109 (vers 2) not registered on ::1
80722 4 %s%s 2 24 36 Failed to create RPC client handle: 11 26 355:program not
registered
Creating tcp RPC client handle with host LBRPECP1 (127.0.0.1)
Creating TCP/IPv4 RPC client handle
Creating TCP/IPv4 RPC client handle
Attempting to bind IPv4 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv4 socket descriptor 884 to port 7938
RPC service 390109 (vers 2) not registered on 127.0.0.1
Creating TCP/IPv4 RPC client handle
Attempting to bind IPv4 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv4 socket descriptor 884 to port 111
RPC service 390109 (vers 2) not registered on 127.0.0.1
80722 4 %s%s 2 24 36 Failed to create RPC client handle: 11 26 355:program not
registered
Failed to get server attributes for save: Program not registered
Creating tcp RPC client handle with host LBRPECP1 :):1)
Creating TCP/IPv6 RPC client handle
Creating TCP/IPv6 RPC client handle
Attempting to bind IPv6 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv6 socket descriptor 884 to port 7938
RPC service 390433 (vers 1) not registered on ::1
Creating TCP/IPv6 RPC client handle
Attempting to bind IPv6 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv6 socket descriptor 884 to port 111
RPC service 390433 (vers 1) not registered on ::1
80722 4 %s%s 2 24 36 Failed to create RPC client handle: 11 26 355:program not
registered
Creating tcp RPC client handle with host LBRPECP1 (127.0.0.1)
Creating TCP/IPv4 RPC client handle
Creating TCP/IPv4 RPC client handle
Attempting to bind IPv4 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv4 socket descriptor 884 to port 7938
RPC service 390433 (vers 1) not registered on 127.0.0.1
Creating TCP/IPv4 RPC client handle
Attempting to bind IPv4 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv4 socket descriptor 884 to port 111
RPC service 390433 (vers 1) not registered on 127.0.0.1
80722 4 %s%s 2 24 36 Failed to create RPC client handle: 11 26 355:program not
registered
77558:save: Warning: Could not determine job id: Program not registered. Continu
ing ...
Creating tcp RPC client handle with host LBRPECP1 :):1)
Creating TCP/IPv6 RPC client handle
Creating TCP/IPv6 RPC client handle
Attempting to bind IPv6 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv6 socket descriptor 884 to port 7938
RPC service 390109 (vers 2) not registered on ::1
Creating TCP/IPv6 RPC client handle
Attempting to bind IPv6 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv6 socket descriptor 884 to port 111
RPC service 390109 (vers 2) not registered on ::1
80722 4 %s%s 2 24 36 Failed to create RPC client handle: 11 26 355:program not
registered
Creating tcp RPC client handle with host LBRPECP1 (127.0.0.1)
Creating TCP/IPv4 RPC client handle
Creating TCP/IPv4 RPC client handle
Attempting to bind IPv4 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv4 socket descriptor 884 to port 7938
RPC service 390109 (vers 2) not registered on 127.0.0.1
Creating TCP/IPv4 RPC client handle
Attempting to bind IPv4 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv4 socket descriptor 884 to port 111
RPC service 390109 (vers 2) not registered on 127.0.0.1
80722 4 %s%s 2 24 36 Failed to create RPC client handle: 11 26 355:program not
registered
Creating tcp RPC client handle with host LBRPECP1 :):1)
Creating TCP/IPv6 RPC client handle
Creating TCP/IPv6 RPC client handle
Attempting to bind IPv6 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv6 socket descriptor 884 to port 7938
RPC service 390109 (vers 2) not registered on ::1
Creating TCP/IPv6 RPC client handle
Attempting to bind IPv6 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv6 socket descriptor 884 to port 111
RPC service 390109 (vers 2) not registered on ::1
80722 4 %s%s 2 24 36 Failed to create RPC client handle: 11 26 355:program not
registered
Creating tcp RPC client handle with host LBRPECP1 (127.0.0.1)
Creating TCP/IPv4 RPC client handle
Creating TCP/IPv4 RPC client handle
Attempting to bind IPv4 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv4 socket descriptor 884 to port 7938
RPC service 390109 (vers 2) not registered on 127.0.0.1
Creating TCP/IPv4 RPC client handle
Attempting to bind IPv4 socket descriptor 884
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv4 socket descriptor 884 to port 111
RPC service 390109 (vers 2) not registered on 127.0.0.1
80722 4 %s%s 2 24 36 Failed to create RPC client handle: 11 26 355:program not
registered
VSS .. new NSRSnapper object..VSS .. COM library initialized.VSS .. CoInitialize
Security succeeded ..
getstats(VSS, 0000000000108680)
fullcanon(name=VSS)
exit fullcanon(fullname=C:\Users\rpradm\VSS)
6999:save: VSS: No such file or directory
getstats(SYSTEM, 0000000000108680)
fullcanon(name=SYSTEM)
exit fullcanon(fullname=C:\Users\rpradm\SYSTEM)
6999:save: SYSTEM: No such file or directory
getstats(SERVICES:, 0000000000108680)
fullcanon(name=SERVICES:)
exit fullcanon(fullname=SERVICES:)
6999:save: SERVICES:: No such file or directory
VSS .. cancelsnap called -- backup state is 0 -- UNDEFINED VSS .. destructing NS
RSnapper..win32_post_save(): Called
C:\User
 
In your debug file there is IPv6 mentioned so your client is mostlikely Windows 2008R2.
To my experience a non or malconfigured IPv6 Stack can give unpredictable errors.
So disbale IPc& on your client using regedit, locate HKEY_local_machine\SYSTEM\CurrentControlSet\Services\TCPIP6\parameters. Then add the dword DisabledComponents with the value of 0xffffffff.
reboot and test again.
On 2008R2 the VSS:*=off command is ignored.

 
Sorry that i have have not detected the most important issue: compatibility.
- Windows NT does not have VSS implemented
- A (relatively new) NW 7.6 client does not support Windows NT any longer.
- You must use the appropriate older NW client SW (we use 7.3.4 bo backup such an old machine).

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top