Unsolved
This post is more than 5 years old
76 Posts
0
3261
Message box with Error and "Ok" button, when i click on recover on NWS 8.1
Hello everybody,
I have a strange error since the upgrade in 8.1.
And like an image is more explicit than a too long explanation...
When i click on "recover" have a msgbox with "Ok". And if i click on this "Ok" button, the msgbox reappear
I have the same error when i access directly on the NMC (Java 7 update 51) or via another machine with Java 7 update 10.
Anyway, one time i close the Networker administration windows and i rerun it, i haven't anymore this msgbox.
Also, with this msgbox, networker is fully fonctionnal
Have you an idea of what can i do ?
Regards
David.
coganb
736 Posts
0
March 12th, 2014 01:00
Hi David,
According to this article, it could be a problem with the java cache:
https://support.emc.com/kb/108967
-Bobby
ble1
14.3K Posts
0
March 12th, 2014 01:00
If you try to open NMC from some other box, do you get the same?
Vidda911
76 Posts
0
March 12th, 2014 01:00
I have an access deny on this link..
I suppose that it's the explanation on how delete the java cache ?
I have do that on the both server.
Same problem.
Adding info: the NMC have already been reinstalled without result.
Vidda911
76 Posts
0
March 12th, 2014 02:00
Which box ?
Sorry i don't understand.
I have tried to open NMC from another server, same problem.
ble1
14.3K Posts
0
March 12th, 2014 02:00
And what java version do you use (and what NW build)?
Vidda911
76 Posts
0
March 12th, 2014 03:00
Java 7 Update 10 Build 1.7.0_10-b18 on NMC
and
Java 7 Update 51 Build 1.7.0_51-b13 on the other server where i have the same error.
nmc2
268 Posts
0
March 12th, 2014 04:00
Try with deferent user login. Check is there any user permission issue?
Also can you please confirm the NetWorker server build version.
Regards,
Prajith
ble1
14.3K Posts
1
March 12th, 2014 06:00
8.1.0.1??? Come on man... why would you use first release of anything. You can do that, but expect to have all the bugs and shortcomings out there. Update it! Latest patch release for 8.1.0.x is 8.1.0.5 and it won't be updated as SP1 has been released and current release there is 8.1.1.3.
Vidda911
76 Posts
0
March 12th, 2014 06:00
Test with a different user, same problem.
Version of NWS is 8.1.0.1 Build 199
ble1
14.3K Posts
0
March 12th, 2014 07:00
Only if you started your tests more than half a year ago
Vidda911
76 Posts
0
March 12th, 2014 07:00
Simply, because we have a test environement where all work perfectly.
But maybe is not enough for Networker...
Man...
Vidda911
76 Posts
0
March 13th, 2014 07:00
I will upgrading my NWS/NMC during the next 2 weeks.
I'll keep you inform.
dsienerth
2 Posts
0
June 24th, 2015 10:00
Sorry if I'm raising the dead here, but besides "updating" the Networker/NMC, was there an actual answer to this question??? I'm running version 8.2.1.3b774 and I'm getting this same non-informational error box on the Recover tab. I've cleared the Java cache with no results. Same error regardless of user or running on server or from web. Nothing in any logs that point to anything useful.
Has anyone actually solved this?
Brooklyn2
4 Posts
0
November 5th, 2015 07:00
I recently started experiencing this yesterday. I tried deleting the Java cache and it didnt work. Today I couldn't take it anymore and just stopped all services related to networker/java and delteted cache a few times in a row and it is gone. Hopefully this will work for you too.
kge8889
6 Posts
2
April 6th, 2016 06:00
I have seen this issue on multiple versions of Networker. The issue are saved recoveries that are kept when using the Recover, New Recovery option. Here is how to correct the issue.
1) On the Networker server at command prompt: type nsradmin and enter
2) nsradmin> print type: NSR recover This will display the recovers that are stored
3) nsradmin> d Type "d" to delete the recoveries that are saved
4) y Enter a "y" to confirm the deletion of each recover that is saved.
5) When it goes back to the nsradmin> command prompt you may exit.
6) Close the NMC console and then start it up again and login. The error message should no longer appear.