Solved!
Go to SolutionA
amediratta
2 Intern
•
2014 Posts
0
2990
December 18th, 2006 05:00
The Jukebox is not properly licensed.
Hi,
I have entered the enablers provided to me by EMC and am getting the following error -
"The Jukebox is not properly licensed. Make sure the jukebox is properly enabled and authorized."
Any help or suggestions
I have entered the enablers provided to me by EMC and am getting the following error -
"The Jukebox is not properly licensed. Make sure the jukebox is properly enabled and authorized."
Any help or suggestions
1287
1
Posted December 18th, 2006 05:00
Try to restart server. If it doesn't help, remove license, stop NW, clean /nsr/tmp, start NW and enter license. Before all of that, check that you have correct license (number of slots).1288
0
Posted December 19th, 2006 04:00
Sorry, it is a 38 slot library and 32 slot license.
I think we need to set the available slots to 32 or something. Would this be a problem?825
0
Posted December 19th, 2006 04:00
What is nsrcap saying for enabler code? (nsrcap -vnc ) Also, what does it says for status of that library license - is it recognized and accepted by system?825
0
Posted December 19th, 2006 04:00
nsrcap -vnc accepts the enabler code. Library has been functional for the last 30 days.1288
0
Posted December 19th, 2006 04:00
Sorry, it is a 38 slot library and 32 slot license.
I think we need to set the available slots to 32 or
something. Would this be a problem?
YesI believe it won't work due to famous NW licensing approach, but at least we know now what was the issue.
1287
0
Posted December 19th, 2006 04:00
No this does not work.
We have 26 slot library and 32 slot license.1288
0
Posted December 19th, 2006 05:00
Let me try with a 40 slot temp code, that would make the picture clearer.1288
0
Posted December 19th, 2006 05:00
Yes it is working fine.
I have read a thread that describes how to restrict NEtworker to use lesser no. of slots using nsradmin but neveer tried that - does it work or is there a logical way to do this?815
0
Posted December 19th, 2006 06:00
I never tried that under 7.2.x code (it would be unsupported), but under 7.3.x it should not work. Also, if you leave customer with 7.2.x workaround (under assumtion that it works) what happens once you go 7.3.x? You may try to play with it, but I think it won't work at the end.
ble1
6 Operator
•
14354 Posts
•
56186 Points
1288
0
Posted December 19th, 2006 05:00