One of my Netware 6.5 sp6 servers abended (multiple spinlock abends)
and NDPS would not load on restart. I started it up with /nodatabase
and did a restore and resync. It seemed to be working fine, but I
noticed one printer was missing. I took the PADBTXT.CSV file and
removed all the printers except the missing one and added it back in
with pagen.exe. All seemed well after that and NPDS health monitor was
happy.

About an hour later the server started throwing "NDPSJPMComm failed
with error 1310724, opcode 106" about 3 or 4 times a second.
I looked up the 1310724 error, but that wasn't very helpful.
I resynced the database and the errors stoped, but the one printer was
missing again. I added it back in with pagen.exe again, then using
NDPS Manager, did a backup and then resync. As a test, I tried restore
again, from both Local and NDS. Both worked fine. Everything seemed
happy again.

About an hour later the server started throwing "NDPSJPMComm failed
with error 1310724, opcode 106" again!!! I noticed that PSMDB.DAT had
grown to about 4 times the size. Doing a NDPS manager restore stopped
the errors and all the printers were there.

Now PSMDB.DAT slowly grows over an hour or so then the errors start
again. All this time the printers seem to work OK. Is this an NDS or
NDPS problem? It's been working fine for months. I'm using NDPSM.NLM
V3.02 November 30, 2006 and NDPSGW.NLM Version 4.00.10 March 6, 2007.

Thanks,
Russ