Deleting the LPO Object

Problem

"I recently ran into an issue with our BM38SP3 NW6SP5 server where users were unable to log in and were getting various NMAS errors. I was told to delete the LPO object and reboot, which I did.

Thereafter I got "NMAS Failed to launch" errors scrolling off the console, and still users were unable to log in.

I recreated the LPO - still no joy. Then I found there was no login sequence defined. I defined a NDS login sequence, and the NMAS error went away on the server, but some folks are still having difficulty logging in, getting the FFFFF981 message."

Solution

And here's some advice from Novell's Scott Kiester ...

For the benefit of those reading this, it is never a good idea to delete your LPO. As you have seen firsthand, deleting your Login Policy Object will only cause new problems.

You can use nmasinst.nlm to restore your LPO. From the server console, enter:
"nmasinst -m admin.container adminPassword"

This will re-run the portion of the NMAS install that creates the NMAS objects in eDirectory.

Next, you'll need to re-create your login sequences. A login sequence is an ordered list of login methods. Login sequences are stored in an attribute on the LPO, so any login sequences that you had prior to deleting the LPO will be gone now.

Nmasinst.nlm will create the NDS login sequence automatically, but you'll have to use ConsoleOne or iManager to re-create login sequences any for other login methods that you have installed. A typical configuration will have one login sequence for each login method.