General discussion

Locked

Unable to write license usage info to ND

By nyg2k ·
I have a mixed NW 5/5.1 WAN environment. The tree is divide up into three partitions ROOT,SA_OB,WEST_OB. On three of the NW 5.1
servers, I'm getting the following errors:


2-05-2001 2:25:45 pm: SERVER-5.0-0
NLSLSP.NLM: Warning:Unable to write license usage information to NDS. Historical usage information may be incomplete. Check "O=WEST" partition synchronization. Service will continue. OB_WEST.WEST_OB.

I get this error on three of the NW 5.1
servers,AD_SALK,AD_SANDBURG,and AD_EAST. AD_EAST and AD_SANDBURG are in the ROOT partition and got this error twice within an hour. I ran NDS Manager against the WEST_OB partition and do not come up with any errors. Any ideas? Let me know. Thanks.

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Unable to write license usage info to ND

by wisonpo In reply to Unable to write license u ...

Explaination:NLS detected an accumulation of unsynchronized data on the license certificates.
Possible Cause: The partition containing the license certificate is not synchronizing properly.
Action:Fix NDS synchronization

Collapse -

Unable to write license usage info to ND

by nyg2k In reply to Unable to write license u ...

The question was auto-closed by TechRepublic

Collapse -

Unable to write license usage info to ND

by tbradley In reply to Unable to write license u ...

This is common if you have a busy WAN, and
traffic is not allowing timely synchronization of all your replicas and partitions.

1. Check your time synchronization in DSrepair. Ensure all servers are close to the same time reference. 1 server wayout of sync can throw the whole ball of wax out for a loop, especially if it contains critical NLS data.

2. Once you're sure time sync is ok, do a full dsrepair, at a slow traffic time of day. Start with the Main NDS server, follow up with the other root servers, then all others.
You may have to run it 2 or 3 times to get errors down to zero.

3. If you can't get errors down to zero, then
you have some severe traffic problems, and it's time to look at how your routers are handling your traffic.

HOpe this helps.

Collapse -

Unable to write license usage info to ND

by nyg2k In reply to Unable to write license u ...

The question was auto-closed by TechRepublic

Collapse -

Unable to write license usage info to ND

by aclerici In reply to Unable to write license u ...

Be sure you have applied NW51 Spack 2.0a & possibly WSOCK2 to resolve an Nds issue ...

Alex

Collapse -

Unable to write license usage info to ND

by nyg2k In reply to Unable to write license u ...

The question was auto-closed by TechRepublic

Collapse -

Unable to write license usage info to ND

by nyg2k In reply to Unable to write license u ...

This question was auto closed due to inactivity

Back to Networks Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums