running Networker 7.4.3 on windows 2003, the client windows 2008 R2, networker 7.4 SP5 64bit.
cannot backup the client because of : Error: the client is giving error: unable to set up VSS filesystem directives
Solved! Go to Solution.
If the client enabler code is set to no, then this means the client somehow has not been granted a license or unable to retrieve a license.
Please run the command nsrlic -v in order to review your current license allocation status.
If the client connection licenses have been exhausted, here is a temp enabler for 5 client connections
Please note that you will need to contact licensing to aquire the auth codes and proper licenses as per your entitlement.
Licensing may be contacted at (408)566-2000 or firstname.lastname@example.org
Hello - Seems you are trying to backup a W2K8 R2 client with NW 7.4.5 .
Please bear inmind that this is not supported.
NW 7.5.3 needs to be installed on the client in order to backup W2K8 R2.
Please apply the supported version and let me know the results.
Hello - Here is a link to the NW 7.5 SP3 for Windows x64 package >
Support > Software Downloads and Licensing > Downloads J-O > Networker then scroll down to the Networker 7.5 SP3 section.
I installed like suggested, Networker 7.5 SP3 64 bitsBuilt415 on the client, and started getting this error from the client:
39078: winworkr:SYSTEM error:client'142.x.x.x" is not properly configured on the networker server
I am no longer getting any error regarding VSS since I installed networker client 7.5
You'r help is very appreciated.
Correct any TCP/IP parameters that may have incorrect information (i.e. DNS server, subnet mask, DNS suffix, etc.)
Ensure that the client name as configured on NetWorker, is referenced on the Aliases field.
I have the FQN and short name on the client's aliases field. The server can ping the client aliase, and the client can ping the server
Do I need "save -s servername vss:=*off " in command field ?
You dont need to set VSS:*=off. Do you have more than one NIC on the client. If so just enter all the aliases for the client on the Client properties->aliases. If there is any NIC which is not being used, then disable it.
If you have name resolution (forward and reverse) and aliases configured properly, then the last thing would be to reconfigure this client and check if this helps.