Due to compatibility issues, we still have about 40 W2K3 servers in production. Those run fine with NW 8.1.3.7 in our environment although there are a few issues with VSS writers. There is no really need to insist on such old NW software.
Agree with bingo. I also use 8.1.3.x for win2k3 (and 7.6.5 I think for win2k :-D). I don't have VSS issues, but this could be due to patch level. There was fair amount of (documented) patches for VSS under win2k3.
I have a few different errors in the logs that I'm seeing. One is "Volume Shadow Copy Service information: The COM Server with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} and name SW_PROV cannot be started. Most likely the CPU is under heavy load. [0x80080005]"
When I search for nsr description i come across an Application error "Faulting application save.exe, version 7.6.5.7, faulting module libnsr.dll, version 7.6.5.7, fault address 0x00007554."
As already suggested, uninstall the current version of NetWorker client and install the 8.1.3 32 bit version of the NetWorker client. I have a number of Windows 2k3 systems being backed up using NetWorker 8.2.1 running client version 8.1.3 and have not come across any issues for now.
bingo.1
2.4K Posts
0
January 11th, 2016 11:00
This is a general error message and does not tell you anything about the details.
Please have a look at the Event Viewer and especially at ..\nsr\logs\daemon.raw to get more details.
And ensure of course that the OS/NW versions are compatible.
B4FQqUoIrW12094
60 Posts
0
January 12th, 2016 04:00
Windows 2003 is EOL Operating system, even i am facing lots issues with 2003 and networker
Version 7.6 is working fine with Windows 2003 , incase of issue , uninstall the client and reboot the system and re-install the client back
Also update the .net version to the latest supported by Windows 2003
bingo.1
2.4K Posts
0
January 12th, 2016 04:00
Due to compatibility issues, we still have about 40 W2K3 servers in production. Those run fine with NW 8.1.3.7 in our environment although there are a few issues with VSS writers. There is no really need to insist on such old NW software.
ble1
4 Operator
•
14.4K Posts
0
January 12th, 2016 05:00
Agree with bingo. I also use 8.1.3.x for win2k3 (and 7.6.5 I think for win2k :-D). I don't have VSS issues, but this could be due to patch level. There was fair amount of (documented) patches for VSS under win2k3.
awoitte
1 Rookie
•
12 Posts
0
January 20th, 2016 15:00
I have a few different errors in the logs that I'm seeing. One is "Volume Shadow Copy Service information: The COM Server with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} and name SW_PROV cannot be started. Most likely the CPU is under heavy load. [0x80080005]"
When I search for nsr description i come across an Application error "Faulting application save.exe, version 7.6.5.7, faulting module libnsr.dll, version 7.6.5.7, fault address 0x00007554."
crazyrov
4 Operator
•
1.3K Posts
0
January 20th, 2016 21:00
As already suggested, uninstall the current version of NetWorker client and install the 8.1.3 32 bit version of the NetWorker client. I have a number of Windows 2k3 systems being backed up using NetWorker 8.2.1 running client version 8.1.3 and have not come across any issues for now.