Article ID: 937919 - Last Review: October 8, 2011 - Revision: 2.0 The GetUserNameEx function returns the user name in an incorrect format in Windows Server 2003
On This PageSYMPTOMSIn Microsoft Windows Server 2003, you call the GetUserNameEx function to retrieve the Security Account Manager (SAM)-compatible user name. The SAM-compatible user name is retrieved by impersonating the client token. However, if you use the NameSamCompatible value as the NameFormat parameter, the GetUserNameEx function returns the user name in an incorrect format. You expect the following user name format: NetBIOS_Domain\User_Name However, the format of the returned user name is as follows: DNS_Domain\UPN Note The NetBIOS_Domain placeholder represents the NetBIOS domain name for the user. The User_Name placeholder represents the SAM account name for the user. The DNS_Domain placeholder represents the Domain Name System (DNS) domain name for the user. The UPN placeholder represents the user principal name for the user.Applications may experience unexpected issues if software developers have assumed that the returned user name is formatted correctly. CAUSEThis problem occurs because the Kerberos component in Windows Server 2003 applies an incorrect check before the returned user name is formatted. The check causes the NetBIOS domain name in the Kerberos token to be absent. RESOLUTIONHotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesTo apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003
Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2003 with SP1, x86-based versionsCollapse this table
Windows Server 2003 with SP2, x86-based versionsCollapse this table
Windows Server 2003 with SP1, Itanium-based versionsCollapse this table
Windows Server 2003 with SP2, Itanium-based versionsCollapse this table
Windows Server 2003, x64-based versionsCollapse this table
Windows Server 2003 with SP2, x64-based versionsCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about the GetUserNameEx function, visit the following Microsoft Web site: http://msdn2.microsoft.com/en-us/library/ms724435.aspx
(http://msdn2.microsoft.com/en-us/library/ms724435.aspx)
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|





















Back to the top