Voltar
-
Título
"NTLM failed due to insufficient memory" when adding a new SQL Server agent -
Descrição
Unable to add a new SQL Server agent. The error "NTLM failed due to insufficient memory" is encountered using the Agent Installer in the SQL Server cartridge. -
Causa
NTLM Access token size is too small.
Access token size in bytes can be estimated by using the following formula:[12 x number of user rights] + [token overhead] + [44 x number of group memberships] = token size in bytes- User rights include rights such as "Log on locally" or "Access this computer from the network." The only user rights that are added to an access token are those user rights that are configured on the server that hosts a secured resource. Most Exchange Server users are likely to have only two or three user rights on the Exchange server. Administrators may have dozens of user rights. Each user right requires 12 bytes to store it in the token.
- Token overhead includes multiple fields such as the token source, expiration time, and impersonation information. For a typical domain user who has no special access or restrictions, token overhead is likely to be between 400 and 500 bytes. Typically, estimating 500 bytes for both user rights and token overhead is more than sufficient.
- Each group membership adds the group SID to the token together with an additional 16 bytes for associated attributes and information. The maximum possible size for a SID is 68 bytes. However, it is rare for a SID to be this large. In Windows Server 2003 and in earlier versions of Windows, the typical SID for a user or a group is 28 bytes in length. Therefore, each security group to which a user belongs typically adds 44 bytes to the user's token size.
Ref: Microsoft -
Resolução
Solution 1:
The token size (MaxTokenSize) value in the Windows registry was increased.
Solution 2:
Instead of using a domain account, create a SQL Server account to monitor the affected SQL Server Instance. Assign all the required permissions.
Please note: Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.