Unsolved
This post is more than 5 years old
8 Posts
0
2822
July 31st, 2008 04:00
Probe job had unrecoverable failure(s)
Hello,
On some client-PCs (most notebooks) I am not able to start backups and scheduled backups from the Networker server (V 7.4.1). From client-side backups work.
On the networker Server I get the following messages:
"savegrp: rtww033:D:\ save was never started * Probe job had unrecoverable failure(s)" and "probe unexpectedly exited".
We have tried different Networker client versions and different users with "Admin" rights.
I am looking forward to your replies.
Kind regards, sahjan
On some client-PCs (most notebooks) I am not able to start backups and scheduled backups from the Networker server (V 7.4.1). From client-side backups work.
On the networker Server I get the following messages:
"savegrp: rtww033:D:\ save was never started * Probe job had unrecoverable failure(s)" and "probe unexpectedly exited".
We have tried different Networker client versions and different users with "Admin" rights.
I am looking forward to your replies.
Kind regards, sahjan
No Events found!


benzino1
2 Intern
•
244 Posts
0
July 31st, 2008 05:00
savegrp -p -vvv -c notebook_client_name -l full group_attached_to_client
IKP1
198 Posts
0
July 31st, 2008 23:00
Just a quick question, you say these PCs are mostly notebooks; what OS are they running. If it is Windows XP SP2 or newer then look to the MS Windows Firewall being enabled and stopping communications.
HtH
IKP
sahemc
8 Posts
0
August 1st, 2008 02:00
The clients are running Windows XP with SP2 or SP3. The firewall is configured to use Networker. We also disabled the firewall with the same results.
I am goint to try the mentioned commands next week, when the notebooks are online again.
Kind regards,
sahjan
smora1
253 Posts
0
August 1st, 2008 02:00
DeaconZ28-2015
252 Posts
0
August 1st, 2008 06:00
Networker may not be getting correct DNS resolution for the clients if the IP is changing.
sahemc
8 Posts
0
August 1st, 2008 21:00
Kind regards,
sahjan
sahemc
8 Posts
0
August 4th, 2008 04:00
Here is the output from rpcinfo. RZJS016 is the Server, RTWW033 is the Client:
C:\>rpcinfo -p rzjs016
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390436 1 tcp 8335
390435 1 tcp 9514
390113 1 tcp 7937
390402 1 tcp 9001
390103 2 tcp 9467
390109 2 tcp 9467
390110 1 tcp 9467
390120 1 tcp 9467
390109 2 udp 8929
390105 5 tcp 9858
390105 6 tcp 9858
390107 5 tcp 9509
390107 6 tcp 9509
390104 105 tcp 8107
390104 205 tcp 9025
390104 305 tcp 8547
390104 405 tcp 9076
390104 505 tcp 8373
390104 705 tcp 8966
390430 1 tcp 9913
390429 201 tcp 9275
390429 101 tcp 9409
390433 1 tcp 8207
390104 805 tcp 8400
390104 905 tcp 8536
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390436 1 tcp 8335
390435 1 tcp 9514
390113 1 tcp 7937
390402 1 tcp 9001
390103 2 tcp 9467
390109 2 tcp 9467
390110 1 tcp 9467
390120 1 tcp 9467
390109 2 udp 8929
390105 5 tcp 9858
390105 6 tcp 9858
390107 5 tcp 9509
390107 6 tcp 9509
390104 105 tcp 8107
390104 205 tcp 9025
390104 305 tcp 8547
390104 405 tcp 9076
390104 505 tcp 8373
390104 705 tcp 8966
390430 1 tcp 9913
390429 201 tcp 9275
390429 101 tcp 9409
390433 1 tcp 8207
390104 805 tcp 8400
390104 905 tcp 8536
C:\Documents and Settings\Administrator.JR1>rpcinfo -p rtww033
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390436 1 tcp 9422
390435 1 tcp 8139
390113 1 tcp 7937
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390436 1 tcp 9422
390435 1 tcp 8139
390113 1 tcp 7937
sahemc
8 Posts
0
August 4th, 2008 04:00
Here is the output:
C:\Documents and Settings\Administrator.JR1>savegrp -p -vvv -c rtww033 -l full Client_RTG_Wien_einzeln
32451:savegrp: rtww033:C:\Dokumente und Einstellungen\woi level=full
32451:savegrp: rtww033:D:\ level=full
7236:savegrp: Group will not limit job parallelism
32493:savegrp: rtww033:probe started
savefs -s rzjs016.jr1.local -c rtww033 -g Client_RTG_Wien_einzeln -p -l full -R -v -F "C:\\Dokumente und Einstellungen\\woi" "D:\\"
7336:savegrp: Log file D:\nsr\tmp\gClient_000001 is empty.
7340:savegrp: rtww033:probe unexpectedly exited.
7076:savegrp: --- Probe Summary ---
rtww033:Probe level=full, dn=-1, mx=0, vers=pools, p=1
rtww033:Probe level=full, pool=Default, save as of 04.08.2008 13:24:40
rtww033:C:\Dokumente und Einstellungen\woi level=full, dn=-1, mx=0, vers=pools, p=1
rtww033:C:\Dokumente und Einstellungen\woi level=full, pool=Default, save as of 04.08.2008 13:24:40
rtww033:D:\ level=full, dn=-1, mx=0, vers=pools, p=1
rtww033:D:\ level=full, pool=Default, save as of 04.08.2008 13:24:40
rtww033:index level=full, dn=-1, mx=0, vers=pools, p=1
rtww033:index level=full, pool=Default, save as of 04.08.2008 13:24:40
sahemc
8 Posts
0
August 4th, 2008 04:00
aismaili
25 Posts
0
August 4th, 2008 04:00
PeterBen
120 Posts
0
October 24th, 2008 00:00
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
October 24th, 2008 03:00
Hari5
443 Posts
0
October 24th, 2008 21:00
1. Name resolution from client to server and server to client. I would recommend that the ip addresses and the fqdn be hardcoded into the host file on both ends. Remember that reverse lookup is also required.
2. Some sort of firewall is blocking the traffic. This could be windows firewall or a anti-virus related firewall on the client. It could also be a external firewall between the client and the server.
I had a similar problem recently where reinstalling networker on the client fixed my problem. You might want to try that.