AdminP problem causing Lotus Domino 7.0.2 server to hang
I keep receiving AdminP "abnormally terminated" errors on my Lotus Domino 7.0.2 server console. Due to this problem, the server keeps either hanging or getting stuck in the middle of working. I then have to restart it in order for it to begin working again. Can anyone suggest what might be wrong and what I should do to combat this issue?
Software/Hardware used:
Software/Hardware used:
ASKED:
June 30, 2008 6:45 PM
UPDATED:
July 2, 2008 2:44 PM
RELATED QUESTIONS
- I have a Cognos Inpromptu 7 report that works in Windows XP but gives me and error in Windows 7.
- Lotus Notes 'replication only client' problems
- Figured out - Adminp Rename Process - Administrative Server connection?
- error during configuration of lotus notes client 7.2
- Problem with my Local BD in Lotus Notes
Answer Wiki:
Well, unfortunately this could be a myriad of issues. First, have you gotten a NSD? There are tools to help read them, but opening a ticket with IBM and getting them the NSD to help troubleshoot is the first and quickest way to get to the bottom of this. Second, I'd need to know more about your environment, but if you have multiple servers, would it be possible to put a fresh replica of admin4.nsf on the server that is crashing? You need to figure out what adminP is trying to process when it dies. The ease of that depends on how much activity is in your admin4.nsf. If there are not many things being processed in AdminP, you might be able to pinpoint it easily. If you have a large environment, this could be more problematic.
Please post some more information about your environment, and we'll see what we can do to help.
To see all answers submitted to the Answer Wiki: View Answer History.
You should do some basic debugging to try to identify the problem. Firstly, is AdminP crashing on only one server? If so, stop the server, then rename the admin4.nsf database (e.g. to admin4.old), then restart the domino server. Create a new replica of the admin4.nsf database from another server in your domain. Issue a “Tell adminp process all” ……. does the task crash again? If so then it is a problem with an adminp request, if it does not then there was some corruption in the old AdminP database which should now be fixed after creating a new replica. If the problem still occurs then you have to do as Mblazar suggests and identify the actual record causing the crash. Remember that AdminP processes different types of request at different times during the day so this may help you eliminate some requests.