| Previous | Next |
| ERROR_EXTENDED_ERROR | ERROR_INVALID_COMPUTERNAME |
ERROR_INVALID_GROUPNAME
The specified group name is not valid for the receiving Windows subsystem.
ERROR_INVALID_GROUPNAME is Win32 error 1209 (0x4B9). The value says the group-name string violates the syntax expected by the API that received it. “Group” can refer to a domain group, local group, workgroup-related field, or provider-defined grouping, so the function and target server determine the applicable rules.
Information needed before changing the name
- exact API, information level, and target computer or domain
- original UTF-16 string and its length, including leading or trailing spaces
- whether the caller intended a local group, domain group, or workgroup
- qualified form such as
DOMAIN\Nameversus an unqualified account name - normalization performed by UI, JSON, command line, or directory import
Frequent input defects
- path separators or qualification syntax in a field that accepts only a simple name
- control characters, trailing periods, or whitespace copied from a spreadsheet
- a display name supplied where an account name is required
- an empty string produced by failed variable expansion
- using DNS-domain rules for a NetBIOS-style field or the reverse
Diagnostic approach
Log the API and a safely escaped representation of the name, not merely the localized error message. Check length in characters rather than bytes and verify that the call uses the wide-character variant. If a domain prefix is allowed, resolve it separately and validate the account portion according to that API’s documentation.
Developer guidance
Validate at the boundary where the intended namespace is known. A universal “Windows name validator” is unreliable because computer names, DNS labels, local groups, domain groups, shares, and service principal names follow different rules. Preserve the server-returned code so callers can distinguish malformed input from ERROR_ALIAS_EXISTS, access denial, or an unavailable domain controller.
Administrator action
Correct the source directory, provisioning template, or script that supplied the malformed value. Renaming an existing security group can affect ACL readability and integrations even though permissions are SID-based, so do not treat 1209 as permission to rename unrelated groups automatically.
Example
An import tool reads a local group name from CSV and includes an invisible carriage return at the end. The create call returns 1209. Escaped logging exposes the extra character; trimming only transport artifacts and revalidating the intended local-group name fixes the input without changing directory policy.
References
- Microsoft: System Error Codes (1000–1299)
- Microsoft: NetGroupAdd function
- Microsoft: NetLocalGroupAdd function
- Microsoft: Security identifiers
Looking for a different code? Search another status or error code.