how to kill hung Domino processes

On all of my Domino servers, I load some of the Windows NT, 2000, or 2003 Resource Kit Utilities. See Microsoft KB article 927229 for the Windows 2000 Resource Kit Tools download page (You can download them individually and they’re free).

Here is the link to the Windows Server 2003 Resource Kit Tools

The individual tools I use are:
WNTIPCFG.EXE (does not work on Windows 2003 unfortunately)

I put them into the c:\program files\rktools\ directory, which is the default if you install the whole package. I also put that directory into the path so that you can execute any of the commands from any directory or any script/batch file.

If you have a hung Domino process that refuses to shut down, go to the command prompt and type:
0 System Process
4 System
416 smss.exe
464 csrss.exe
488 winlogon.exe
536 services.exe
548 lsass.exe
940 svchost.exe
1128 spoolsv.exe
1152 msdtc.exe
1284 EmcPowSrv.exe
1296 RMServer.exe
1312 HbaHsMgr.exe
1388 svchost.exe
1428 ibmhpasv.exe
1464 nservice.exe
1600 NaviAgent.exe
1636 nsrexecd.exe
1700 nsrpm.exe
1712 nserver.exe Notes1/Domain: Lotus Domino Server
1728 NTRtScan.exe
1824 svchost.exe
1836 savapi2s.exe
1860 RaidServ.exe
2116 TmListen.exe
2168 nevent.exe
2612 nupdate.exe
2720 nreplica.exe
2728 nrouter.exe
2740 namgr.exe
2748 nadminp.exe
2756 ncalconn.exe
2764 nsched.exe
2772 nhttp.exe
2800 patrolat.exe
2844 ncollect.exe
2868 nrunjava.exe
2876 ntm_grab.exe OleMainThreadWndName
2884 nSMDemf.exe
2912 nSMDreal.exe
2920 nSMDsch.exe
2928 nSMDmon.exe
2936 nsmtp.exe
3044 svchost.exe
3312 namgr.exe
3340 alg.exe
3684 CNTAoSMgr.exe
3700 AD28BF.EXE
308 ncldbdir.exe
1744 nclrepl.exe

I’ve cut the list short to save space.

Let’s say for example you want to stop the router task and from the Domino console “tell router quit” has no effect.

Notice in the list above, that the router is listed as “2728 nrouter.exe”

If you have hundreds of tasks, you can type:
C:\>tlist nrouter.exe
2728 nrouter.exe
CWD: d:\Lotus\Domino\
CmdLine: d:\Lotus\Domino\nRouter.EXE
VirtualSize: 1056780 KB PeakVirtualSize: 1057804 KB
WorkingSetSize: 14460 KB PeakWorkingSetSize:598896 KB
NumberOfThreads: 12
2732 Win32StartAddr:0×00434540 LastErr:0×00000000 State:Waiting
2292 Win32StartAddr:0x601158c0 LastErr:0×00000000 State:Waiting
1072 Win32StartAddr:0x601158c0 LastErr:0×00000000 State:Waiting
720 Win32StartAddr:0x601158c0 LastErr:0×00000000 State:Waiting
4616 Win32StartAddr:0x601158c0 LastErr:0×00000000 State:Waiting
5108 Win32StartAddr:0x601158c0 LastErr:0×00000000 State:Waiting
1572 Win32StartAddr:0x601158c0 LastErr:0×00000000 State:Waiting
4004 Win32StartAddr:0x601158c0 LastErr:0×00000000 State:Waiting
5664 Win32StartAddr:0x601158c0 LastErr:0×00000000 State:Waiting
2944 Win32StartAddr:0x601158c0 LastErr:0×00000000 State:Waiting
4344 Win32StartAddr:0x601158c0 LastErr:0×00000000 State:Waiting
2320 Win32StartAddr:0x601158c0 LastErr:0×00000000 State:Waiting shp 0×00400000 nRouter.EXE
5.2.3790.3959 shp 0x7C800000 ntdll.dll
5.2.3790.4062 shp 0x77E40000 kernel32.dll shp 0×60000000 nnotes.dll shp 0x621B0000 nxmlpar.dll shp 0×62320000 nxmlcommon.dll
7.0.3790.3959 shp 0x77BA0000 MSVCRT.dll shp 0×62150000 js32.dll shp 0×62350000 NLSCCSTR.DLL
5.2.3790.3959 shp 0x77F50000 ADVAPI32.dll
5.2.3790.4115 shp 0x77C50000 RPCRT4.dll
5.2.3790.3959 shp 0x76F50000 Secur32.dll
6.0.3790.3959 shp 0x766D0000 SHFOLDER.dll
5.2.3790.4098 shp 0x77D00000 OLEAUT32.dll
5.2.3790.4033 shp 0×77380000 USER32.dll
5.2.3790.4033 shp 0x77C00000 GDI32.dll
5.2.3790.3959 shp 0×77670000 ole32.dll
6.0.3790.3959 shp 0x762B0000 comdlg32.dll
6.0.3790.3959 shp 0x77DA0000 SHLWAPI.dll
5.82.3790.3959 shp 0×77530000 COMCTL32.dll
6.0.3790.4184 shp 0x7C8D0000 SHELL32.dll
5.2.3790.0 shp 0x71BB0000 WSOCK32.dll
5.2.3790.3959 shp 0x71C00000 WS2_32.dll
5.2.3790.3959 shp 0x71BF0000 WS2HELP.dll shp 0×62950000 ndgts.dll
5.82.3790.3959 shp 0×77420000 comctl32.dll shp 0x624D0000 NSTRINGS.DLL shp 0×10000000 ntk_hook.DLL shp 0x4A800000 icuucgrp36.dll shp 0x4AD00000 icudtgrp36.dll shp 0x625B0000 namhook.DLL shp 0x038D0000 nSMDext.DLL shp 0×03900000 nte_hook.DLL shp 0×62610000 nNTCP.DLL
5.2.3790.3959 shp 0x71B20000 mswsock.dll
5.2.3790.3959 shp 0x76ED0000 DNSAPI.dll
5.2.3790.3959 shp 0x76F70000 winrnr.dll
5.2.3790.3959 shp 0x76F10000 WLDAP32.dll
5.2.3790.3959 shp 0x76F80000 rasadhlp.dll shp 0x625D0000 nTCP.DLL
5.2.3790.3959 shp 0x5F270000 hnetcfg.dll
5.2.3790.3959 shp 0x71AE0000 wshtcpip.dll shp 0x044C0000 nFTGTR40.DLL shp 0x044E0000 gtr40nts.dll shp 0×04570000 nlxlid102.dll shp 0×04590000 nlxrt22.dll shp 0x0FD40000 nlxsum22.dll shp 0x0FDA0000 kvfilter.dll

The results show each nrouter.exe task and it’s Process ID (PID).

Once you know the PID, you can use the kill.exe command

C:\>kill 2728
This will show you that a process has been killed.
You should notice that the process disappears from the process list in the Windows Task Manager and from the Domino console list.

This works 99% of the time.

You can also type:
C:\>Kill nrouter.exe
This does work, but I have found mixed results. It works less often that specifying the PID.

You can also try to use the Windows Task Manager, select the Processes view, and click “End Process” on the hung process, but I have found that this does not work very often.

All of that being said, you should only kill processes like this if it is an extraneous situation and they will not quit via the Domino console. If you are successful in killing the process, you should try and reboot the server as soon as possible to have a “clean” Domino process and memory footprint. It would be assumed that if you are resorting to killing a process like this, the server cannot be recycled until the end of the business day. So typically if you need to kill a compact process, for example, because it is hung and eating up resources, but you cannot reboot the server because it is in the middle of a business day on a busy server – make sure and reboot it at the end of the business day to clean everything up.

Leave a Reply


I'm currently available
for Lotus Notes / Domino consulting engagements.


Connect with me: