Networks

Most common licensing problems are fixed in NW5SP5. Since these errors tend to happen at inconsistent intervals, the relief you got from moving the licenses was probably a coincidence.

As for the container, assuming all subordinate objects are gone, check the health of your DS and have another go at deleting it.

NW stores licenses in file located at DOS partition. If you used command like [remove dos] in your autoexec.ncf file in some cases NW will lose licenses Have a nice work

P.S. At server console you can run install programm and load licenses from disk (in condition that you not removed dos )

A 3 node training network is great for making mistakes and learning where you aren't risking your company or your career.

NWAdmin is convenient, but for basic server operations, if you can get to the physical server console easily, use the bluescreen utilities. There is also no question of your being able to get a "connection" when you are at the console.

Starting just like NW Support - you must have all the service packs loaded. Run the DS Repair utility and also check the schema with the nds manager.

Remember that with no licenses installed, the basic system will accept 2 logged connections. Some older server-side programs will use a connection, even though they are now supposed to.

If the license is shown as still installed, and you can't remove the associated container, try looking at the Licence Server manager through the console.

You may also be able to use nwsetup to remove the undesired licence.

Only if everything else fails, should you remove NDS. This is practice for the r

This question was closed by the author