Licensing problem with 5.1 sp6 1

[ehavens]

I have 1 5.1 server with 3 5.0 servr in the tree. On serveral occasions the licensing on the 5.1 server gets wacked. Resulting in policy manager update connection errors
c0001003. Usually dsrepair will fix. This time however I can
neither remove or reinstal the licensing. Would appreciate
any help.

Eric (user)

 

[marvhuffaker]

Does the 5.1 server have a read/write replica on it (for the container holding the license)? if not, put one there.

Also, I suspect that if this is an ongoing problem, you have other DS issues that need resolved. Start with a health check and troubleshoot from there.

You might have to use ConsoleOne to remove the licenses. Or go back and forth between NWADMIN and CONSOLEONE until you get them. Use the same UserID that you used to instal them. Plus, you need to make sure they are flushed out of the system before you reinstall them. It's not good enough just to have them gone in NWADMIN.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[ITsmyfault]

FWIW
Not sure what version of the directory you're on.. but in our case we upgraded our 5.1 servers to eDir 8.7 and had some interesting license problems - nothing serious though. Every time we did an unattended full repair licensing would break which was extra bad bc it was a cluster and all sorts of bad things would happen. Fortunately I learned neat but simple trick that can fix license issues many times. The NLSLSP is the program which communicates with the directory when you attempt to connect. If the links from the NLSLSP to the licenses in the tree are fudged, it can come back with different "you have no license" types of errors.
Try this to fix it:
from the console:
setupnls
then:
unload nlslsp <enter>

the NLSLSP will reload automatically after 10 seconds. You have just reinitialized it and rebuilt the links to the licenses. This fixed it for us and we just knew that whenever we did a health check, we'd have to do one of these on each cluster member before we wrapped it up or face the consequences. Again, I've only seen this on 5.1 servers which had eDirectory installed on them, but on the off chance it might help here, there you go. At any rate I don't think trying this can hurt.