Default Insufficient privileges on Domino 14 on Windows for NSD?

HCL Domino Domino Forum
,
1

I'm investigating a server crash at a customer for Domino 14 and one interesting in the NSD i highlighted in bold below:

ERROR (0): AdjustTokenPrivileges failed - (1300) Not all privileges or groups referenced are assigned to the caller.

WARNING (0): NSD is unable to obtain privileges for some debugging operations. If you are running as a limited or restricted user then NSD will be unable to obtain some of the information it is attempting to collect. NSD will also produce error messages when privileged operations fail. However, useful data such as Notes/Domino callstacks will still be collected.
WARNING (3): can't get process 0x2184 status
Host Name : <removed>
User Name : LOCAL SERVICE
Date : Sun Feb 25 02:02:40 2024
Windows Dir : C:\Windows
Arguments : "d:\Lotus\Domino\nsd.exe" -dumpandkill -termstatus 1 -crashpid 4272 -crashtid 10156 -runtime 600
NSD Version : 14.00.0000.3312 (Release 14.0)
OS Version : Windows/2022 10.0 [64-bit] (Build 20348), PlatID=2, (4 Processors)
Build time : Thu Nov 9 02:45:00 2023
Latest file mod : Thu Nov 09 00:17:49 2023
Domino Version : Release 14.0 (64-bit server)
Java Path : d:\Lotus\Domino\jvm\bin\java.exe
Java Version : openjdk version "17.0.8.1" 2023-08-24

It would be good to know which privileges this entails. What changes do we have to make on Windows when installing Domino 14 to allow NSD to create a full crash report?

2

As far as I know NSD requires Administrator rights to run properly.

I usually create a local user, member of the Administrators group, used as service log on user.

3

This server was installed in the default way (See https://blog.nashcom.de/nashcomblog.nsf/dx/domino-14.0-on-windows-important-to-read-before-updating.htm?opendocument for what I mean), so it would be interesting if the default way result in insufficient access rights for NSD.